u/mr-ahmed-kamal

Hey everyone, would love a sanity check on my conversion tracking setup before I ship it.

My stack:

• Storefront: Next.js app on myexamplewebsite.com
• Checkout: Shopify-hosted checkout on shop.myexamplewebsite.com (subdomain)
• Customers browse on the Next.js side, hit "Proceed to Payment," and get handed off to Shopify checkout to complete the purchase.

I'm running Google Ads and want to track conversions reliably and attribute ROAS correctly. Instead of relying solely on the conversion linker (which I think drops GCLIDs in cross-domain / subdomain setups), I want to carry the GCLID end-to-end myself.

Setup I am proposing:

1. Visitor lands on the storefront from an ad → Google appends gclid to the URL.
2. I capture the GCLID and store it in a cookie.
3. When they add a product to the cart, a cart is created on the Shopify side.
4. I attach the GCLID to that cart (as a cart attribute).
5. They proceed to checkout → land on shop.myexamplewebsite.com → same cart, so the GCLID travels with it as an order attribute.
6. Order gets placed → GCLID is now stored on the order itself.
7. A Shopify webhook fires on orders/create and sends the conversion data (including GCLID) to the Google Measurement API server-side.

To me this feels bulletproof: the GCLID is persisted in actual order data rather than depending on cookies surviving a cross-subdomain redirect, and the server-side webhook means I'm not dependent on the user's browser making the conversion fire.

But I'm not deep in the GTM/ads tracking world, so I'd love to hear what you guys think.

Thanks in advance 🙏

Hey everyone, would love a sanity check on my conversion tracking setup before I ship it.

My stack:

• Storefront: Next.js app on myexamplewebsite.com
• Checkout: Shopify-hosted checkout on shop.myexamplewebsite.com (subdomain)
• Customers browse on the Next.js side, hit "Proceed to Payment," and get handed off to Shopify checkout to complete the purchase.

I'm running Google Ads and want to track conversions reliably and attribute ROAS correctly. Instead of relying solely on the conversion linker (which I think drops GCLIDs in cross-domain / subdomain setups), I want to carry the GCLID end-to-end myself.

Setup I am proposing:

1. Visitor lands on the storefront from an ad → Google appends gclid to the URL.
2. I capture the GCLID and store it in a cookie.
3. When they add a product to the cart, a cart is created on the Shopify side.
4. I attach the GCLID to that cart (as a cart attribute).
5. They proceed to checkout → land on shop.myexamplewebsite.com → same cart, so the GCLID travels with it as an order attribute.
6. Order gets placed → GCLID is now stored on the order itself.
7. A Shopify webhook fires on orders/create and sends the conversion data (including GCLID) to the Google Measurement API server-side.

To me this feels bulletproof: the GCLID is persisted in actual order data rather than depending on cookies surviving a cross-subdomain redirect, and the server-side webhook means I'm not dependent on the user's browser making the conversion fire.

But I'm not deep in the GTM/ads tracking world, so I'd love to hear what you guys think.

Thanks in advance 🙏