StackAdapt

Sync your warehouse audiences to StackAdapt for programmatic advertising. Zeotap uploads audience profiles to StackAdapt CRM segments via the GraphQL API, enabling precise targeting across display, native, video, and connected TV campaigns.

Prerequisites

A StackAdapt account with API access enabled
A GraphQL API token (contact your StackAdapt account manager to obtain one)
Your StackAdapt Advertiser ID

Permissions

Your GraphQL API token must have WRITE scope for the target advertiser. You can verify token permissions in the StackAdapt API portal under token management.

Authentication

StackAdapt uses a GraphQL API Token for authentication.

Contact your StackAdapt account manager to request a GraphQL API token
In Zeotap, navigate to Destinations and click Add Destination
Select StackAdapt from the Advertising category
Enter your API Token in the credentials section

Configuration

Field	Type	Required	Description
Advertiser ID	Text	Yes	Your StackAdapt advertiser ID. Found in your StackAdapt account settings.

Target Settings

Field	Type	Required	Description
Segment Name	Text	Yes	Name for the CRM audience segment in StackAdapt. This is how the audience appears in the StackAdapt platform.

Supported Operations

Sync Modes

This destination is audience-only and does not support standard data sync modes.

Audience Sync Modes

Mode	Supported	Description
Add	Yes	Add profiles to the audience segment
Upsert	Yes	Add or update profiles in the audience segment
Remove	—	StackAdapt does not support removing users from CRM audiences via the API
Mirror	—	Not supported (removal not available)

Features

Field Mapping: Yes
Schema Introspection: No

Required Mapping Fields

Field	Description	Alternatives
Email	Email address for audience matching	`hashed_email`

StackAdapt requires at least an email address for profile matching. You can provide either a plaintext email or a pre-hashed email (hashed_email).

Default Destination Fields

Field	Type	Description
`email`	string	Email address
`first_name`	string	User’s first name
`last_name`	string	User’s last name
`phone`	string	Phone number
`city`	string	City
`state`	string	State or province
`zip_code`	string	Postal or zip code
`address`	string	Street address

Providing additional PII fields beyond email improves match rates in StackAdapt.

How It Works

Zeotap extracts audience profiles from your warehouse model
Profiles are mapped to StackAdapt’s PII fields (email, name, phone, address)
Profiles are uploaded to StackAdapt via the GraphQL upsertProfiles mutation in batches of up to 1,000
StackAdapt processes the profiles and adds them to the specified CRM audience segment
The audience segment becomes available for targeting in StackAdapt campaigns

Rate Limits

StackAdapt’s GraphQL API enforces rate limits on API token usage. Zeotap handles rate limiting automatically with exponential backoff and retry logic. If you experience throttling, consider reducing sync frequency or contact StackAdapt support to increase your API rate limits.

Best Practices

Provide multiple PII fields — Including first name, last name, and phone alongside email significantly improves match rates
Use descriptive segment names — Segment names appear in the StackAdapt UI, so use clear, descriptive names like “High-Value Q1 Purchasers”
Schedule syncs during off-peak hours — For large audiences, schedule syncs during off-peak hours to minimize API throttling
Monitor match rates — Check audience sizes in StackAdapt after syncs to verify match rates are within expected ranges

Troubleshooting

Authentication failed: invalid API token

Verify your GraphQL API token is correct and has not expired. StackAdapt periodically rotates API tokens. Contact your StackAdapt account manager for a new token if needed.

Advertiser ID not found

Ensure the Advertiser ID matches an advertiser your API token has WRITE scope for. You can verify token scopes in the StackAdapt API portal.

Low match rates

StackAdapt matches profiles using PII fields. To improve match rates:

Ensure email addresses are valid and properly formatted
Include additional PII fields (first name, last name, phone, address)
Verify data is not stale or outdated

Sync appears successful but audience is empty

CRM audience segments may take several hours to process after upload. Wait 4-6 hours before checking audience sizes in StackAdapt.

Rate limit errors

If you see 429 errors in sync logs, Zeotap automatically retries with exponential backoff. For persistent rate limiting, reduce sync frequency or contact StackAdapt support to increase your API limits.

GraphQL errors in sync logs

GraphQL errors typically indicate malformed data. Check that:

All email addresses are properly formatted
Phone numbers use a valid format (E.164 recommended)
No fields contain excessively long values

Taboola The Trade Desk