Facebook pixelId not working about gatsby-plugin-gdpr-cookies

[axelra82]

From what I can tell the getCookie(options.cookieName) function is the issue. It's supposed to return "true", but gets null, but only for the Facebook pixel. I've tried different names, default name (i.e. not giving it a specific cookie name). Makes no difference, the return from getCookie is always null.

Logs

GA

–––––––– GET COOKIE FUNCTION RETURN ––––––––
["; custom-gdpr-google-analytics=true", ";", "true"]
––––––––––––––––

FB

–––––––– INITIALIZE FACEBOOK PIXEL ––––––––
{cookieName: "custom-gdpr-facebook-pixel", pixelId: "0123456789"}
––––––––––––––––

–––––––– TRACK FACEBOOK PIXEL ––––––––
{cookieName: "custom-gdpr-facebook-pixel", pixelId: "0123456789"}
––––––––––––––––

–––––––– GET COOKIE FUNCTION RETURN ––––––––
null
––––––––––––––––

[axelra82]

Solution

I use react-cookie-consent for user consent and realized that the cookie name was coming from there.

Giving my cookies in GDPR plugin the same name, everything works fine. Since the GDPR plugin by itself doesn't set any cookie name, and I had two different cookie names in the plugin it would never match.

{
	resolve: `gatsby-plugin-gdpr-cookies`,
	options: {
		googleAnalytics: {
			trackingId: process.env.GATSBY_GOOGLE_ANALYTICS_TRACKING_ID,
			cookieName: 'some-custom-cookie-name',
		},
		facebookPixel: {
			pixelId: process.env.GATSBY_FACBOOK_PIXEL_ID,
			cookieName: 'some-custom-cookie-name',
		},
		environments: ['production']
	},
},

Not sure how different cookie names (as per the documentation) is supposed to work. It all depends on you cookie consent package in the end and how you set it up.

Having different cookie names will allow for more granular control on a "cookie info page" I guess.

Anyway, I'm just happy I was able to resolve this and hopefully it can help anyone else searching for the same thing.