Documentation

Meta pixel extension loads JavaScript before consent in AEP

Last update: Thu Feb 05 2026 00:00:00 GMT+0000 (Coordinated Universal Time)

The meta pixel extension in Adobe Experience Platform (AEP) loads the fbevents.js script before consent is provided. Although the script initializes immediately, it queues all events and processes them only after consent is granted. This behavior ensures that initialization occurs without transmitting data before consent.

Description description

Environment

Adobe Experience Platform (AEP)

Issue/Symptoms

  • The fbevents.js script for the meta pixel extension loads before consent is obtained.
  • Events queue automatically and process only after consent is granted.
  • No data is transmitted before receiving consent, ensuring event handling remains gated.

Resolution resolution

Follow these steps to understand and address the issue:

  1. Go to Tags > Extensions > Select Meta Pixel. Confirm that the Meta Pixel extension loads fbevents.js by default. Check the extension details to verify that fbevents.js is part of the default load behavior.
  2. Navigate to Tags > Rules. Review the rule conditions for consent and confirm that event actions are gated by the consent management settings. Note that fbevents.js loads immediately, but no events are sent until the user provides consent.
  3. Verify with your legal or compliance team that this behavior meets your organization’s data‑privacy and consent‑management requirements.
  4. Test your implementation to ensure no events are transmitted before consent is granted.
  5. After consent is provided, verify that queued events are processed correctly.

Note: The fbevents.js can’t be blocked from loading before consent. Only event transmission is controlled by the consent state.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f