Adikteev
Sync audience segments to Adikteev for mobile app retargeting and user acquisition campaigns. Upload device advertising IDs (GAID, IDFA, or IDFV) from your warehouse to Adikteev’s audience platform for precise mobile targeting.
Prerequisites
- An Adikteev account with API access
- Your Adikteev account email and password
- Your Adikteev Company ID (provided by your account manager)
- Device advertising IDs (GAID for Android, IDFA/IDFV for iOS) available in your data warehouse
Permissions
Your Adikteev account must have permission to create and manage audience segments via the Audiences API. Contact your Adikteev account manager to ensure API access is enabled.
Authentication
Adikteev uses OAuth2 Resource Owner Password authentication. Zeotap automatically obtains and manages access tokens using your credentials.
- Enter your Adikteev account Email address
- Enter your Adikteev account Password
- Zeotap will automatically obtain an OAuth2 access token (valid for 30 days) and refresh it as needed
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
| Company ID | Text | Yes | Your Adikteev company identifier. Contact your Adikteev account manager to obtain this value. |
| Platform | Select | Yes | The mobile platform for this audience. Choose Android (GAID) for Google Advertising IDs, iOS (IDFA) for Apple Identifier for Advertisers, or iOS (IDFV) for Apple Identifier for Vendors. Each platform requires a separate audience. |
Target Settings
| Field | Type | Required | Description |
|---|---|---|---|
| Audience Name | Text | Yes | Name for the Adikteev audience segment to create. |
| Audience ID | Text | No | Existing Adikteev audience/segment ID to update. Leave blank to create a new audience automatically. |
Supported Operations
Sync Modes
Adikteev is an audience-only destination and does not support standard data sync modes.
Audience Sync Modes
| Mode | Supported | Description |
|---|---|---|
| Add | Yes | Upload device IDs to the audience. Each upload replaces the full device list. |
| Mirror | Yes | Sync the complete audience membership, automatically excluding removed members. |
| Remove | — | Not supported. Use Mirror mode to manage removals. |
| Upsert | — | Not supported. Use Add mode instead. |
Features
- Field Mapping: No
- Schema Introspection: No
Required Mapping Fields
No explicit field mapping is required. Zeotap automatically detects device advertising IDs from common column names: device_id, advertising_id, idfa, gaid, idfv.
How It Works
- Zeotap authenticates with Adikteev using your email and password to obtain an OAuth2 access token
- If no Audience ID is provided, Zeotap creates a new audience segment via the Adikteev API
- Device advertising IDs are extracted from your data and normalized for the selected platform:
- Android: GAIDs are lowercased
- iOS (IDFA): IDFAs are uppercased
- iOS (IDFV): IDFVs are uppercased
- IDs are uploaded as plain text (newline-separated) to the Adikteev Audiences API
- Important: Each upload replaces the previous device list for the audience — Adikteev does not support incremental add/remove operations
Rate Limits
Adikteev does not publish specific API rate limits. Zeotap uploads the full device list in a single request per sync. For very large audiences, contact your Adikteev account manager to confirm capacity.
Best Practices
- One audience per platform: Adikteev requires separate audiences for Android and iOS. Create two destinations in Zeotap if you need both.
- Use Mirror mode: Since each upload replaces the full audience, Mirror mode ensures your Adikteev audience always matches your warehouse segment exactly.
- Use unhashed IDs: Unlike other ad platforms, Adikteev requires raw (unhashed) device advertising IDs. Do not pre-hash your IDs.
- IDFV for broader reach: For iOS campaigns, consider using IDFV instead of IDFA to maximize reach via Adikteev’s probabilistic retargeting methods.
- Schedule regular syncs: Set up daily or weekly syncs to keep your Adikteev audiences fresh and in sync with warehouse changes.
- Validate device IDs: Ensure your device ID column contains valid advertising identifiers. Invalid or empty IDs are silently skipped.
Troubleshooting
Authentication failed: invalid email or password
Verify your Adikteev account email and password are correct. Ensure your account has API access enabled. Contact your Adikteev account manager if you cannot log in.
Company ID not found
Confirm your Company ID with your Adikteev account manager. The Company ID is a numeric identifier specific to your organization.
Audience creation fails
Ensure your account has permission to create audience segments. Verify the platform selection is correct (Android or iOS). Check that the audience name does not already exist.
No device IDs found in batch
Zeotap looks for device IDs in columns named device_id, advertising_id, idfa, gaid, or idfv. Ensure your source model includes a column with one of these names containing valid device advertising IDs.
Upload returns HTTP 401
Your OAuth2 access token may have expired. Zeotap automatically obtains a new token at the start of each sync. If this error persists, verify your credentials are still valid.
Platform mismatch errors
Each Adikteev audience is platform-specific. Ensure you are uploading the correct ID type for the selected platform: GAIDs for Android, IDFAs or IDFVs for iOS. Mixing ID types will result in targeting errors.