For the complete documentation index, see llms.txt. This page is also available as Markdown.

Changes to data exports (Export API & custom exports)

As part of our platform migration, the data source used for exports is evolving. This page explains what stays the same and what will change for your exports, whether they run through the Export API or as a custom export.

What isn't changing

We've done compatibility work to guarantee full continuity of your exports:

  • your exports keep running with no interruption;

  • the format of the files and responses stays identical;

  • no action is required on your side to maintain your existing flows.

This remains true even after the legacy installation bases (MEP/legacy) are retired and the v1 push is discontinued.

What will change

Starting [DATE — TBD], the data source for exports will switch from the installation base to the Profiles base. The flow and format are preserved, but this change of source introduces a few functional differences to anticipate.

1. Advertising ID (IDFA/GAID) — empty values

The Advertising ID (IDFA/GAID) is no longer indexed in the new source, so the corresponding field will always be returned empty in your exports.

2. Smart Segments — empty values

Smart Segments are no longer available for export and will return empty values.

3. Exported volumes — likely decrease

The number of exported profiles (both API and custom exports) will likely decrease. By default, the Profiles base only retains profiles active over the last 13 months; profiles that have been inactive for longer are no longer included in exports. This retention period (TTL) is configurable on request — contact your CSM if you need a longer window.

When?

This change takes effect on [DATE — TBD]. Until then, nothing changes for your exports.

Questions?

For any question about the impact on your use case, or to adjust the retention period, reach out to your CSM.