# Qualified Destination

## Destination Info

* Accepts [Page](/docs/segment/connections/spec/page), [Alias](/docs/segment/connections/spec/alias), [Group](/docs/segment/connections/spec/group), [Identify](/docs/segment/connections/spec/identify), [Track](/docs/segment/connections/spec/track) calls.
* Refer to it as **Qualified** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object)
* This integration is **partner owned.** Please reach out to the partner's support for any issues.
* This destination is **Beta.**

[Qualified](https://qualified.com/?utm_source=segmentio\&utm_medium=docs\&utm_campaign=partners) 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](mailto:help@qualified.com).

## Getting started

1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog), 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](https://app.qualified.com/settings/api-keys), create and copy the **API Key**.
5. Paste the **API Key** in the destination settings in Segment.

## Destination Settings

| Field   | Description                                                                                    | Required | Type     |
| ------- | ---------------------------------------------------------------------------------------------- | -------- | -------- |
| API Key | Your Qualified API Key. When creating the API Key in Qualified make sure to select all scopes. | Yes      | password |

## Available Actions

Build your own Mappings. Combine supported [triggers](/docs/segment/connections/destinations/actions/#components-of-a-destination-action) with the following Qualified-supported actions:

> \[!NOTE]
>
> Individual destination instances have support a maximum of 50 mappings.

* [Update Company](#update-company)
* [Upsert Lead](#upsert-lead)

### Update Company

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"`

| Field          | Description                                                                            | Required | Type   |
| -------------- | -------------------------------------------------------------------------------------- | -------- | ------ |
| Domain         | The domain of the company to update.                                                   | Yes      | STRING |
| String Fields  | String, text or picklist field values to set on all Leads associated with the Company. | No       | OBJECT |
| Boolean Fields | boolean / checkbox field values to set on all Leads associated with the Company.       | No       | OBJECT |
| Number Fields  | Numeric / decimal field values to set on all Leads associated with the Company.        | No       | OBJECT |

### Upsert Lead

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"`

| Field          | Description                                                  | Required | Type   |
| -------------- | ------------------------------------------------------------ | -------- | ------ |
| Email          | The email address of the lead to upsert.                     | Yes      | STRING |
| Phone          | The phone number of the lead to upsert.                      | No       | STRING |
| Company        | The company name of the lead to upsert.                      | No       | STRING |
| Name           | The name of the lead to upsert.                              | No       | STRING |
| String Fields  | Additional string, text, picklist fields to set on the Lead. | No       | OBJECT |
| Boolean Fields | Additional boolean / checkbox fields to set on the Lead.     | No       | OBJECT |
| Number Fields  | Additional numeric / decimal fields to set on the Lead.      | No       | OBJECT |

## Engage

You can send computed traits and audiences generated using [Engage](/docs/segment/engage) to this destination as a **user property**. To learn more about Engage, schedule a [demo](https://segment.com/contact/demo).

For user-property destinations, an [identify](/docs/segment/connections/spec/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.

> \[!NOTE]
>
> 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.