Supersonic: a creative-level decision depends on a reliable cost join

Supersonic's public TikTok case describes joining platform activity with internal BI. The useful engineering question is whether the cost line and the creative line still refer to the same object.

What the public case establishes

AppsFlyer says Supersonic used APIs and Data Locker to populate internal BI, with cost aggregation supporting analysis of TikTok campaigns and individual creatives. The account also describes creative workshops and more rapid testing. It does not isolate the effect of the data integration from the wider creative process. AppsFlyer case study.

This debrief analyses a public customer case published by a commercial supplier. It is not an original UA Ledger interview. The chronology below follows the supplier’s account; we did not inspect the advertiser’s dashboards or interview its staff.

The decision worth examining

A creative dashboard is only as useful as the identifiers joining spend, delivery and outcomes. Renamed assets, duplicated campaigns or reused labels can silently merge different executions. An attractive low CPI may then belong to a reporting accident rather than a concept worth reproducing. The first decision is whether the record is trustworthy enough to brief production.

Use an immutable asset identifier distinct from its descriptive name, and preserve the mapping from each platform's object identifiers. A translated variant should share a concept family but retain its own file identity. The worksheet separates missing joins from poor performance, because an unjoined row should not be promoted to a winner or retired as a loser.

A usable next check

Reconcile a small authorised set of creative objects end to end: exported file, platform asset, campaign placement, spend and outcome record. Include a renamed item and a duplicated placement deliberately. Check that totals remain stable and that the intended family rollup can still be reproduced. Only after this passes should the team use the report to prioritise a creative refresh.

Download the populated case worksheet. Its control, variant and decision rules are a proposed experiment, not an account of results already measured. Keep the source URL with the worksheet when circulating it so reported findings cannot become unattributed team benchmarks.

Evidence boundary

We did not inspect Supersonic's BI or live API responses. Historic API and product references in the case are context, not current integration instructions, and the reported creative gains are not independently validated.

For background, see reading an mmp dashboard without fooling yourself and cohort quality checklist ua spend. These are existing archive discussions, not independent certification of this case. No first-hand campaign result is asserted.