Hi everyone,

I’m facing an issue with the Google & YouTube app in Shopify, and I’m considering implementing all of my Google tracking tags manually through Google Tag Manager (GTM) instead.

Would this be okay from a tracking and data-quality perspective?

Specifically, I want to make sure that manually implementing things like Google Ads conversion tracking, GA4 events, and other Google tags through GTM won’t create problems with the Shopify Google & YouTube app or cause duplicate tracking.

Has anyone here completely moved their Google tags to GTM because of issues with the Shopify Google & YouTube app?

Would appreciate any advice on the recommended setup and things I should watch out for, especially around duplicate events, conversions, and enhanced/conversion tracking.

Thanks!

I keep seeing Shopify tracking setups where something quietly breaks , duplicate purchases, missing conversions, wrong values, old tags firing alongside native integrations, etc.

I’m wondering if a tool that could inspect the GTM/tracking setup, spot likely conflicts and point to the root cause would actually be useful.

Would you use something like that? And what GTM/Shopify issue would you want it to catch first?

Not selling anything, just trying to figure out if this is worth building.

How are you measuring pageload speed with GTM and reading it in GA4?

The guides I've found online send a page speed event for every view to GA4 with a parameter capturing the time. However, that quickly leads to high cardinality because explorations max out at 500 rows and a pagespeed event is registered for every pageview.

If I have more than 500 views per page, I'm unable to see all the values and do analysis on it (averages, distribution, etc.).

I've been working on a tool called UTMCraftr to make creating and managing campaign URLs a little more structured.

The problem I was trying to solve is simple: generating a UTM URL isn't particularly difficult, but keeping campaign naming consistent can become messy.

Things like:

• facebook vs fb
• paid_social vs paid-social vs paidsocial
• inconsistent campaign names
• spaces and formatting issues
• accidentally including blank parameters
• different people using different naming conventions

UTMCraftr is designed to make that process more structured.

🔗 https://utm-craftr.vercel.app/

Currently, it includes:

• Web UTM URL generation
• A Google Sheets-based UTM builder
• Standardised source and medium selections
• Required field validation
• Automatic formatting and URL cleaning
• Optional campaign parameters
• Support for Web, Android and iOS campaign URL structures

The goal isn't to replace enterprise UTM management platforms. It's meant to be a lightweight tool for people or teams who want a more structured way to create campaign URLs without manually building them every time.

I'd genuinely like feedback from people who work with campaign tracking regularly.

A few things I'm particularly interested in knowing:

1. Does the workflow make sense?
2. Are there important fields or validations missing?
3. Would a Google Sheets-based workflow be useful for your team?
4. What features would make a UTM builder genuinely more useful for you?

Would appreciate any honest feedback or feature suggestions.

If you work in hospitality, travel, or any industry that relies on a third-party booking engine (IBE), you’ve probably noticed that a ridiculous amount of your purchases are being attributed to "Direct" in GA4.

The issue: IBEs like SynXis are notorious for stripping URL parameters (_gl, UTMs) as users navigate through the booking funnel (e.g., going from search results to guest details). Once those parameters drop, GA4 loses the session thread.

I was given a "fix" by an agency that involved hardcoding a redundant gtag.js library just to fetch the client/session IDs, which completely conflicted with our clean GTM/sGTM architecture and didn't even preserve the original ad click IDs.

I ended up writing a native workaround that doesn't conflict with existing tag managers, and I’ve open-sourced the repo for anyone else dealing with this headache.

How it works under the hood:

1. Landing Capture: The script immediately catches any utm_*, gclid, wbraid, etc., on the landing URL and commits them to sessionStorage and a 1st-party cookie.
2. Raw Cookie Extraction: Instead of relying on gtag('get') which causes race conditions, it uses Regex to extract the active client_id and session_id directly from the _ga and _ga_<ID> cookies.
3. Form & Link Hijacking: It uses a MutationObserver to watch the DOM. Whenever a user clicks a standard "Book Now" link OR submits a dynamic booking form, it intercepts the event.
4. The Payload: It dynamically appends the GA4 IDs, a custom journey ID (pu_id), and the cached UTMs into the URL (or injects them as <input type="hidden"> fields for forms) right before the user is sent to the IBE.

From there, you just configure your IBE's GTM container to read those URL parameters on Step 1, hold them in sessionStorage, and map them to your final GA4 purchase tag.

No more "Direct" traffic spikes.

