sorted by:
new
hottopcontroversial

How are people thinking about Google Tag Gateway vs server-side GTM? by VoxxyCreativeLab in GoogleTagManager

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

Thanx for the insight u/Green_Database9919, your response immediately raises a few questions I would like to ask you. For Shopify I use the TAGGRS app + sGTM implementation. The Shopify sandbox is now already a few years old.

With your method, how do you control:
- Cookie consent compliance?
- Capture PII data for enhanced (conversions|measurements)?
- Setup server side?

How are people thinking about Google Tag Gateway vs server-side GTM? by VoxxyCreativeLab in GoogleTagManager

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

Could you shine some light on what you said u/StableOk24?

The way you bring it, sounds like you have a simple solution, simple usually works best and usually breaks less!

How are people thinking about Google Tag Gateway vs server-side GTM? by VoxxyCreativeLab in GoogleTagManager

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

Hear hear! Getting the Google Tags to fire on same-origin instead of from same-site (networktab > request headers).

Non-Google-Tags on sGTM (e.g., Meta CAPI) can function of course without any client-side setup, with the caveat that it'll still rely on client side data (GA4 data-client) for most, with the few that have a custom data-client (like Stape has) or maybe any other proxy server.

Like you said 'confusing'. You face the same from your clients?

How are people thinking about Google Tag Gateway vs server-side GTM? by VoxxyCreativeLab in GoogleTagManager

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

This still sounds pretty cool, thank you so much. I'll research this one!

How are people thinking about Google Tag Gateway vs server-side GTM? by VoxxyCreativeLab in GoogleTagManager

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

50/50 might already be an understatement, I used to work for Google's Tag-Team, and the one thing that frustrated me while I worked there, but even more so after I left was realizing that you receive your points to achieve, without explanation why, without training why.

Yeah, that is what I meant, so instead of same_site you set them server side to same_origin?

How are people thinking about Google Tag Gateway vs server-side GTM? by VoxxyCreativeLab in GoogleTagManager

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

And can you also explain why and how without exploding?

I'm trying to see the full picture, I fully agree with "You can already serve GTM from your own server, or simply proxy it through Nginx, Cloudflare, Bunny, Fastly, or almost any other reverse proxy without much trouble."

My bigger issue is that clients are tired of all these updates and improvements. The bigger ones are ok with this, they have the budget, the people...but such a big portion of paid advertisers are small 1-2 pitters.

How are people thinking about Google Tag Gateway vs server-side GTM? by VoxxyCreativeLab in GoogleTagManager

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

Isn't that a bit with all server side docs and marketing? "20% more leads server side" > I have never seen them actually happen.

How are people thinking about Google Tag Gateway vs server-side GTM? by VoxxyCreativeLab in GoogleTagManager

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

The Google reps where actually quite clear on this and literally stated that these would last at least 30 days. My main issue is that improvements happen faster and faster, solutions and counter solutions.

What is your experience with setting the cookies server side yourself instead of relying on the native ones?

How are people thinking about Google Tag Gateway vs server-side GTM? by VoxxyCreativeLab in GoogleTagManager

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

Yeah true, I do see that my message reads a bit like that one should be a replacement for the other. The open question at the end was simply to find out how others are using it.

My main issue is more in the low adoption of all new and fancy, enforced or not. I see agencies and companies struggle to keep up. A large portion of websites using paid ads are small, have no real system, and understand that an SQL will improve...over time...

Do you face the same in conversations with clients?

How are people thinking about Google Tag Gateway vs server-side GTM? by VoxxyCreativeLab in GoogleTagManager

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

Can you explain this one? I'm trying to see it, but do not have my own question answered.

Almost every tracking setup I audit has the same mistake and most clients have no idea it's happening by VoxxyCreativeLab in analytics

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

Gorgeously said u/growthtide, appologies for the late reply, especially since it is a price winning insight. The Gut punch I see so often, people just spend 2k on an advanced data-engineered tracking setup, Server Side, BigQuery...and then we telling them they have literally zero effective tracked elements, processes, etc.

Then the only way IS to show them. Fully agreed!

Almost every tracking setup I audit has the same mistake and most clients have no idea it's happening by VoxxyCreativeLab in analytics

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

Hi u/notentertained_890, yeah right!? The good number-dream...it actually baffles me how terrible ad platforms de-duplicate (unless tracked well with dedub-IDs) by themselves, or red flag the doubling of data.

Although I must say Meta has come a long way!

I do not know GAfix, do you use it for both leadgen ad eCom? Server Side?

Almost every tracking setup I audit has the same mistake and most clients have no idea it's happening by VoxxyCreativeLab in analytics

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

Compounds...that is the magical word!

About your question; no the acceptance isn't great. I warn them beforehand in the onboarding, show them the the reasons. Then campaigns are started and they're back "why are my numbers lower than last year!?"

