Adikteev Audiences
Overview
The Adikteev Audiences destination allows you to sync custom audience data to Adikteev for user targeting and re-engagement campaigns. You can either select an existing audience (segment) or create a new one per stream.
Adikteev specializes in app re-engagement and churn prediction, helping mobile marketers win back inactive users through personalized campaigns.
This page covers the Adikteev Audiences reverse ETL destination. Adikteev also supports a separate S3-based reporting source for pulling performance reports from Adikteev-managed S3 storage; that source is documented separately.
Authentication
To authenticate Adikteev, provide AWS credentials that have read access to Adikteev’s reporting bucket in S3.
You’ll need:
- AWS Access Key ID
- AWS Secret Access Key
These credentials must be permitted to list and read objects from Adikteev’s reporting bucket (for example, ak-client-reporting) under your assigned folder/prefix.
Setup Guide
To connect Adikteev Audiences, you'll need:
| Parameter | Required | Description |
|---|---|---|
email | Yes | Your Adikteev account email |
password | Yes | Your Adikteev account password |
Contact your Adikteev account representative to obtain credentials. For more details, see Adikteev's Audiences API documentation.
Stream Configuration
Each stream targets one Adikteev audience (segment). You can:
- Select an existing audience from the
audience_selectiondropdown (populated dynamically from your Adikteev account), or - Choose Create new audience... and provide an
audience_name
The platform (iOS/Android) and identifier type are determined by the data contract you select for the stream.
Stream parameters
| Parameter | Required | Description |
|---|---|---|
audience_selection | Yes | Select an existing Adikteev segment, or choose Create new audience... |
audience_name | Conditional | Required only when audience_selection is Create new audience.... Used to create (or reuse) a segment with the same name and platform. |
Sync Behavior
This destination supports Replace mode with Full Refresh streams only. Each sync replaces the entire audience membership with the identifiers from your source data.
- Diffing is not supported (Adikteev uploads replace the full audience)
- If creating a new audience with zero records, the audience creation is skipped
- If an audience with the same name and platform already exists, it will be reused instead of creating a duplicate
Identifier normalization
Device IDs are normalized automatically based on the selected data contract:
- iOS (IDFA): converted to uppercase
- iOS (IDFV): preserved as-is
- Android (GAID): converted to lowercase
Configuration
Provide the following configuration values when creating the Adikteev Audiences destination.
- API Key: Your Adikteev API key.
- API Secret: Your Adikteev API secret.
- Advertiser ID: The Adikteev advertiser identifier where audiences will be created/updated.
- Environment: Select the Adikteev environment to send data to (for example, production vs. sandbox), if applicable in your account.
After saving, run a test sync to confirm the credentials are valid and the destination can create/update audiences for the specified advertiser.
Data Contracts
Choose the appropriate data contract based on your target platform and identifier type:
android_gaid_audience
ios_idfa_audience
ios_idfv_audience
Streams
This destination provides a single stream type: Audience membership upload.
For each stream run:
- The connector resolves the target audience:
- Uses the selected existing segment, or
- Creates/reuses a segment by
audience_name+ platform
- The connector uploads the full set of identifiers from the stream using replace semantics.
Supported identifiers depend on the selected data contract (Android GAID, iOS IDFA, iOS IDFV).