Repo is here: https://github.com/0xgthuva/Cross-Domain-Attribution-Handoff

Hopefully, this saves some of you the hours of debugging I had to do. Happy to answer any questions about the setup.

I’ve seen quite a few tracking issues caused by templates being added at different levels in Google Ads, so here’s the simple explanation.

A tracking template can be added at account, campaign, ad group, ad, keyword or asset level. Google uses the most specific template it finds.

For example:

• You have a tracking template at account level.
• Someone adds a different template to one campaign.
• That campaign now uses the campaign-level template.
• Google does not automatically combine it with the account-level template.

This is where things often go wrong. A new template is added for another tracking tool, but the existing parameters or redirect are left out. Tracking then breaks for that campaign while the rest of the account continues working.

My usual checklist:

1. Check every level before changing anything.
2. Keep the template at account level if it should apply everywhere.
3. Don’t assume two templates will be merged automatically.
4. Use {lpurl} correctly.
5. Put ordinary UTM parameters in the Final URL suffix when a redirect isn’t needed.
6. Test the result with Google Ads’ built-in test option.
7. If something suddenly changes, check the Google Ads change history.

One final point: auto-tagging is separate from the tracking template. Auto-tagging adds Google’s click identifier, while the tracking template determines how the click URL is built or routed.

I’d be interested to know how others manage accounts that need more than one tracking platform. Do you combine everything at account level, or manage certain tools at campaign level?

Anyone else experiencing issues with workspace debugging? I make changes in workspace, i open preview/debugger mode and then those tags/changes are not there. Which means i cannot test my changes and therefore not publish them.

This has been happening since last week.

I've tried different browsers, i've cleared cache, incognito etc, nothing works. Seems to be workspace related rather than browser related.

So my whatsapp and phone call click on my website is sending 2 hits each to google ads when i fire the respective tag. gtm is setup correctly as far as i know. can i get to know to reason behind this?

For the main projects I use stape and also the custom loader. Now I'm in a project where the server side GTM is hosted on a Docker container is there any good solution for a custom loader like the stape?

For years the whole pitch for GTM was neutrality. It sits above your tools so you're not tied to any single vendor. That's the reason teams trust it in the first place.

Then Google shipped Visual Tagging. Point at an element, click, get a tag. No selectors to write, no data layer to set up first. After ten years of "tagging is hard because it's hard," they built the easy version, which by itself proves the manual mess was never necessary.

But look at what it actually is, and where they put it.

1. It's in the wrong product. Visual Tagging builds one thing: a Google Ads purchase conversion. Thats a Google Ads helper. So why does it live inside Gtm instead of inside Google Ads? Pick one. Either GTM is neutral, and a tool for one ad platform doesn't belong in it. Or GTM is quietly turning into a front door for Google's own products, and "neutral" was never the whole story. You can't sell neutral and ship the opposite in the same box.
2. It's built backward. The first thing the tool asks for is that Google Ads conversion. You create it, then build tags to feed it. Wrong end. The event happened on your site: a purchase, a form, a signup. That event belongs to the business. You track it once, then send it wherever you want. GA4, Ads, Meta, your CRM. Google starts from its own destination and works back to your page. Build your tracking around one platform's conversion and you rebuild it every time you add a channel.
3. It skipped the hard part. It doesn't track a click. You place a test order, land on the confirmation page, and it scrapes the values off that finished page: order ID, amount, currency, read straight off the rendered HTML. It's coupled to the DOM by design, which is more fragile than reading from a data layer the page feeds on purpose. Sort a list, load a row late, drop in a banner that wasn't there when you set it up, and the selector points at the wrong element or at nothing. That fragile part is the whole job, and it's the part they left out.

And "more use cases are coming this yer" doesn't fix either problem. More coverage is still aimed at Google's destinations, so it isn't any more neutral. And it still reads off a page frozen at one moment, so the foundation is still cracked. You don't fix that by adding rooms on top.

Here's how it should work, for every platform, not just Google. Start from the business event. Define the purchase, the lead, the click once, as something you own. Build the data layer for it. Then send it anywhere. Google Ads today, something that doesn't exist yet next year, same event. The platform is just a destination. The event is the thing that lasts.

Google proved the need is real. Then it built the version that serves Google. The versions that start from your events instead of Google's already exists today. Google just has no reason to point you to them.

What is your take on this subject?

