Skip to contentSkip to navigationSkip to topbar
Page toolsOn this page
Looking for more inspiration?Visit the

Qualified Destination


Destination Info
  • Accepts Page, Alias, Group, Identify and Track calls.
  • Refer to it as Qualified in the Integrations object
  • This integration is partner owned. Please reach out to the partner's support for any issues.
  • This destination is in Beta

Qualified(link takes you to an external page) is an agentic marketing platform designed for B2B organizations. The platform's AI Sales Development Representative (SDR) agent, Piper, automates tasks across both website and email channels, such as capturing leads, nurturing prospects, and converting buyers. Use Qualified to increase lead conversions, generate more meetings, and improve efficiency within your inbound-pipeline motion.

This destination is maintained by Qualified. For any issues with the destination, contact the Qualified support team.


Getting started

getting-started page anchor
  1. From your workspace's Destination catalog page(link takes you to an external page), search for "Qualified".
  2. Select Qualified, and then click Add Destination.
  3. Select an existing source to connect to Qualified.
  4. In your Qualified API settings(link takes you to an external page), create and copy the API Key.
  5. Paste the API Key in the destination settings in Segment.

Property nameTypeRequiredDescription
API Keypassword
required

Your Qualified API Key. When creating the API Key in Qualified make sure to select all scopes.


Build your own Mappings. Combine supported triggers with the following Qualified-supported actions:

(information)

Mapping limits per destination

Individual destination instances have support a maximum of 50 mappings.

Update Company

update-company page anchor

Update all Leads withing a Company in Qualified.

Update Company is a Cloud action. The default Trigger is type = "track" and event = "Leads In Company Updated"

Property nameTypeRequiredDescription
DomainSTRING
required

The domain of the company to update.


String FieldsOBJECT

Optional

String, text or picklist field values to set on all Leads associated with the Company.


Boolean FieldsOBJECT

Optional

boolean / checkbox field values to set on all Leads associated with the Company.


Number FieldsOBJECT

Optional

Numeric / decimal field values to set on all Leads associated with the Company.

Send a Lead to Qualified, or update an existing Lead

Upsert Lead is a Cloud action. The default Trigger is type = "track" and event = "Lead Updated"

Property nameTypeRequiredDescription
EmailSTRING
required

The email address of the lead to upsert.


PhoneSTRING

Optional

The phone number of the lead to upsert.


CompanySTRING

Optional

The company name of the lead to upsert.


NameSTRING

Optional

The name of the lead to upsert.


String FieldsOBJECT

Optional

Additional string, text, picklist fields to set on the Lead.


Boolean FieldsOBJECT

Optional

Additional boolean / checkbox fields to set on the Lead.


Number FieldsOBJECT

Optional

Additional numeric / decimal fields to set on the Lead.


You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo(link takes you to an external page).

For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to false.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

(information)

Real-time to batch destination sync frequency

Real-time audience syncs to Qualified may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.