tagmanager | DEPRECATED - Tag Manager plugin for Craft CMS | Plugin library

Your gatsby-node.js looks perfect. Your issue is caused by the types of the data context you are sending to the template (videoDetailTemplate). You are telling to GraphQL that both id and editorId are ID types while I guess they should be strings.

I guess changing this line:

It's not the npm that needs an update but rather Node.js. You are running Node.js 10.22.0, but the package gatsby-plugin-google-tagmanager@3.4.0 requires Node.js 12.13.0 or higher.

Given that support for Node.js 10.x ended a few days ago (on April 30 2021), that's another reason to update. At the current time, I'd recommend updating to 14.x which is the most recent LTS (long-term-support) release. 12.x is fine, though, and will be supported for another 12 months. (14.x will be supported for another 24 months. 16.x will be supported for another 36 months, but is not officially an LTS release until October, so lots of changes might happen with it that wouldn't happen in an LTS release.)

It's also worth noting that the package did in fact get installed. You received a warning about the Node.js version, but not an error. Still, I would not recommend trying to run the package with a version of Node.js that it says it does not support.

Setting up the dataLayer pushes is just half of the battle. You need to config your GTM container to "listen" for those events and variables.

Setup new variable to track search query (note that you need to name it exactly how you pushed it to the data layer.

Setup new trigger to track the data layer event

After that, you can do whatever you want/need to do. Here's a simple example if you want to capture it as an event (note, the names are arbitrary, pick something that makes sense to you, just note the variable name that I used for the label, you can use this anywhere within GTM.

Can you maybe do e.g.:

Didn't find a permanent solution, but found a fix...

The problem stemmed from a conflict between my gatsby-source-wordpress and the way my Polylang WP plugin gets exposed to the GraphQL API. Basically, the "Duplicate ID" is related to the first post the API could find that has a translation, and for some reason it breaks. As of this writing this seems to be specific to gatsby-source-wordpress version ^5.0.0 and ^5.1.0. My fix : revert to gatsby-source-wordpress version ^4.1.0-next.1, which does not suffer from the same issue.

This fix works for me with Gatsby v3.1.1.

After searching a lot on the internet and reading different articles, I found out the solution mentioned here works perfectly well in Safari but not in other browsers because:

Chrome, Safari, and Edge mask the nonce attribute value so GTM is unable to grab it and store it as a variable.

Considering this solution for propagating the nonce to the custom HTML tags, we go ahead and apply the following changes to fix this issue on Chrome, Firefox, and Edge. As suggested here in the comments we need to modify the nonce-aware script a little bit and put the nonce in a data- attribute (then the browsers won't mask it), and push it to the dataLayer:

So it seems I'm part of the problem on this one. It looks like despite having disabled my adblockers and such, some chrome feature (or a getsby misconfiguration on my side) is still preventing the initialisation of the dataLayer by the injected script while in developement mode (everything works fine in production).

Using the incognito mode on chrome allows the former to be initialized and to send the hits to gtm witch does answer the question but still makes the testing quite unpractical.

Also note that I didn't manage to make the devmode work on firefox (even in private window with the tracking protection disabled). I'll fill an issue on the gatsby github repo and update this response if/whenever I recieve a response on the matter.

Based on this answer using jQuery, you can use an attribute selector and the ID of the element you want to get the label for, e.g. document.querySelector('label[for=' + button.id + ']'), then get its textContent to get the actual label:

Your source code with Tags.of should not compile as there is no such a method for .NET defined.

Documentation specifies Tags.Of - https://docs.aws.amazon.com/cdk/latest/guide/tagging.html

Tags.Of(myConstruct).Add("key", "value");

(!) Notice that the stack object has the Tags property, so make sure you do not access the Tags property of the stack, but Tags class.