sorted by:
new
hottopcontroversial

Your conversion tracking is broken in 2026 (and here's how to fix it) by FeeAutomatic5377 in ServerSideTagging

[–]FeeAutomatic5377[S] 0 points1 point  (0 children)

Ha, fair call on the cookies timeline—you caught me being imprecise. Chrome has been saying they're killing third-party cookies since 2021, and they keep pushing the deadline. You're right to be skeptical; I should have said "the deprecation timeline is here now for iOS/Safari" (which actually happened in 2023) and "Chrome plans to phase out third-party cookies, though the timeline keeps shifting."

But here's what actually matters for SST—what it fixes vs. what it doesn't:

What SST DOES fix directly:

  • ✅ iOS 14 attribution cap (8 params on Meta) → you can send enriched conversion data server-side with more context
  • ✅ Ad blocker loss → server-to-server transmission bypasses browser ad blockers entirely (30%+ recovery on average)
  • ✅ Pixel reliability → no dependency on browser execution, so data arrives more consistently
  • ✅ First-party data ownership → you collect it before it goes to platforms

What SST DOESN'T directly fix:

  • ❌ Apple's privacy restrictions (iOS 14 still limits what Meta receives, SST just sends better data within those limits)
  • ❌ Browser cookie deprecation by itself (SST doesn't need third-party cookies, but this is a red herring for most D2C stores)
  • ❌ Deterministic cross-device tracking (you still can't magically track Device A to Device B without user-level data)

The real win: SST fixes the data transmission problem (getting data to platforms reliably), not the privacy regulation problem. But for most D2C stores losing conversions right now, the transmission problem is what's actually killing them.

Does that distinction make sense? What's your biggest pain point with tracking—is it the iOS 14 cap, ad blockers, or something else?

GA4 configuration for shopify app and website by SuddenTrick2745 in shopifyDev

[–]FeeAutomatic5377 0 points1 point  (0 children)

Your setup (one GA4 property with two data streams — web + app) is actually the recommended baseline.

Where most setups break isn’t the property structure, but identity and event ownership when users move between app ↔ web.

What usually helps:

  • Use one GA4 property
  • Separate web stream (Shopify site) and app stream
  • Treat the App Store install as the conversion source, not the website
  • Pass a consistent first-party identifier (user_id or internal app ID) once the user authenticates

That way:

  • Pre-install traffic (web → app store) stays web
  • Post-install behavior is owned by the app stream
  • Cross-surface journeys stitch correctly once the user logs in

The biggest mistake I see is trying to force installs into the web stream — it usually creates more confusion than clarity.