The client (I could not find the actual client name or task link) had test.com (the main domain) and test.booking.com (a booking subdomain). Users could move between these domains. The main issue was that tracking consent was only set up for test.com. This meant that users who visited test.booking.com and then went to test.com to complete a conversion often had their conversions incorrectly counted as direct traffic. This happened because users needed to accept consent before the tracking tags could work. As a result, many conversions from Google Ads or marketing campaigns were miscounted.
To solve the tracking issues, we recommended the following solution, which needed approval from the client’s compliance team:
Successfully resolved cross-domain consent issues affecting conversion attribution for a client with two domains, leading to improved accuracy in reporting and better insights into campaign performance.