| What you need to know |
New media source
- The new media source is
onedigitalturbine_int.
Campaign reporting dimensions
- Reporting shifts from Campaign/Campaign ID to Adset/Adset ID.
- This affects cohort and LTV reporting.
Reporting during the transition
- Select both media sources (
digitalturbine_int and onedigitalturbine_int) when reviewing reports during the transition period.
- Review any custom dashboards, BI integrations, or saved reports that reference the legacy PID, since they won't automatically pick up the new PID.
|
| What you need to do |
- Generate new attribution links using the DT<>AppsFlyer Integration Guide, and send them to your DT Account Manager.
- DT will migrate your campaigns to the new links. You don't need to recreate them manually.
Keep your legacy integration active until your lookback window expires, so in-flight conversions still attribute correctly. On the day you transition, switch cost reporting to DT's Unified Reporting API only. Do this as soon as onedigitalturbine_int is live, and avoid running both at once to prevent double-counting spend.
Reporting API and cost data
- Transition from the legacy Reporting API to DT's Unified Reporting API to avoid duplicate data.
- InCost is configured at the account level.
- The app-level Cost tab is being phased out for migrated networks.
- Account-level API authentication is required under the
onedigitalturbine_int partner setup.
- No Client ID or Secret is needed for cost data. AppsFlyer receives it directly from DT. What's changed is the setup flow: Cost integration used to be enabled per app, and now it's configured once at the account level for multiple apps.
Migration deadline
- The deadline is October 1, 2026. Generate your new links as soon as possible.
- DT will monitor delivery and cost data after the migration.
- If you run into issues, contact AppsFlyer Support or your CSM, or reach out to your DT Account Manager.
|