Data Export
Data Export is the screen where you export the advertising identifiers (ADIDs) of your ad audience to CSV, based on collected events. You access it from the left menu under Events > Data Export, then proceed in the following order: set the extraction conditions, check the audience size in advance (Preview Count), and download the CSV (Download CSV). The exported CSV can be used to upload Custom Audiences to ad platforms such as Meta, Google, and TikTok.
1. Export Flow
- In the left
Filterpanel, configure the audience preset, period, platform, CSV preset, and hash format. - Click the
[Preview Count]button to check the audience to be extracted (the number of unique ADIDs per platform). - Review the Total, Android, and iOS figures in the result table on the right.
- Click the
[Download CSV]button to download the file.
If the audience is 0, the [Download CSV] button is disabled. Adjust the period or preset and run the preview again.
2. Filter Items
| Item | Description |
|---|---|
Audience Preset | The type of user group to extract (see the table below). |
Date Range | The event aggregation period. The default is the last 90 days. |
Platform | Choose from All / Android / iOS. |
Dormancy period (inactive) | Shown only when the Dormant Users preset is selected. This is the reference number of days with no activity; the default is 30 days (minimum 7 days, maximum 365 days). |
Ad Platform CSV Preset | The column format of the CSV to download (see the table below). |
Hash Format | Choose whether to hash the ADID with SHA256 or export it as Plain text. |
Audience Presets
| Preset | Extraction Target |
|---|---|
| Installers | Devices that generated an install (install/first_open) event during the selected period. |
| Purchasers | Devices that generated a purchase (purchase/first_purchase) event during the selected period. |
| Installed Non-Purchasers | Devices that installed but did not purchase during the selected period (Installers minus Purchasers). |
| Dormant Users | Devices that have not generated any event during the most recent Dormancy period after installation. |
Ad Platform CSV Presets
The column composition of the CSV varies depending on the preset you select.
| Preset | CSV Columns | Notes |
|---|---|---|
| Meta (Facebook/Instagram) | madid | Combines IDFA (iOS) and GAID (Android) into a single column. |
| Google Ads | Mobile Device ID | A single column. |
| TikTok Ads | IDFA, GAID | iOS values are placed in the IDFA column, and Android values in the GAID column, separately. |
| Custom (raw columns) | advertising_id, platform | Exports the advertising identifier and platform as-is. |
3. Hash Format (SHA256 Recommended)
| Format | Description |
|---|---|
| SHA256 (recommended by ad platforms) | Normalizes the ADID to lowercase, then hashes it with SHA256 before exporting. |
| Plain text | Exports the raw ADID as-is. |
Because Custom Audience uploads on ad platforms generally require hashed identifiers, we recommend SHA256 if you intend to upload to an external ad platform.
4. Preview Result Table
After running [Preview Count], the result table displayed on the right consists of the following columns.
| Column | Description |
|---|---|
| Platform | Divided into Total, Android, and iOS rows. |
| Ad ID Type | Total is shown as ADID, Android as GAID, and iOS as IDFA. |
| Unique ADIDs | The number of unique advertising identifiers with duplicates removed. |
| Ratio | The proportion that each platform accounts for relative to the total. |
5. Automatic Exclusion Rules
During extraction, devices with invalid advertising identifiers are automatically excluded from the audience.
| Exclusion Target | Description |
|---|---|
| No advertising identifier | Devices whose advertisingId is empty (null/blank value). |
| Zero-value IDFA | IDFA filled with zeros (00000000-0000-0000-0000-000000000000) because tracking consent was not obtained on iOS. |
| Platforms other than Android/iOS | Because extraction is based on advertising identifiers, only Android and iOS devices are aggregated. |
Due to these automatic exclusions, it is normal for the extracted audience to be smaller than the total number of events shown in real-time logs.

