Gatsby plugin to add google analytics and facebook pixel in a GDPR form to your site.
npm install --save gatsby-plugin-gdpr-cookies
// in your gatsby-config.js
module.exports = {
plugins: [
{
resolve: `gatsby-plugin-gdpr-cookies`,
options: {
googleAnalytics: {
trackingId: 'YOUR_GOOGLE_ANALYTICS_TRACKING_ID', // leave empty if you want to disable the tracker
cookieName: 'gatsby-gdpr-google-analytics', // default
anonymize: true // default
},
googleTagManager: {
trackingId: 'YOUR_GOOGLE_TAG_MANAGER_TRACKING_ID', // leave empty if you want to disable the tracker
cookieName: 'gatsby-gdpr-google-tagmanager', // default
dataLayerName: 'dataLayer', // default
},
facebookPixel: {
pixelId: 'YOUR_FACEBOOK_PIXEL_ID', // leave empty if you want to disable the tracker
cookieName: 'gatsby-gdpr-facebook-pixel', // default
},
// defines the environments where the tracking should be available - default is ["production"]
environments: ['production', 'development']
},
},
],
}
First of all the plugin checks in which environment your site is running. If it's currently running in one of your defined environments it will add the tracking code by default to the <head>/<body>
of your site. It will not be activated or initialized by this.
By default this plugin will not send any data to Google or Facebook to make it GDPR compliant. The user first needs to accept your cookie policy. By accepting that you need to set cookies for the tracker you want to use - gatsby-gdpr-google-analytics
, gatsby-gdpr-google-tagmanager
, gatsby-gdpr-facebook-pixel
. Depending on the user input the value of each of the cookies should be true
or false
.
If the gatsby-gdpr-google-analytics
cookie is set to true, Google Analytics will be initialized onClientEntry
. Same is for the Google Tag Manager and Facebook Pixel.
The page view will then be tracked on onRouteUpdate
.
Important: read below about using the plugin with Google Tag Manager.
Here you place your Google Analytics tracking ID.
You can use a custom cookie name if you need to!
Some countries (such as Germany) require you to use the _anonymizeIP function for Google Analytics. Otherwise you are not allowed to use it. The option adds two blocks to the code:
ga('set', 'anonymizeIp', 1);
If your visitors should be able to set an Opt-Out-Cookie (No future tracking) you can set a link e.g. in your imprint as follows:
import ReactGA from 'react-ga';
render() {
return (
<div>
<ReactGA.OutboundLink
eventLabel="myLabel"
to="http://www.example.com"
target="_blank"
trackerNames={['tracker2']}
>
My Link
</ReactGA.OutboundLink>
</div>
);
}
Here you place your Google Tag Manager tracking ID.
You can use a custom cookie name if you need to!
Data layer name
Google Tag Manager environment auth string
Google Tag Manager environment preview name
Data layer to be set before GTM is loaded. Should be an object or a function that is executed in the browser, e.g.:
defaultDataLayer: { platform: "gatsby" }
defaultDataLayer: function() {
return {
pageType: window.pageType,
}
}
Out of the box this plugin will simply load Google Tag Manager on the initial page/app load. It’s up to you to fire tags based on changes in your app.
This plugin will fire a new event called gatsbyRouteChange
on Gatsby's onRouteUpdate
(only if the consent was given by a visitor). To record this in Google Tag Manager, we will need to add a trigger to the desired tag to listen for the event:
In order to do that, go to Tags. Under Triggering click the pencil icon, then the ”+” button to add a new trigger. In the Choose a trigger window, click on the ”+” button again. Choose the trigger type by clicking the pencil button and clicking Custom event. For event name, enter gatsbyRouteChange
. This tag will now catch every route change in Gatsby, and you can add Google tag services as you wish to it.
Here you place your Facebook Pixel ID.
You can use a custom cookie name if you need to!
Thanks goes to these wonderful people who helped shaping this project.