Hey people,

I'm newish to GTM but have done plenty of in-hand events now for some time, so its been mostly self learning, I would like to know any opinions on the setup and other general questions I would love to hear some answers or thoughts on.

1.- I share with you the setup I currently have for hubspot form submission tracking below. I have had some inconsistencies between the form submission number from GTM to GA4, looking at it with data studio.

This is the HS form listener:

<script type="text/javascript">
window.addEventListener("hs-form-event:on-submission:success", function(event) {
  window.__hs_form_submitted = true;
  try {
    var formGuid = HubSpotFormsV4.getFormFromEvent(event).getFormId();
    window.dataLayer.push({
      'event': 'hubspot_form_success',
      'hs-form-guid': formGuid
    });
  } catch(e) {
    window.dataLayer.push({
      'event': 'hubspot_form_success',
      'hs-form-guid': 'unknown'
    });
  }
});
</script>

My event generate_lead: basically triggers in a custom event.

Custom event: hubspot_form_success // this trigger fires on: All custom Events.

I basically take all form submissions and with parameters i distinguish them by form names or types.

I also added, the parameter: transport_type beacon to reduce the possible issues with navegation and missing those form submissions.

In my mind the difference between GA4 Form submissions vs the pure number showed by Hubspot, can be affected by:

• Tracking: I switched it to all form submissions so that there is no form missing.
• Data filters: I have yet to completely check if this could be an issue, its pending on my tasks
• Ad blockers: nothing i can do to mitigate this
• Listener: I share it with you in case theres anything else i could do to improve it, i even added the "catch" and "try" to mitigate listener failing?
• User's closing the page too quickly: mitigated by the transport type beacon thing.
• Cookies: I have checked and even if people dont accept the analytics cookies the event in preview mode of hs form success is still triggered so i dont see a problem

More than welcome for any critics :)

2.- My forms are HS forms V4 so I think now I can not access lets say data field values when a form is submitted, but before with V3 forms, did you guys did any workaround in terms of GDPR? My understanding is we could not send it to ga4 given that would be personal information for 3rd party companies

3.- How would you go on to stablish dashboards or correct tracking from web to CRM, because i was thinking of using the previous personal information as a match key for ga4 web vs crm and see things like OI. But I'm not sure if there are better ideas here, as I mentioned, I'm a bit new in this digital world.

4.- Before there was an individual who configured server side tracking, anyone knows where i can read to better understand this as I have absolutely no idea and now theres no one I can ask. The only thing regarding this in my mind is that some data does not pass to ga4 so its more data compliant and apparently more clear in traffic sources and some metrics.

Any comments on any of the questions is much appreciated, I find tracking to be so interesting but a bit challenging for me to learn and implement as there are many errors in my experience setting things up :) thanks people!

​

Hi everyone,

I have a tracking problem with Prestashop and the Redsys payment gateway.

The issue is:

When a customer comes from a Google Ads campaign and completes the payment through Redsys, the order is correctly created in Prestashop and the payment is successfully processed.

However, Google Ads and sometimes GA4 do not register the conversion.

After investigating, it seems that Redsys does not always return the user to the proper Prestashop order confirmation page (order-confirmation), or the original tracking/session information is lost during the external payment process.

As a result:

Orders exist in Prestashop

Payments are successful

But Google Ads conversions are missing

GA4 attribution is sometimes lost or appears as Direct traffic

Current setup:

Prestashop

Redsys payment module

Google Ads

Google Analytics 4

Google Tag Manager

I suspect:

loss of GCLID/session attribution,

broken return URL flow,

or conversion tags depending only on thank-you page views.

Has anyone solved this properly?

Would you recommend:

server-side tracking,

enhanced conversions,

custom GTM events,

modifying Redsys return URLs,

or triggering conversions directly from backend order validation?

Any advice or proven setup would be greatly appreciated.

Hi everyone,

I'm working on setting up Enhanced Conversions for Google Ads using a GTM Server-side container (Stape) and I'm running into an interesting issue that I can't figure out.

My Setup:

- Multiple domains (.es, .de, .uk, etc.) - each with its own GTM Web container

- 1 shared GTM Server-side container (Stape with first-party domains)

