google-analytics | Get data from google analytics using PHP | Analytics library

So if anyone comes across this question for some reason, I figured it out. As it turns out, the cross-origin-embedder-policy header was giving me troubles. This had to be disabled. Helmet has a built in option to do so crossOriginEmbedderPolicy: false,. More info here.

For most people I guess that'll work. However it did not work for me. The header was still being set. Disabling it with express also did not work (app.disable('cross-origin-embedder-policy');).

I have no idea why the header was still being set, but I had to disable it manually in my nginx configuration: proxy_hide_header cross-origin-embedder-policy;

My config:

You are probably recognized as a bot / spam. Try to add other parameters to the call such as the host name (dh) and the pagePath (dp) or the location (dl) or even ua parameter: https://developers.google.com/analytics/devguides/collection/protocol/v1/parameters#ua

Google Analytics script should be added inside the tag. Ideally, this is automatically handled by the plugins. In fact, it's exactly what {props.headComponents}, {props.preBodyComponents} and {props.postBodyComponents} does, they manipulate Gatsby's SSR API onRenderBody to place the scripts you add in the gatsby-config.js or manually in the gatsby-ssr.js.

If you are not able to add several instances of gatsby-plugin-google-analytics or add multiple tracking identifiers using Google Tag Manager, you can use the html.js as you are doing. In this case, you should do something like:

I MUST maintain this line where she is.

That directive does not need to go inside the WordPress code block. You should place that directive before the # BEGIN WordPress comment marker. And this will prevent it from being overwritten by WordPress. In fact, you could place your custom rules at the very top of the file to make them easier to find/maintain.

It will work exactly the same.

You do not need to enclose it in an container like the other directives. And you should not repeat the RewriteEngine On and RewriteBase / directives. (The order of these particular directives do not matter. In fact, the last instance "wins" and controls the entire file.)

For example:

you can use html_to_json

The problem is that you have Node 17.2.0. locally but in Netlify's environment, you are running a lower version (by default it's not set as 17.2.0). So the local environment is OK, Netlify environment is KO because of this mismatch of Node versions.

When Netlify deploys your site it installs and builds again your site so you should ensure that both environments work under the same conditions. Otherwise, both node_modules will differ so your application will have different behavior or eventually won't even build because of dependency errors.

You can easily play with the Node version in multiple ways but I'd recommend using the .nvmrc file. Just run the following command in the root of your project:

It turns out that duplicate keys are no longer allowed. And to fix it, you not only need to delete one of the duplicates (as I did), but you need to unpublish your extension entirely and then republish.

It wasn't clear on what would happen when unpublishing. Essentially, you extension will disappear from the Webstore and when you republish, it takes longer than usual to review it. (it took about 2 days vs the normal couple hours). In that time it will say 'pending' but when it does get approved, everything in your store will be restored and it will be as though nothing happened.

To properly use the google tag in your next.js app, You should add the GTM script to _document.js in the Head section.

example code _documents.js, source.