CS: Server Side Tracking (GTM)

Hi Kaufweise,

Thank you for sharing your experience. We truly understand how important accurate tracking is for ad-driven stores. At the same time, we want to provide full clarity because the situation described in the review does not reflect the complete support history or the actual technical findings during your implementation.

1. Support engagement was continuous from start to end:
Every message through Shopify support, WhatsApp, and email received a reply, most on the same day or the following working day. We shared recordings, screenshots, technical insights, and internal updates, and escalated the case to engineering multiple times. At no point was the case left unattended.

2. Attribution expectations and multiple payment flows were the root of the concern:
During our order-by-order review, many purchases were attributed to organic search, direct visits, email campaigns,or journeys without click identifiers. However, it was expected that every order should appear as a Google Ads conversion, which is not how attribution works on any analytics or advertising platform.

A conversion is counted only when the user journey contains a paid-ad click signal. If a purchase is driven by non-paid traffic, Google Ads does not count it as a conversion even though the order is real and fully tracked, this is standard behaviour across the industry.

Additionally, your store uses multiple payment methods, and for most of them tracking worked perfectly with our server-side setup. For new or non-standard payment providers that behave differently, Shopify delivers purchase event data differently, so we request details to enable full mapping. Once we receive the complete list of payment redirection behaviours, we can enable 100% tracking coverage across all methods as well.

3. Server-side tracking was working correctly on supported flows:
On all flows where Shopify provided the purchase event information through its native mechanism, server-side conversions were tracked and delivered successfully to Google Ads, Meta, and GA4. The missing events were tied to checkout flows that had not yet been mapped, not to a malfunction of the tracking system.

4. Multiple tracking tools were active at the start:
Initially, several pixel scripts and tracking apps were running simultaneously. These can override or duplicate tracking signals and create mismatches across Google Ads, Meta, and GA4. We highlighted this early and shared the steps required to stabilize performance.

We are still happy to complete the setup. If you would like to continue, we can:
- Audit every payment and checkout flow
- Finalize mapping for 100% purchase-event coverage
- Validate server events for all payment methods
- Ensure consistent conversion visibility across Google Ads, Meta, and GA4

Our goal has always been to help you get the performance expected from server-side tracking, and we are ready to bring everything to completion anytime.

Hi there,

Thank you for your feedback.

We are glad that our team were able to assist you with you.

Feel free to reach out to us with any tracking concerns you may have and we would be gladly assist you.

Hi there,

We are glad to hear that you are happy with our app and support.

Feel free to reach out to us in case of any assistance needed.