- Each domain has its own GA4 property

- All properties have "Allow user-provided data capabilities" enabled with:

- Automatically detect: Email, Phone, Name and address

- CSS selectors configured:

- Email: `.modal_msg_texto > strong:nth-child(1)` (captures from confirmation modal)

- Phone: `input[name="telefono"]`

The Problem:

- Spain (.es) is successfully sending BOTH email and phone number to Google Ads

- Other domains (Germany, UK, etc.) are sending NEITHER

When I check with Tag Assistant on Spain, I see:

ep.user_data.email: user@example.com ep.user_data.phone_number.0: +34123456789

On Germany and other domains: nothing.

**What's Identical Across All Domains:**

- Same form HTML structure (`<input name="email">` and `<input name="telefono">`)

- Same GTM Web container setup (tags, triggers, variables)

- Same GTM Server container (shared by all)

- Same GA4 configuration for "Allow user-provided data"

**My Theory:**

The email CSS selector points to the confirmation modal (`.modal_msg_texto > strong:nth-child(1)`) which appears AFTER form submission. The phone number is NOT visible in the modal, only in the form input (which is still in the DOM but hidden under the modal overlay).

Questions:

1. Why would GA4's "Automatically detect" work for phone numbers in Spain but not in other domains, when the configuration is identical?

2. Should I configure hashing in GTM Server, or does GA4 handle that automatically when linked to Google Ads?

3. For Enhanced Conversions with GTM Server-side, is it better to use "Google tag" method or GTM method in Google Ads settings?

Additional Context:

- I just updated the CSS selector for email on the other domains to match Spain's configuration (pointing to the modal instead of the input field)

- Configuration was saved 24-48 hours ago but hasn't propagated yet

- Spain's configuration was done weeks/months ago and works perfectly

Any insights would be greatly appreciated! Has anyone experienced similar issues with GA4's automatic detection in server-side GTM setups?

Thanks!

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 🙏

If your store or your client's store has any of these problems, this post is for you.

1. How do you track Stripe purchases server-side without losing the order ID? The reason your Stripe purchases keep "going missing" in Meta and Google isn't a Pixel bug—it's the architecture. Stripe redirects the user off-domain, processes payment, and brings them back to a thank-you page where Safari ITP and ad blockers have already killed the cookie context.

• The fix: Don't rely on the "Thank You" page trigger. Capture the order via Stripe webhook on your server.
• The workflow: Forward the webhook to a server-side GTM container (I run mine on Stape for first-party cookie/custom domain), then send the Purchase event to Meta CAPI / Google Ads with the order_id, hashed PII, and an event_id for deduplication.
• The result: Match rate typically goes from ~60% to 90%+ because you aren't relying on a browser-side trigger that may or may not fire.

2. How do you sell server-side tracking to a client who only cares about ROAS? You don't sell tracking. You sell Signal Recovery.

• The Hook: "Your ad platforms are missing 30–50% of your conversions."
• The Logic: If 40% of purchases never reach Meta, the algorithm is optimizing on bad data. This artificially inflates your CPA by ~25% because the "learning" phase is starved of success signals.
• The Close: Promise a lower CPA through cleaner signal. When the algorithm sees the full conversion set, it finds your customers faster.

3. Why does GA4 disagree with my ad platform? Both are technically "right"—they just speak different languages.

• Attribution: Meta uses 7-day-click + 1-day-view. GA4 defaults to Data-Driven or Last-Click (Non-direct).
• Stitching: Meta deduplicates on its own user graph; GA4 relies on user_id, which most stores haven't configured correctly.
• Privacy: Ad blockers hit GA4 (client-side) harder than they hit server-side CAPI.
• The Framework: Optimize campaigns against the ad platform's number (to feed the algo), report business performance against GA4/Backend, and use server-side deduplicated data as your monthly source of truth.

4. What does a privacy-first stack look like in 2026? The myth is that privacy kills accuracy. In reality, a clean consent stack captures durable signal that doesn't get blocked.

• The Stack: CMP (OneTrust/Cookiebot) → GTM Variables → Google Consent Mode V3.
• Why V3? It’s mandatory for EEA traffic. Skip it, and Google throttles your bidding models silently.
• The Setup: Client-side GTM fires only consented tags; server-side GTM (Stape) hashes PII and deduplicates before outbound to Meta/TikTok.

