Poorer tracking results

[Silicone]

We currently use the Google and YouTube app as the primary tracking method for Google Ads.
We have set up Stape as a secondary solution to first check the results of the server-side tracking.

For the events “added to cart” and “checkout started”, Stape consistently delivers better values - so more conversions are recorded, which is to be expected.

However, the actual orders show a different picture: Stape records fewer orders than the Google app.

We checked the logs at Stape - there is also only one order recorded, although two actually took place. So one order was not recorded correctly.

short infos:
1.the conversions naturally use the same attribution. (data-driven)

2. counting method: each conversion
3. all 3 tracking events use the consent mode

Our question:
How can we fix this problem so that server-side tracking via Stape works completely and reliably in the future? The aim is to use Stape as the primary tracking method in the long term.

[Alex]

If you see in the logs that not all purchases are registered, this indicates that something is wrong with your tracking settings.

With GA4, the most common problem is the initialisation of the measurement ID from several places at once. This could be gtag in the website code, GA4 integration enabled in Google app, or another Google tag in the container or in an additional container.

This problem causes the configuration to be overwritten and some events to be sent via sGTM, while others are sent directly to GA4. As a result, you will not see some events in the logs and Google Ads tags will not work.

Another common problem may be incorrect consent settings. In some cases, for example, the actual consent status at the time of purchase is unknown, which is why the tag does not work.