Conversion tracking and attribution for several media brands
Google Ads, Adobe Analytics, and the subscription shops reported different purchases. The causes included the purchase tracking and the websites' security settings.
- Context
- Media, several brands and subscription shops
- Focus
- Conversion tracking, troubleshooting, attribution
- Period
- 2025–2026
- Stack
- Google Ads
- Adobe Analytics
- Meta Pixel & CAPI
- Sourcepoint
Background
Several brands of a media company ran their own subscription shops on different website and checkout systems. Measurement used Google Ads conversions, Adobe Analytics, and Meta, with consent handled by Sourcepoint. Some shops were missing purchase conversions, and the numbers in Google Ads, Adobe, and the shops did not line up.
Implementation
The purchase tracking was repaired in several shops. Every purchase now carries a unique transaction ID, so purchases can be deduplicated and compared across systems.
On some pages, the website’s security settings prevented Adobe scripts and the consent settings from loading completely. The required change was documented for the development team. The Sourcepoint configuration on staging was aligned with production so that tests there show the same behavior.
For Meta, a concept combining the pixel with a first-party gateway for the Conversions API was created for use by all brands.
The comparison between systems took consent, reporting times, and attribution rules into account.
Result
Purchase conversions are captured again in all affected shops, and the remaining differences between the systems are explained.