5. The "Impossible" Platforms: Drupal and Shopware. Most agencies run from these because there’s no "one-click" app.

• Drupal: Hook into Commerce module events via a Twig template extension to push a clean dataLayer.
• Shopware: Use the Frontend Subscriber pattern + checkout finish event.
• The Secret: Use webhooks as a fallback. If the browser fails to hit the thank-you page, your server-to-server webhook ensures the conversion is still recorded.

Happy to go deeper on any of these in the comments. If you want a quick "sniff test" of your setup, drop your stack in a reply (Platform + Ad Channels) and I'll tell you where your biggest leak likely is.

One of the biggest problems in Google Ads dropshipping is not finding products.

It’s getting your store approved by Google Merchant Center.

Most beginners get hit with misrepresentation, website needs improvement, or policy issues — then they start guessing what to fix.

That’s exactly why Terry Ecom created GMC Scout:

www.gmcscout.com

It’s a Shopify / Google Merchant Center scanning tool built specifically for ecommerce stores and Google Ads dropshippers.

The goal is simple:

Scan your store, find the compliance issues, fix them properly, and improve your chances of getting GMC approved.

GMC Scout checks things like:

• Policy pages
• Contact information
• Shipping and returns
• Trust signals
• Product page issues
• Store structure
• Google Merchant Center readiness

Most dropshippers don’t fail because the product is bad.

They fail because their store doesn’t look trustworthy enough for Google.

That’s the gap GMC Scout was built to solve.

If you’re trying to run Google Shopping Ads, Performance Max, or scale a dropshipping store with Google Ads, your GMC approval is the foundation.

Without it, you can’t even get started properly.

Try it here: www.gmcscout.com

Where can I find free tag manager training?

How long to master this beginner tool to expertise !!

are they in-house | consultant ?

Hello,

CMS: Shopify

Tracking integration: pixel

I setted the tracking through GTM and I get this status for a Facebook request:

>(failed) net::ERR_BLOCKED_BY_ORB

It is the same with the Facebook & Instagram plugin.

Any ideas why?

Thank you.

Heads up if you are running sGTM. As of May, 5 the Web Container client in server-side GTM has a new Tag Serving Path field. It lets you serve gtm.js (and gtag.js) through your tagging server with a randomized alphanumeric path that hides which container is being loaded.

So instead of:

https://www.googletagmanager.com/gtm.js?id=GTM-XXXXXX

you load:

https://yoursite.com/data/zxq7pm2r/

(where /data is your tagging server path and /zxq7pm2r is the auto-generated serving path).

The container ID is still in the query string of course, but the loader URL itself no longer screams "GTM", which is what most ad blockers pattern-match on. Some will still catch it via the ?id= parameter; others won't.

Few questions for who already tried it:

• Did you measured a recovery in pageview counts after the switch?

• The path is auto-generated when you add a container but you can override it. Anyone benchmarking whether a custom-rotated path performs better than the default?

For a while our Next.js app had tracking scripts scattered across _app.tsx. Every time we needed a new pixel or wanted to tweak a conversion event, it meant a code change, a PR, a deploy.

For a solo founder moving fast, that friction adds up — you skip instrumentation you should have added, or you add it sloppily.

Switched to GTM a few weeks ago. The difference:

- New pixel? Less than 5 minutes in GTM, no deploy

- Want to test a conversion trigger? Preview mode shows you exactly what fires and when

- Audit what's tracking what? One dashboard instead of grepping through app.tsx

- Load order is explicit. Tags fire in the sequence you define, not whenever the async script loads

The migration + testing took about 3 hours. Mostly replacing the existing gtag calls with GTM's dataLayer pushes and moving the tag configs into the GTM container.

If you're still on raw gtag snippets in a Next.js app and you're running any paid acquisition, this is worth doing. The overhead drops significantly once tracking lives outside your codebase.

Did I mention no deploys?

Hi, I’m trying to set up conversion events for my meta ads account and integrate it with sevenrooms. Unfortunately, sevenrooms can only be configured with GTM so I was wondering if anyone here has experience setting this up and will be willing to help me out.

