gtm

It looks like you have an older version of Node? https://github.com/nuxt/nuxt.js/issues/2385#issuecomment-358111543

Try to upgrade it to the latest LTS aka 14 and double-check that you got the latest version of Nuxt too.

Right, that's cuz either the fields aren't being inherited from the settings variable (I have noticed that behavior in GA4 before) or the values of your DL variables are not set at that point (which is unlikely).

An obvious fix for it would be just adding your fields to the click tag and be done with it.

The way I do GA4 tags is by making one single tag. For everything. All its content are variables, including the name of the event. And all the logic for it is either in regex lookup tables or in CJS. Or in both: CJS that uses rLUTs.

Now it may seem complicated and overengineered, but now the size of your GA4 set up is small (remember: the size of the container is limited), it's easy to manage if you love your JS (all logic is in one place) and you don't need to iterate through all your dimensions every time you need a new event to fire.

So I basically treat a GA4 event tag as a config variable. In your case, you can even merge the pageview and the click events into one.

Also, not having history changes is a really poor practice and I would switch the site engine completely. It will cause dramatic issues in other places, like SEO.

Try changing your trigger filter to Matches CSS Selector. And this is the value of your selector: a.button.primary, a.button.primary *

Your problem is that click actually lands on a span in a rather than a itself, therefore, your click classes are empty. That span has no classes.

How do I know where the click lands? I can see that from the "value" of the Click Element variable in your debugger screenshot. That's not real value, but that's a generic selector that attempts to uniquely identify an element that was clicked on. The end of that selector. See how it actually has your a but then it has > span? There.

you can use html_to_json

From your screenshot, gtm.js is executed before the update of the consent mode so the pageview continues to be sent to Google Analytics as denied.

The update must take place before gtm.js

Server-side GTM doesn't proxy js like normal GTM does. It's mostly for proxying network requests.

If you wonder if it can send enhanced ecommerce events then yes, it can.

If you wonder if it can deploy anything on the site (that includes any js files), then no, it can't. It doesn't manifest on the front-end in any way at all. It can proxy files, but all that does is rewrites the endpoint that you still have to include in your DOM.

Use front-end GTM to deploy anything on the front-end.

In order to enter preview, you have to first open GTM. In GTM, you have workspaces. Or at least, the default one. open GTM, go to the overview tab of the workspace that you're previewing (since you don't know what worspaces are, you probably use the default one) and make sure there are no Workspace Changes in it. Here is a screenshot of a workspace WITH changes:

And here is another workspace with NO changes:

If you have changes in your workspace, try publishing them and see if your tags start firing in prod.

dataLayer.push({ 'user_id': 'xxx' }) by itself might not have an effect, but that is because you do not tell GTM to update it's internal state.

GTM overwrites the "push" method of the datalayer array with some custom code that, among other things, scans the pushed objects for a key with the reserved name "event". Only if it finds that key, the data that has been pushed to the datalayer is actually evaluated, and the variables configured in the "variables" tab of the GTM interface assume a new value, if indeed a new value for them has been set in newly added datalayer object. The "event" key also allows you to create a trigger to fire tags with the updated values.

So if you do

@Eike is correct there. Noscript is completely useless in 99.99% of cases. It's used when a user has JS off, but unlike what you think, it won't make GTM work with no JS. In fact, only one tag will "fire" in that state and that would be a rarely used custom image tag.

Yes, noscript implies an iframe and if your app doesn't support them, well then no noscript for you. Really, Nuxt is a front-end rendering framework. Why would you have anything in your other than asking the user to enable JS in order to see the site...