Aarki
Aarki S3 reads CSV and gzip-compressed CSV reports delivered by Aarki. It preserves campaign and creative granularity and the original report fields.
Source Setup Guide
To connect Aarki to Extract, you'll need to provide a Folder Name.
- Select Aarki S3 in Extract.
- Enter the Folder Name provided for your Aarki integration, as you would in Singular. Enter only the folder, without a bucket name or
s3://URL. - Complete source setup. The folder must contain a readable CSV report.
You do not need to enter an API key or password. Contact Extract support if setup reports that partner access is not configured.
Connection Setup Guide
After connecting Aarki to a destination, configure the connection:
- Connection Pull Schedule: How frequently Extract pulls data from Aarki.
- Destination-specific settings: Settings such as dataset name or target schema (depends on destination).
- Schema Migration Policy: How Extract handles schema changes from the source.
Report Updates
The first sync reads all available reports in the folder. Later syncs read new or updated reports based on their S3 modification time.
For each date, the newest report containing that date supplies all its rows. Extract replaces the destination's data for that date, including removing rows that are absent from the newer report. It does not add overlapping reports together or aggregate rows. Each report must therefore contain complete data for every date it includes.
Aarki delivers one report per day with a filename pattern of Stats for YYYYMMDD.csv.gz. Replaying an unchanged report replaces the same date's rows without appending duplicates.
A malformed report fails the run without advancing sync progress. Once the report is corrected, the next run retries it.
Deleting a source object or delivering a header-only file does not clear existing destination dates.
Schema ERD
Explore the interactive entity relationship diagram for Aarki.
Data Streams
reports
Daily cost reports with campaign and creative granularity. Reports must include date and cost headers. Missing optional values become null. Invalid dates or numbers, duplicate normalized headers, and inconsistent CSV column counts fail the sync.