{"id":9048,"date":"2021-11-29T13:03:46","date_gmt":"2021-11-29T12:03:46","guid":{"rendered":"https:\/\/www.myagileprivacy.com\/how-to-install-facebooks-gdpr-compliant-pixel\/"},"modified":"2026-01-02T15:11:22","modified_gmt":"2026-01-02T14:11:22","slug":"how-to-install-facebooks-gdpr-compliant-pixel","status":"publish","type":"post","link":"https:\/\/www.myagileprivacy.com\/en\/how-to-install-facebooks-gdpr-compliant-pixel\/","title":{"rendered":"How to install Facebook's GDPR-compliant Pixel"},"content":{"rendered":"

In general, the Facebook Pixel is used to track user behavior on your website, such as page views and conversions, and sends this data to Facebook. With the information collected, you can create custom audiences, run remarketing campaigns, and optimize your campaign targeting. This includes automatically excluding users who have already completed \"conversions,\" such as making a purchase, filling out a form, or adding products to their shopping cart.<\/p>\n

Due to regulations like the GDPR and cookie law, it is essential to obtain explicit consent from users before engaging in these activities.<\/p>\n

In this article, we'll explore how to bring the Facebook Pixel into compliance with GDPR regulations using the My Agile Privacy\u00ae<\/sup><\/strong> WordPress plugin. Below is a step-by-step guide:<\/p>\n

Solution 1 \u2013 Automatic Scan<\/h2>\n

You can take advantage of the advanced \"Cookie Shield\" feature.
\nThis mode automatically detects the Facebook Pixel on your website. By setting the Shield to \"Learning\" mode, the plugin will scan your site\u2019s pages and configure the necessary settings. You may also choose manual configuration if you prefer.<\/p>\n

Solution 2 \u2013 Manual Configuration<\/h2>\n

Part 1 \u2013 Identify Your Pixel Code<\/h3>\n

The first step is to locate your Facebook Pixel code.
\nIt will look similar to this example below:
\n\"\"<\/p>\n

Part 2 \u2013 Find the Facebook Pixel Cookie in the My Agile Privacy\u00ae<\/sup> Cookie List<\/h3>\n

Go to the \"My Agile Privacy\u00ae<\/sup>\" section in your WordPress admin menu and select \"Cookie List.\" Here, you\u2019ll see a list of cookies imported during plugin installation.
\nBy default, these cookies will be in draft status. Be sure to publish only the cookies necessary for your website.
\n\"\"<\/p>\n

On this screen, you\u2019ll see a number of columns:<\/p>\n

    \n
  • Cookie<\/em> Name: the name of the cookie.<\/li>\n
  • Is Necessary<\/em>: Indicates whether the cookie is essential for your website\u2019s functionality. If rejecting the cookie makes your site unusable, it\u2019s considered essential. This detail is pre-filled for each cookie.<\/li>\n
  • Auto Update<\/em>: Specifies if the reference text for the cookie (explained next) is kept up to date automatically. If set to \"yes,\" we will handle updating the cookie references for GDPR compliance.<\/li>\n
  • Installation Type<\/em>: Shows the chosen insertion type for the cookie. This value changes based on the inclusion method required, which will be covered in these guides.<\/li>\n<\/ul>\n

    To install the Facebook Pixel cookie, search the list for the entry titled \"Facebook Remarketing (Facebook, Inc.)\" and click on it.
    \nThe detail page provides a pre-filled informational text and two blank fields where you can enter the required code.
    \nThe pre-filled text appears in your cookie policy and is automatically updated for compliance when \"Allow Automatic Update\" is enabled.
    \nRight below the text, you\u2019ll find the option to select the \"Type of Installation\" (Javascript and Noscript, or Raw).
    \nKeep \"Javascript-noscript code\" selected; you will then see two fields:<\/p>\n

      \n
    • Javascript Activation Code<\/em> \u2013 where to enter your main Facebook Pixel code<\/li>\n
    • NoScript code \u2013 where to enter any NoScript code if necessary<\/li>\n<\/ul>\n

      \"\"<\/p>\n

      Part 3 \u2013 Enter the Facebook Pixel Code<\/h3>\n

      Now you simply need to enter your Facebook Pixel code, found in the first step, into the two fields as shown in the image below.
      \nBe sure to insert the code WITHOUT the opening and closing <script><\/em> and <\/script><\/em> tags, or <noscript><\/em> and <\/noscript><\/em> tags.
      \nDon\u2019t forget to save and publish your Cookie by clicking the blue \"Publish\" button in the top right corner.<\/p>\n

      Final Step \u2013 Verifying Proper Operation<\/h2>\n

      Check that the Facebook Pixel is correctly installed on your website using tools provided by Google or Facebook. Visit any page of your site to ensure that the Facebook Pixel remains inactive until the user has given explicit consent to cookie installation. Users can provide this either by clicking \"I agree\" on the cookie consent banner or by activating the Facebook cookie in the \"Customize\" section.<\/p>\n","protected":false},"excerpt":{"rendered":"

      In general, the Facebook Pixel is used to track user behavior on your website, such as page views and conversions, and sends this data to Facebook. With the information collected, you can create custom audiences, run remarketing campaigns, and optimize your campaign targeting. This includes automatically excluding users who have already completed \"conversions,\" such as […]<\/p>\n","protected":false},"author":1,"featured_media":8674,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[33],"tags":[35],"class_list":["post-9048","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cookies","tag-free"],"acf":{"visibilita_box_autore":false,"autore_associato":null,"elenco_faq_articolo":null,"url_esterno":"","titolo":"Facebook pixel"},"_links":{"self":[{"href":"https:\/\/www.myagileprivacy.com\/en\/wp-json\/wp\/v2\/posts\/9048","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.myagileprivacy.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.myagileprivacy.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.myagileprivacy.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.myagileprivacy.com\/en\/wp-json\/wp\/v2\/comments?post=9048"}],"version-history":[{"count":10,"href":"https:\/\/www.myagileprivacy.com\/en\/wp-json\/wp\/v2\/posts\/9048\/revisions"}],"predecessor-version":[{"id":15174,"href":"https:\/\/www.myagileprivacy.com\/en\/wp-json\/wp\/v2\/posts\/9048\/revisions\/15174"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.myagileprivacy.com\/en\/wp-json\/wp\/v2\/media\/8674"}],"wp:attachment":[{"href":"https:\/\/www.myagileprivacy.com\/en\/wp-json\/wp\/v2\/media?parent=9048"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.myagileprivacy.com\/en\/wp-json\/wp\/v2\/categories?post=9048"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.myagileprivacy.com\/en\/wp-json\/wp\/v2\/tags?post=9048"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}