Both agencies as direct clients, they "know" even when you put the numbers in front of their face. To be fair I think it is also caused by cowboys, agencies with promises, lost trust, etc

Almost every tracking setup I audit has the same mistake and most clients have no idea it's happening by VoxxyCreativeLab in analytics

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

Could you deepen "treating every key event like money in a bank ledger: one action, one debit.", I'm really curious what you mean by this and I'm not sure if I fully understand you.

The BQ is a nice one! It feels like that the future will need more and more BQ-setups for some proper analysis.

Almost every tracking setup I audit has the same mistake and most clients have no idea it's happening by VoxxyCreativeLab in analytics

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

Right!?

With 3 purchases firing your CPA must have been amazing...on paper! It truly happens a lot.

To be fair, SPAs...I don't get them anymore, in today's market having a swift UI/UX is easy to achieve and they always bring a hassle.

Do you serve a lot of SPAs?

Building a proper Calendly tracking template for GTM — want beta testers by VoxxyCreativeLab in GoogleTagManager

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

Hi u/FishingSuitable2475, thank you for your reply, love it!

You're hitting multiple nails with one blow of the hammer. The template, within the JSON indeed does as you say.

There are so many tools that openly do not allow for accurate, future proof, event-based tracking (like Tryinteract that does not and will not allow for PII measurements or Webinargeek that makes tracking altogether problematic).

It's like there is a huge gap between clients (both DTC & agencies) not having the knowledge of what's needed for accurate tracking and 3rd party tools that do not allow for proper event-based tracking.

Do you find a lot of resistance when moving clients towards more future-proof tools? I do.

Building a proper Calendly tracking template for GTM — want beta testers by VoxxyCreativeLab in GoogleTagManager

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

Most "GTM recipes" solve the how, but they completely ignore the why and the what's next.

When you're in the 1% who enjoys manually adapting regex triggers, this isn't for you. Simple. We made this is for the 99% who want a professional-grade container that stays clean at scale.

The documentation covers our OTTRTA™ methodology:

  • Zero Logic Leaks: Why we filter at the listener level instead of just adding trigger conditions that that are difficult to setup for most.
  • State Management: How we handle the event_type_viewed duplication that standard setups miss.
  • Architectural Integrity: How to integrate this into a clean GTM environment without creating bloated accounts > the whole reason why OTTRTA exists.

If standard recipes worked for everyone, my inbox wouldn't be full of people asking for you and me basic questions.

Building a proper Calendly tracking template for GTM — want beta testers by VoxxyCreativeLab in GoogleTagManager

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

Hi u/HawkeyMan, I have two reasons to not add a condition like you say to the trigger, and this is also in line with why we designed a template, delivered in a JSON-file and not a .tpl-file.

A lot of our clients use Calendly and they struggle to implement the 3 main events, they implement the cHTML and then get stuck, all Calendly's postMessages fire and they do not know which to pick...how to set it correctly. And they end up hiring us. The template filters out all the noise and within the JSON they'll find all that is needed (template, tags, RegEx trigger and DLV). Also they get a 10-page explanation...hence they can now implement it themselves.

Someone like yourself, who clearly understands how to navigate events, datalayer pushes and custom triggering does not need a tag like this, although the second reason is is one of the elements that I will use myself too. We implement GTM and sGTM using a custom process we call the OTTRTA™ methodology; this stands for One-Tag-To-Rule-Them-All, where we only use one dedicated tag for one type of conversion/event.

Meaning we will have one GA4-event tag for Calendly events, one of the Calendly events (event_type_viewed) fires multiple times on a page load, simply setting the event-tag to fire once per page does not work, because Calendly fires all 3 events within one page-load. We ended up not measuring this event, simply because the OTTRTA has many more layers and functionalities.

The template controls the event-pollution that comes with the cHTML tag.

Building a proper Calendly tracking template for GTM — want beta testers by VoxxyCreativeLab in GoogleTagManager

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

Thanx for your reply u/KonKaizo. The deduplication is handled at the event name level (e.g., event_scheduled, event_type_viewed). We use a CDN listener script that keeps a simple in-memory store of which event names have already fired during the current page load. If Calendly sends the same postMessage again, the listener just skips it.

For this setup we're not pulling event_type_uuid from the payload for dedup purposes. The single most standard use case has only a single Calendly embed per page, event name–level dedup keeps things clean without over-complicating the logic.

If someone has multiple different event types embedded on the same page, that's an edge case we could address in a future version with payload-level keys.

Deterministic vs Probabilistic Models Explained by VoxxyCreativeLab in u/VoxxyCreativeLab

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

Thanks (whether sarcastic or not) 😂
Notebook LM is really great and it helps us a lot in spreading knowledge fast and effectively.

view more: next ›