← All connectors

Marketing · Source connector

Adikteev ELT Connector

Extract brings Adikteev marketing data into data warehouses and databases for analysis with the rest of your business data. Teams use it to compare channel performance, audience engagement, and campaign trends. Flexible scheduling keeps reporting current for routine analysis and time-sensitive decisions.

View setup guide
Adikteev logo

What teams use this connector for

Marketing performance analysis

Compare Adikteev channel, campaign, and engagement trends to identify opportunities for improvement.

Audience and content analysis

Use Adikteev data to understand which audiences, content, and activities contribute to engagement.

Cross-channel reporting

Combine Adikteev metrics with other marketing and business data for consistent performance reporting.

Flexible reporting cadence

Refresh Adikteev reporting every 15 minutes, hourly, daily, or on a custom schedule as business needs change.

Warehouse and database analysis

Use Extract to make Adikteev marketing data available in data warehouses and databases such as Snowflake, BigQuery, Redshift, and PostgreSQL for governed analysis.

Available streams

StreamDescriptionSync mode
daily_reportDaily campaign performance by app and campaignIncremental
country_daily_reportDaily campaign performance by app, campaign and countryIncremental
creative_daily_reportDaily campaign performance by app, campaign and creativeIncremental
creative_country_daily_reportDaily campaign performance by app, campaign, creative and countryIncremental

Data model at a glance

Preview the exported entities and fields for Adikteev.

Open full ERD

country_daily_report

  • app_idinteger
  • campaign_idinteger
  • country_keystring
  • datestring
  • _singular_extract_timestampstring
  • app_namestring
  • app_store_idstring
  • bundle_identifierstring

+12 more fields

creative_country_daily_report

  • app_idinteger
  • campaign_idinteger
  • country_keystring
  • creative_idinteger
  • datestring
  • _singular_extract_timestampstring
  • app_namestring
  • app_store_idstring

+17 more fields

creative_daily_report

  • app_idinteger
  • campaign_idinteger
  • creative_idinteger
  • datestring
  • _singular_extract_timestampstring
  • app_namestring
  • app_store_idstring
  • bundle_identifierstring

+14 more fields

daily_report

  • app_idinteger
  • campaign_idinteger
  • datestring
  • _singular_extract_timestampstring
  • app_namestring
  • app_store_idstring
  • bundle_identifierstring
  • campaign_namestring

+9 more fields

No verified relationships are available in this schema preview.

Why Extract for Adikteev

  • Rust-native performanceUse Rust-native data movement to refresh Adikteev reporting every 15 minutes, hourly, daily, or on a custom schedule as volume grows.
  • Full run transparencyInspect Adikteev API activity, execution steps, and timing in Extract's run-level logs when data needs review.
  • ELT + Reverse ETL in oneCombine Adikteev data with customer and finance models, then send approved outputs through a separately configured Reverse ETL destination.

Frequently asked questions

How does Extract handle incremental and full Adikteev syncs?

An incremental sync processes only new or changed data since a stored checkpoint or new date partition, while a full sync processes the complete selected dataset or date range again. By avoiding repeated processing and writes for the full dataset, incremental syncs can reduce destination database updates and warehouse compute costs. Daily partition replacement with a saved date cursor and configurable lookback. Extract records run details so teams can verify each sync.

Can I backfill historical Adikteev data with Extract?

Historical coverage for Adikteev: 7 days by default; explicit history within the last 24 months, through yesterday UTC. Use the setup guide and run details to confirm the available source records and selected settings.

How can teams monitor Adikteev data quality and freshness?

Compare expected reporting periods and record totals in your models, then use Extract's run-level logs to inspect Adikteev API activity, execution steps, and timing. This helps teams distinguish a source-data delay from a failed or incomplete run.

How often can Extract sync data from Adikteev?

Extract supports schedules every 15 minutes, hourly, daily, or on a custom cadence. Teams can choose a frequency that matches routine reporting, time-sensitive monitoring, or operational activation needs.

What does the Adikteev data model look like in the destination?

The Available streams table describes the datasets Extract can read from Adikteev. The inline schema previews entities and fields. Only relationships verified from the exported schema are shown. Use the full schema link for more details.