Qualified

Sync leads and companies to Qualified for AI-powered pipeline generation, conversational sales, and website visitor intelligence. Zeotap pushes data from your warehouse into Qualified via their bulk REST API, enabling you to enrich visitor profiles with CRM data, firmographic attributes, and custom properties for real-time buyer engagement.

Prerequisites

• A Qualified account on an Enterprise plan with bulk API access
• An API key generated from the Qualified dashboard with Enterprise bulk access permissions
• For lead syncs: email addresses that serve as the primary identifier
• For company syncs: company domains that serve as the primary identifier

Authentication

Qualified uses API Key authentication with Bearer tokens.

1. Log in to your Qualified account at app.qualified.com 
2. Navigate to Settings > API
3. Generate a new API key with Enterprise bulk access permissions
4. Copy the API key immediately — store it securely as it may not be shown again
5. Paste it into the API Key field in Zeotap

Your API key must have Enterprise bulk access permissions to use the bulk endpoints required by Zeotap. Standard API keys without bulk access will fail during the connection test.

Configuration

No additional configuration fields are required beyond authentication and target settings.

Target Settings

When Object Type is “Leads”

Lead data is sent to Qualified via the bulk leads endpoint. Each lead is upserted by email address — new leads are created, and existing leads (matched by email) are updated. You can map standard fields like first_name, last_name, title, and phone, as well as custom properties that have been created in Qualified.

When Object Type is “Companies”

Company data is sent to Qualified via the bulk companies endpoint. Each company is upserted by domain — new companies are created, and existing companies (matched by domain) are updated. You can map fields like company_name, industry, website, and custom properties.

Supported Operations

Sync Modes

Qualified’s bulk API is inherently upsert — records are matched by their primary identifier (email for leads, domain for companies) and created or updated accordingly.

Audience Sync Modes

Qualified does not expose a list or segment membership API. Segments in Qualified are computed dynamically based on visitor attributes and behavior — membership cannot be managed directly via the API.

Features

• Field Mapping: Yes
• Schema Introspection: No

Required Mapping Fields

Default Destination Fields

How It Works

Lead Syncs

1. Zeotap extracts lead data from your model or audience
2. Rows are grouped into bulk jobs of up to 500 records each
3. Each bulk job is sent to the Qualified bulk leads endpoint (POST /bulk/leads)
4. Leads are matched by email address — new leads are created, existing leads are updated (upsert behavior)
5. Mapped fields are sent as-is; custom fields must exist in Qualified before syncing
6. Per-record errors are captured and reported individually in the sync results

Company Syncs

1. Zeotap extracts company data from your model
2. Rows are grouped into bulk jobs of up to 500 records each
3. Each bulk job is sent to the Qualified bulk companies endpoint (POST /bulk/companies)
4. Companies are matched by domain — new companies are created, existing companies are updated
5. Mapped fields are sent as-is; custom fields must exist in Qualified before syncing
6. Per-record errors are captured and reported individually

Rate Limits

Qualified enforces account-specific rate limits on the bulk API. General guidelines:

• Batch size: Up to 500 records per bulk API request
• Rate limit response: HTTP 429 when limits are exceeded
• Retry behavior: HTTP 429 and 503 responses trigger automatic retries with exponential backoff

Zeotap automatically handles rate limiting with exponential backoff and retries. For persistent rate limit issues, contact Qualified support to discuss your account’s specific limits.

Best Practices

• Ensure your API key has Enterprise bulk access permissions before configuring the destination
• Create custom fields in Qualified before mapping them in Zeotap — field names are case-sensitive and must match exactly
• Use clean, validated email addresses for lead syncs — Qualified uses email as the primary deduplication key
• Use normalized domain names (e.g., acme.com without https:// or www.) for company syncs
• Start with a small test sync to verify field mapping before running full syncs
• Keep the number of mapped fields focused — only sync fields you actively use in Qualified for segmentation or routing
• Schedule syncs during off-peak hours if you are syncing large volumes to avoid rate limit pressure

Troubleshooting

Authentication failed

Verify your API key is valid, has not been revoked, and has Enterprise bulk access permissions. Standard API keys do not have access to the bulk endpoints required by Zeotap. Generate a new key from Settings > API in Qualified if needed.

Leads not appearing in Qualified

Ensure the email field is mapped and contains valid, non-empty email addresses. Qualified requires an email to create or match a lead. Check that the Object Type is set to Leads in the target settings.

Companies not appearing in Qualified

Ensure the domain field is mapped and contains valid company domains (e.g., acme.com). Qualified requires a domain to create or match a company. Verify the Object Type is set to Companies.

Rate limit errors (HTTP 429)

Qualified’s rate limits are account-specific. Zeotap retries automatically with exponential backoff. For persistent rate limit issues, reduce sync frequency or contact Qualified support to discuss higher limits for your account.

Custom fields not syncing

Custom fields must be created in Qualified before they can be synced. Field names are case-sensitive and must match exactly between your Zeotap mapping and the Qualified field definition. Verify field names in your Qualified account settings.

Duplicate leads

Duplicate leads occur when different email addresses refer to the same person. Qualified uses email as the primary deduplication key for leads synced via the bulk API. Ensure your source data uses consistent, canonical email addresses.

Connection timeout errors

Qualified bulk API calls have a 120-second timeout in Zeotap. If you see timeout errors, check your network connectivity and whether the Qualified API is experiencing downtime. Transient timeouts are retried automatically. Consider reducing the volume per sync if timeouts persist.

Field type mismatches

If field values are rejected, verify that the data types in your source match the expected types in Qualified. For example, numeric fields should not contain string values. Check the sync error details for specific field-level error messages.