Solution Launchpad is available through our certified partner program. Click here to learn how you can become a certified partner.

Overview

Saved searches allow you to create reusable contact filters and segments that can be shared across Keap applications through Solution Launchpad. When you include a saved search in a bundle, users can quickly access pre-configured contact queries without manually recreating search criteria.

What's Included

• Search name

• Search criteria and filter conditions

• Filter logic (AND/OR relationships)

• Sort order configuration

• Any dependencies such as custom fields and tags

What's Not Included

Feature-specific columns (if features aren't available in the destination app's Pro/Max edition)

Form Dependencies

When configuring a saved search, it’s possible to reference other items, which will also be included in your install. Supported dependencies include:

• Contact Custom Fields

• Company Custom Fields

• Tags

• Lead Source

Post-Installation

After a saved search is installed:

• It appears in the destination app's saved search list

• All users with appropriate permissions can access and use the saved search

• Users can modify or customize the saved search in their own app

• The saved search functions independently and doesn't sync back to the source

Duplicate Saved Search Handling

When installing saved searches through the Solution Launchpad, the system uses the following logic to handle duplicates:

• Previously installed from SLP: Installation is skipped and the existing saved search remains unchanged, even if the search criteria in the bundle has been updated since the original install.

• Matching name and criteria: Installation is skipped since an identical saved search already exists.

• Same name, different criteria: The saved search is installed with a number appended to the name (e.g., "Hot Leads 1") to make it unique.

• No conflict: The saved search is installed as-is with no modifications.

Best Practices

• Use clear, descriptive names for saved searches to make them easy to identify

• Document any custom field or tag dependencies in your bundle description

• Test saved searches in multiple editions to ensure criteria work as expected

• Consider creating saved searches that use standard fields when possible to maximize compatibility