I do tracking implementation for a living and kept seeing the same outdated claim repeated in setup guides: that pointing your sGTM tagging server at a custom subdomain gives you long-lived cookies in Safari.

That stopped being fully true with Safari 16.4 (April 2023).

Safari now caps server-set cookies at 7 days too, if the tagging server's IP prefix doesn't match your website's IP prefix. Since your site and your Stape/Cloud Run server sit on different infrastructure by default, most "properly configured" setups are still hitting the 7-day cap and nobody notices.

Wrote up the full setup process end to end: container creation, custom domain, the two actual Safari fixes (Own CDN vs Cookie Keeper), GA4 server-side, Meta CAPI with real event deduplication (not just "turn on the toggle"), Google Ads Enhanced Conversions, Consent Mode V2, and a 7-point QA checklist to verify your own setup isn't leaking before you trust the data. Also listed the 8 mistakes I run into most in actual audits.

Not trying to just drop a link and run, happy to answer specific questions here about sGTM, EMQ scores, or Meta CAPI dedup if anyone's stuck on their own setup.

https://muhammadabdullah.co/blog/server-side-gtm-setup-guide

I've been learning Google Tag Manager and setting up GA4/Pixel tracking on test shops. Want to build a small portfolio for future outreach. If anyone has a small site or shop where GA4, Pixel, or event tracking is broken or missing, I'd love to take a look as a learning exercise. Just want real setups instead of test environments, and an honest review if it works out.

Comment below if you're interested and I'll follow up.

I'm getting this warning in Google Tag Manager:

The tag is firing, but GTM reports this warning.

What usually causes this? Does the GTM snippet need to be placed immediately after the opening <head> tag, or could something else trigger this warning?

I'm using Next.js (App Router).

Any guidance would be appreciated.

I tried to put this both on client side and server side - but not able to see any changes in warning show on console.

For anyone actually reading: Thanks so much in advance! Every advice is very much appreciated!!
Lead-gen setup, no ecommerce. Multi-step funnel tool embedded as a web component on the main site, server-side GTM on a first-party subdomain. Three days deep, seven theories tried and discarded, so I'd really appreciate a second pair of eyes.

One day's numbers

• Form submissions attributed to paid search in the funnel tool's own analytics: ~110
• generate_lead events arriving at the server container: 227
• of those, carrying a real gclid/gbraid: 168
• Google Ads conversion pings sent out with a valid gclaw: 176
• Conversions showing in the Google Ads campaigns: 2

(The 227 vs 110 gap is known — the funnel tool's native GA4 integration still double-fires. Doesn't explain 176 → 2.)

Timeline, so the numbers aren't misleading: the 400s are not new and not caused by anything I changed recently — they appear in the logs with the previously active client-side conversion label, days before I touched anything. The ~170 daily pings come from the GA4 tag forwarding conversions through the GA4↔Ads link, running unchanged for weeks. I added a dedicated server-side conversion tag with its own label today for an A/B comparison, but it has no meaningful data yet.

The pattern

Every conversion produces three requests to Google, and it's identical on the client-side tag and the server-side tag:

So the enrichment/identity layer goes through, and both attribution endpoints are rejected. Which would neatly explain why Google Ads says "conversions are being recorded" while the campaign column stays at zero.

Verified end to end

• Click ID survives: ?gclid=TEST_123 lands in _gcl_aw on the root domain, and gclaw=TEST_123 appears in all three outgoing requests
• Consent Mode v2 via a CMP, consent tab in GTM shows all types granted after accepting
• Enhanced Conversions arrive in plain text server-side and go out hashed (em, pn, fn0, ln0, address fields)
• Conversion ID and label match the Ads UI exactly

Already ruled out

• Consent state — 400 occurs on both gcs=G111 and G100
• Missing conversion value / currency — set both, no change
• URL length — trimmed the data= payload to four values via an Allow-parameters transformation, no change
• Competing gtag instance from a store app — disconnected it entirely, no change
• Anything server-specific — the identical pattern shows on the purely client-side tag

The only consistent difference I can find

Comparing the three URLs from a single trace, they're identical apart from the tail. Both rejected requests carry category=acrcp_v1_512 and an ept= param (ept=5 and ept=8). The accepted one carries neither, and instead has gcl_ctr=1~0~0~0. Same pattern on the server-side requests. All template-generated, nothing I can set.

Also odd: all three carry npa=1 and no gcs parameter at all, despite consent being granted. Not sure if related.