Hello everyone,

I am managing GTM for an EU-based company (strict GDPR compliance). I’ve implemented a manual Consent Mode setup using a custom banner.

Currently, I use "Hard Blocking" for all Meta tags (both Web and Server) when marketing cookies are denied. However, I’d like to move toward a setup similar to Google’s Advanced Consent Mode (anonymous pings for conversion modelling already built in GA4 and Google Ads tags).

Web GTM: I use the official Meta Pixel template. It has a field "Consent Granted (GDPR)" that I can toggle. If I set this to false based on the user's choice and let it fire when consent is denied, will Meta treat this as an anonymous signal for modeling, or is this still a compliance risk?

Server-Side GTM: I use the facebookincubator Conversions API Tag. Unlike the web template, it doesn't have a native "Consent" field. Should I manually map parameters like ad_user_data and ad_personalization to granted/denied within the tag's parameters (or via Transformations) to enable modeling? Or is it safer to stick with hard-blocking for Meta on the server side?

Basically, I want to know if Meta now has a formal "Advanced Consent Mode" that allows for data modeling without violating GDPR when ad_storage is denied.

Thanks for any insights!

Hello! Thank you to anyone who offers me help

I am managing 30+ GTM containers for a client, who has requested to have all changes logged in a sheet. I'm loathe to spend time doing this in the world of automation, and I document the changes within GTM itself, in the versions.

Has anyone had any success in pipelining the version history from GTM into a Google sheet/BigQuery/email report/anything similar?

Setting up sGTM and trying to minimize PII exposure.

My original plan was to hash email/phone before sending data to sGTM. But platforms expect different normalization formats before hashing.

Example:
Meta: 16505551212
Google: +16505551212

Does this mean the better approach is:

• Send raw PII securely to sGTM, then normalize/hash per platform inside sGTM?
• Or hash before sGTM and maintain multiple versions?

What’s the standard approach for Meta CAPI + Google Enhanced Conversions?

“Your Meta Ads data is probably lying to you.”

A few weeks ago, I thought running Meta Ads was only about creatives, copywriting, and targeting.

I was wrong.

The deeper I went into performance marketing, the more I realized something shocking:

Most advertisers are optimizing campaigns based on incomplete or broken tracking data.

And when your data is wrong…

your decisions become wrong too.

That realization pushed me to start learning:

→ Facebook Pixel

→ Conversion API (CAPI)

→ Google Tag Manager (GTM)

→ Server-Side Tracking

→ Event Optimization

→ Advanced Conversion Tracking

At first, everything looked overwhelming.

Tags.

Triggers.

Events.

Deduplication.

Browser limitations.

iOS privacy updates.

Server-side events.

Honestly, it felt like learning a completely different side of digital marketing.

But then I understood something important:

The future of advertising belongs to marketers who understand data, not just design.

Because today:

Better tracking = Better optimization

Better optimization = Lower ad costs

Lower ad costs = Higher profitability

One small mistake in tracking can destroy an entire campaign without you even realizing it.

That’s why I started focusing not only on running ads, but also on understanding what happens behind the scenes.

Now I’m exploring how AI, automation, and advanced tracking systems are changing modern marketing.

Still learning.

Still experimenting.

Still improving every day.

But one thing is clear:

Digital marketing is no longer just about “boosting posts.”

It’s becoming a mix of psychology, analytics, automation, and AI.

And honestly… that’s the most exciting part.

If you're learning Meta Ads or performance marketing, what’s the hardest thing you’ve faced so far?

&#x200B;

Hi, I’m pretty new to GA4 and Google Tag Manager and I’ve been stuck for the last few days trying to properly understand the setup, events, attribution,etc. I am employed at a SaaS company and handling performance ads.

I’ve watched a bunch of tutorials but I feel like I’m mixing things up and making the setup messy.

I just want someone experienced who’d be open to guiding me a bit over a quick call/screenshare (maybe 30 mins to 1 hour max) so I can understand what I’m doing wrong and how can I make the analytics look decent and learn the correct setup approach.

I’m okay paying something for the time as well, just mentioning in advance that I’m still early in my career so I don’t have a huge budget.

