Kayzen
Sync first-party audience segments to Kayzen for mobile in-app programmatic advertising. Zeotap uploads device IDs (IDFA/GAID) to Kayzen audiences via the Audience API, enabling precise targeting for customer acquisition, retargeting, and brand performance campaigns.
Prerequisites
- A Kayzen account with API access enabled
- An API key (contact your Kayzen account manager to obtain one)
- Device advertising identifiers (IDFA or GAID) available in your warehouse
Permissions
Your API key must have permission to create and manage audiences. Contact your Kayzen account manager to verify your API key has the required scope.
Authentication
Kayzen uses an API Key for authentication.
- Contact your Kayzen account manager to request an API key
- In Zeotap, navigate to Destinations and click Add Destination
- Select Kayzen from the Advertising category
- Enter your API Key in the credentials section
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
| Tracking Partner | Text | Yes | The partner name identifying who is conducting the audience edit. Typically your company or MMP name. |
Target Settings
| Field | Type | Required | Description |
|---|---|---|---|
| Audience Name | Text | Yes | Name of the Kayzen audience to create or update. If the audience does not exist, it will be created automatically. |
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 device IDs to the audience |
| Remove | Yes | Remove device IDs from the audience |
| Mirror | Yes | Full sync — adds new devices and removes devices no longer in the source |
| Upsert | — | Not applicable for device list management |
Features
- Field Mapping: Yes
- Schema Introspection: No
Required Mapping Fields
| Field | Description |
|---|---|
| Device ID | A device advertising identifier — IDFA (iOS) or GAID (Android) |
Default Destination Fields
| Field | Type | Description |
|---|---|---|
device_id | string | Device advertising identifier (IDFA or GAID) |
device_id_type | string | Type of device identifier: idfa, gaid, or sha1 |
How It Works
- Zeotap extracts audience members and their device identifiers from your warehouse model
- On the first sync, Zeotap creates a new audience in Kayzen using the specified audience name (or finds an existing one with the same name)
- Device IDs are chunked into batches of up to 2,000 (the Kayzen API limit per request)
- Each batch is sent to the Kayzen
/v1/au/listupdateendpoint with the appropriate action (ADD or REMOVE) - For mirror syncs, Zeotap computes a diff and sends ADD requests for new members and REMOVE requests for members no longer in the source
- The audience becomes available for targeting in Kayzen campaigns
Rate Limits
The Kayzen Audience API enforces a limit of 2,000 device IDs per API request. Zeotap automatically chunks larger audiences into compliant batches. Each audience can hold up to 300 million device IDs.
Device IDs added to an audience expire after 6 months if not refreshed. Schedule regular syncs to keep your audiences current.
Best Practices
- Use consistent device ID formats — IDFA should be uppercase with hyphens, GAID should be lowercase with hyphens. Kayzen also accepts SHA1-hashed device IDs (40 hex characters).
- Schedule regular syncs — Device IDs expire after 6 months in Kayzen. Weekly or bi-weekly syncs prevent audience decay.
- Use descriptive audience names — Audience names appear in the Kayzen platform, so use clear names like “High-Value US Shoppers” or “Lapsed Users 30d”.
- Monitor audience sizes — After syncs, verify audience sizes in the Kayzen platform match your expectations.
- Provide device ID type — While optional, including
device_id_type(idfa, gaid, or sha1) improves matching accuracy.
Troubleshooting
Authentication failed: invalid API key
Verify your API key is correct. Kayzen API keys are long alphanumeric strings. Contact your Kayzen account manager if you need a new key.
Audience creation failed
Ensure your API key has permission to create audiences. If the audience name contains special characters, try using only alphanumeric characters and underscores.
No device IDs in batch
Zeotap skips rows where the device_id field is empty or null. Verify your model returns valid device identifiers for all audience members.
Device IDs not appearing in audience
Kayzen processes device ID uploads asynchronously. Allow 15-30 minutes after a sync completes before checking audience membership in the Kayzen platform.
Sync succeeds but audience size is smaller than expected
This can happen when device IDs are in an invalid format. Verify that:
- IDFA values are uppercase with hyphens (e.g.,
AAAAAA-BBBB-CCCC-1111-222222222222) - GAID values are lowercase with hyphens
- SHA1 hashes are exactly 40 hexadecimal characters
Rate limit errors during large syncs
Zeotap automatically retries failed requests with exponential backoff. For very large audiences (millions of devices), consider scheduling syncs during off-peak hours or splitting into multiple smaller audiences.