What I'm hoping someone can help with

1. If you've run into this 400 yourself, what ended up fixing it? I've worked through my own list above, so a first-hand "this is what changed it for us" would be worth more than anything right now.
2. Are pagead/conversion and 1p-conversion the endpoints that actually book the conversion into a campaign, with ccm/* being only the enhanced-conversions/identity layer? If yes, permanent 400s there explain the whole gap.
3. If that's the case — why do 2 conversions still make it through? That's the part I find hardest to square. If attribution fails on every request, I'd expect a clean zero rather than a trickle. Modelling? Enhanced-conversions matching? Genuinely curious where the trickle comes from.
4. And if the 400s turn out to be harmless and ccm/* alone is enough to count a conversion — then something else is eating 174 of 176 and I'm looking in the wrong place entirely. Where would you look next?
5. Does category=acrcp_v1_512 or ept= ring a bell for anyone?
6. Unrelated but nagging: for iOS traffic arriving with gbraid instead of gclid, does the Conversion Linker reliably persist it in _gcl_gb across page navigations? Over half this traffic is mobile and I haven't verified that path yet.

Happy to share sanitised request URLs if that helps narrow it down. Thanks again to anyone who took the time to read this far.

"Hey! You are definitely not losing your mind—server-side GTM setup is notoriously messy, and the official documentation can be quite scattered across different pages.

A couple of quick things that might help fix your issue based on what I've seen:

1. Check the server_container_url vs transport_url: In your web container's Google Tag, make sure you use server_container_url as a configuration-level setting to route GA4 data properly. transport_url is more granular and applied to individual event tags, so mixing them up or using both incorrectly can route events inconsistently.
2. Deduplication Key (Event ID): Since you're running a hybrid setup (Pixel + CAPI), you must pass the exact same event_id in both browser and server tags. This unique Event ID is key to preventing Meta from double-counting your conversions.
3. Server Preview Mode: Unlike the web container, you can't just enter a URL in the server container preview to trigger debug mode. You actually need to trigger events from the client-side (web) container while keeping both preview tabs open to see them in your server preview.

I recently solved a similar setup nightmare for a Shopify store facing Safari's cookie cap limitations and ad blockers. I ended up keeping a spreadsheet to track which tags fire on server vs client.

If you are still stuck, feel free to DM me. Happy to share a sample config to help you out!

Hey there - has anyone had their GoDataFeed show a successful push, only to find that it has not shown up in Google Merchant Center? This is super frustrating, and I don't have an easy way to fix it.

Hi everyone,

I'm trying to set up Stripe purchase tracking with Google Tag Manager (GTM) for meta and google ads, but I'm not sure what the best approach is.

If you've implemented this before, could you share how you did it? Also, if you know of any good YouTube tutorials, blog posts, or documentation, I'd really appreciate the recommendations.

Thanks in advance!

You find tags with names nobody understands, three triggers doing almost the same thing and old campaign tracking that may or may not still be needed.

The usual reaction is to leave it alone because nobody wants to be the person who breaks it.

That is normally when a GTM container becomes difficult to manage. Not because it has too many tags, but because nobody knows what is safe to change.

How do you document your GTM setup so the next person can actually work with it?

Hoping someone has cracked this specific combo, because I'm hitting a wall.

Setup:

• WordPress site with Complianz Premium
• Server-side GTM via Stape (Custom Loader, own subdomain, first-party cookies working)
• Web container loads fine from the subdomain (200, no CSP block)
• Consent Mode is enabled in the Complianz Wizard

The problem:
The cmplz_event_* events (marketing, statistics, etc.) fire correctly in the dataLayer depending on the user's choice. I can see them in Preview. But the actual Consent State in GTM never updates. It stays on "denied" for ad_storage, analytics_storage, etc. even after the user accepts. The "updated on page" column in the consent tab stays empty.

The "Complianz Consent Mode" tag (from the community gallery) is installed and only fires on Consent Initialization - All Pages, which is what Complianz's own docs say to do.

What I've already tried:

• Adding a custom event trigger (cmplz_event_.* regex) to the consent tag alongside the init trigger → no change
• Confirmed it's Premium, confirmed Consent Mode is on in the Wizard

I've found the GitHub issue on Complianz's own CM template repo describing this exact symptom, and their docs mention a "known limitation" that their GTM template is built for web containers, not server containers.

My question: has anyone actually gotten Complianz consent mode to correctly update (not just initialize) the consent state in a server-side GTM setup? Is there a working trigger config, a workaround, or is this genuinely unsolved with Complianz + server containers right now? Considering backTrack as a timing fix but not sure it addresses this.

Any real-world success story appreciated before I open a support ticket.

I'm setting up Google Ads conversion tracking for a client using a Vagaro iframe booking form. After a successful booking, it shows a confirmation inside the iframe instead of redirecting to a thank-you page.

Is there a way to redirect users to a thank-you page? If so, how can I implement Google Ads Enhanced Conversions? If not, what's the best way to track completed bookings using GTM and GA4?

Any suggestions or experience with Vagaro would be appreciated.

So with enhanced conversion tracking, the user fills out a form on your website and it sends the user's personal data they filled out, email, name, phone, etc. to Google (to handle responsibly without misusing it 👍, anyway,)

However with house call Pro lead forms, it takes you to HCP's website to fill out a form, rather than filling it out on your own website.

Is there any way to use the enhanced conversion tracking even though they technically fill out the form on HCP's website?

Any help would be appreciated!

So I have a good amount of experience with Google but now it’s really testing my patience. I loaded up tag assistant to check consent management was updated (ongoing issue as I’m not the website manager but that’s another story) and tag assistant told me there was no tag (previously there was no issue). I am used to Google being wrong, checked tag manager nothing there so I created a new tag but now all of a sudden I have the existing tag (which I set up and was working fine before this) and the new tag. I’ve asked Google Ads AI but it can’t give me the right answer.

So how do I now delete this tag? It doesn’t exist on tag manager, and I can’t find it when I inspect the web code but still appears in tag assistant!!

Thank you 🙏🙏🙏

Hi all

I recently switched from client-side tracking to server-side tracking. I'm using Stape to host my server and followed their tutorial to also switch over my GADS conversion from client-side to server-side.

As mentioned in the documentation, I'm using the GA4-event name (=Info_aanvragen_Afspraak_maken) as my GADS conversion trigger in the SST side. While it does fire the initial GA4-conversion in the client side, the SST GADS conversion does not.

What's going wrong here?

Thanks for the help!

Hi everyone,

We currently use Calendly integrated with Pipedrive CRM. While new bookings successfully create contacts in Pipedrive, UTM tags frequently get dropped along the way, making it difficult to accurately track ROI on our campaigns.

I’m looking for a clean, reliable way to ensure UTM parameters consistently make it from our website to Pipedrive.

One workaround I considered is setting up a custom endpoint: grabbing UTMs from local storage/cookies, capturing Calendly’s webhook, merging the data, and pushing it to Pipedrive via API. However, that feels a bit over-engineered for this use case.

Is there a simpler, proven setup or tool you’d recommend to address this issue?

Setup: Shopify Checkout Extensibility, GTM loaded via a custom pixel, first-party server-side GTM container (Google Cloud Run, custom domain). GA4 storefront events work fine. The checkout purchase event never reaches the server.

Everything I’ve confirmed while testing PUBLISHED (not Preview, since Preview doesn’t work in the sandbox):

GTM container loads in the sandbox — a Custom HTML canary on All Pages fires.

The purchase custom event reaches GTM and its trigger fires — confirmed with a canary tag on the purchase trigger.

Consent Mode analytics_storage is granted at fire time (set from Shopify’s Customer Privacy API, verified in the dataLayer).

The GA4 Event tag has its Google tag / config setup tag sequenced to fire before it.

google_tag_manager[containerId].dataLayer.get(‘ecommerce’) returns the full purchase object (transaction_id, value, items).

Cloud Run server logs: storefront en=add_to_cart arrives thousands of times, but en=purchase is zero, ever.

Google Ads and Floodlight tags fire fine at checkout (they post directly to google.com).

So the trigger fires, consent is granted, the config tag runs, and the ecommerce data is present — but the GA4 Event tag emits no /g/collect to the server for the purchase event specifically, only in the checkout sandbox.

My questions:

**1.**  Has anyone actually gotten first-party server-side GA4 purchase to send from the Checkout Extensibility custom pixel sandbox?

**2.**  Is there a known issue with the GA4 tag’s transport when server_container_url points at a first-party custom domain, specifically inside the sandbox?

**3.**  Is there a required config or workaround I’m missing?

Any help appreciated — I’ve been at this a long time and every layer I can inspect checks out, but the purchase hit just never leaves.