If someone’s open to helping, please DM me. Would genuinely appreciate it.

I've been lurking here for a while and figured this community would have the most relevant take on this.

A bit about me: I work full-time in a data and measurement role at a SaaS company. On the side I've been building out an independent consulting practice. I'm not looking for clients who need simple tagging implementations or quick fixes. More interested in companies that want a real partner on their measurement infrastructure, the kind of engagement where you're involved in the architecture decisions, not just told what to tag.

The problem is LinkedIn is basically off the table for me. Full-time employment, conflict of interest, you know how it is.

So how do you find those kinds of clients without being able to post openly on LinkedIn? What's actually worked for you? Cold outreach? Referrals? Niche communities? Would love to hear what's worked and what hasn't.

Second question while I have you all here:

What MCP servers or Claude Code skills have you found actually useful for day-to-day GTM/analytics work?

I've already built a custom GTM MCP server that lets me run container operations via CC, reading tags, triggers, variables, making changes, all through natural language. It's been a decent productivity boost. Curious if anyone else is doing something similar or has found other AI tooling that's genuinely useful and not just impressive in a demo.

Appreciate any thoughts on either question.

If your store or your client's store has any of these problems, this post is for you.

1. How do you track Stripe purchases server-side without losing the order ID? The reason your Stripe purchases keep "going missing" in Meta and Google isn't a Pixel bug—it's the architecture. Stripe redirects the user off-domain, processes payment, and brings them back to a thank-you page where Safari ITP and ad blockers have already killed the cookie context.

• The fix: Don't rely on the "Thank You" page trigger. Capture the order via Stripe webhook on your server.
• The workflow: Forward the webhook to a server-side GTM container (I run mine on Stape for first-party cookie/custom domain), then send the Purchase event to Meta CAPI / Google Ads with the order_id, hashed PII, and an event_id for deduplication.
• The result: Match rate typically goes from ~60% to 90%+ because you aren't relying on a browser-side trigger that may or may not fire.

2. How do you sell server-side tracking to a client who only cares about ROAS? You don't sell tracking. You sell Signal Recovery.

• The Hook: "Your ad platforms are missing 30–50% of your conversions."
• The Logic: If 40% of purchases never reach Meta, the algorithm is optimizing on bad data. This artificially inflates your CPA by ~25% because the "learning" phase is starved of success signals.
• The Close: Promise a lower CPA through cleaner signal. When the algorithm sees the full conversion set, it finds your customers faster.

3. Why does GA4 disagree with my ad platform? Both are technically "right"—they just speak different languages.

• Attribution: Meta uses 7-day-click + 1-day-view. GA4 defaults to Data-Driven or Last-Click (Non-direct).
• Stitching: Meta deduplicates on its own user graph; GA4 relies on user_id, which most stores haven't configured correctly.
• Privacy: Ad blockers hit GA4 (client-side) harder than they hit server-side CAPI.
• The Framework: Optimize campaigns against the ad platform's number (to feed the algo), report business performance against GA4/Backend, and use server-side deduplicated data as your monthly source of truth.

4. What does a privacy-first stack look like in 2026? The myth is that privacy kills accuracy. In reality, a clean consent stack captures durable signal that doesn't get blocked.

• The Stack: CMP (OneTrust/Cookiebot) → GTM Variables → Google Consent Mode V3.
• Why V3? It’s mandatory for EEA traffic. Skip it, and Google throttles your bidding models silently.
• The Setup: Client-side GTM fires only consented tags; server-side GTM (Stape) hashes PII and deduplicates before outbound to Meta/TikTok.

5. The "Impossible" Platforms: Drupal and Shopware. Most agencies run from these because there’s no "one-click" app.

• Drupal: Hook into Commerce module events via a Twig template extension to push a clean dataLayer.
• Shopware: Use the Frontend Subscriber pattern + checkout finish event.
• The Secret: Use webhooks as a fallback. If the browser fails to hit the thank-you page, your server-to-server webhook ensures the conversion is still recorded.

Happy to go deeper on any of these in the comments. If you want a quick "sniff test" of your setup, drop your stack in a reply (Platform + Ad Channels) and I'll tell you where your biggest leak likely is.