Skip to main content

Configuring GDPR Consent Settings in Pixel Plus for PrestaShop

Introduction​

The Pixel Plus module for PrestaShop helps you comply with GDPR regulations by blocking Facebook Pixel and Conversion API (CAPI) events until the customer gives explicit consent.

This guide will show you how to:

  • Detect where your consent manager saves consent data (Cookies, Local Storage, or PrestaShop internal cookie).
  • Configure Pixel Plus to block or allow events accordingly.
  • Test and verify that events are blocked and unblocked correctly based on consent.

Consent data is usually stored in:

  1. Cookies (most common)
  2. Local Storage (less common)
  3. PrestaShop’s internal cookie

When inspecting, accept only marketing/ad customization cookies in your consent popup. This ensures you’re checking the cookies relevant to Facebook Pixel usage.

Option A: Check Cookies (Most Common)​

  1. Open your store in Google Chrome.
  2. Press F12 or right-click → Inspect to open DevTools.
  3. Go to the Application tab.
  4. Expand Cookies and select your store's domain.
  5. Accept only marketing cookies.
  6. Look for:
    • New cookies added after acceptance.
    • Changes in existing cookie values.

Common Cookie Examples:

Cookie NameExample Value
cookieconsent_statusaccepted
cookiebot_consent{"marketing":"true","statistics":"false"}
oneplus_consent{"ads":"true","necessary":"true"}

Take note of:

  • The cookie name, e.g., cookiebot_consent.
  • The value pair, like "marketing":"true".

Option B: Check Local Storage (If Cookies Show Nothing)​

  1. In DevTools, go to Application → Local Storage.
  2. Select your store's domain.
  3. Accept only marketing cookies and look for new entries.

Example:

KeyValue
cookieplusConsent{"marketing":"true","preferences":"false"}

Take note of:

  • The key name.
  • The specific value like "marketing":"true".

If no relevant cookies or local storage entries appear:

  1. In PrestaShop Back Office → Modules → Pixel Plus → GDPR Section, find:

    "If you're using a module that generates the cookie and you don't know the cookie name and value you can click here to generate a temporal token to access the cookies on the front."

  2. Click "Click here".

  3. A new button will appear, click on it to Print the front cookies, unhashed.

  4. A clear list of cookies (including internal ones) will display in a table format.

  5. Click once in the cookie name that's related to the consent.

  6. Now a list of the key > Value pairs will be displayed

  7. Click now on the one related to the marketing / ads

Pixel Plus will auto-fill the cookie name and value.

Step 2: Enable GDPR Blocking in Pixel Plus​

  1. In PrestaShop Back Office → Modules → Pixel Plus → GDPR Section, enable:
Block the script: Enabled

This stops Pixel and CAPI events until consent is confirmed.

Step 3: Configure GDPR Block Mode​

Choose based on what you found:

OptionUse When
CookiesConsent is saved in a browser cookie.
Local StorageConsent is saved in local storage.
Internal CookieConsent is found in PrestaShop’s internal cookie.

A) Using Cookies:​

  • Add the cookie name to look for which you will have found previously:
    Example: cookiebot_consent, cookieconsent_status, oneplus_consent

  • Specific Cookie Value (optional):
    Example: "marketing":"true"
    If multiple values:
    marketing:true|||ads:true

  • Is an External Cookie:
    Set to External if generated by an external service (e.g., Cookiebot).
    Set to PrestaShop if it’s an internal cookie.

B) Using Local Storage:​

  • Enter the key name, e.g., cookieplusConsent.
  • Enter the value pair if applicable, e.g., "marketing":"true".
  • Set Is an External Cookie = External.

If you used the Print front cookies tool, Pixel Plus will autofill:

  • Cookie name.
  • Specific value pair.

Set Is an External Cookie = PrestaShop.

Step 5: Handle Page Reloads After Consent​

ScenarioSetting
Page reloads after accepting/denying consentEnable Page reloads after the consent?
Page does NOT reloadConfigure Selector for the Cookies Button

Step 6: Configuring the Cookies Button Selector (For No Reload Pages)​

  1. Open Chrome DevTools → Elements tab.
  2. Use Select Element tool to click on the cookie banner button.
  3. Check if it’s a <button> or <a> element.
  4. Inspect parent containers for a wrapper.
  5. Build a selector:
.cookie-banner-wrapper button
  1. Enter this in Selector for the Cookies Button.

If:

  • Consent is configured correctly.
  • Events don’t fire after acceptance.

Enable:

Disable advanced consent validation: Enabled

Step 8: Testing GDPR Configuration​

  1. Clear cookies & local storage in your browser.
  2. Open your store.
  3. Open Pixel Helper or Facebook Test Events tool.
  4. Reload the page:
    • No events should fire initially.
  5. Accept only marketing cookies.
  6. Check that:
    • Pixel events (like PageView) start firing.
    • CAPI events log correctly if configured.

Conclusion​

By following these steps, you have:

  • Identified if consent is stored in Cookies, Local Storage, or PrestaShop internal cookies.
  • Configured Pixel Plus to block Facebook Pixel and CAPI events based on consent.
  • Ensured GDPR compliance while maintaining accurate event tracking.
  • Verified correct behavior using Facebook’s debugging tools.

For more information, refer to Facebook’s Consent Guidelines.