adobe/reactor-extension-meta-pixel

Adobe Experience Platform tags extension that sends tracking data using the Meta Pixel library.

reactor-extension-meta-pixel

This is the Meta Pixel extension.

Get started

To get started:

1. Install node.js.
2. Clone the repository.
3. After navigating into the project directory, install project dependencies by running npm install.

Scripts

To run tests a single time, run the following command:

npm run test

To run tests continually while developing, run the following command:

npm run test:watch

To ensure your code meets our linting standards, run the following command:

npm run lint

To create a build, run the following command:

npm run build

To create the extension package, run the following command:

npm run package

License

The code is released under the Apache 2.0 license.

reactor-extension-meta-pixel's Issues

Extension ignores Adobe Launch conditional checks

Discovered that when this extension is used in Adobe Launch it does not respect the conditionals of any rule utilizing it.

Steps

activate extension in Adobe Launch
add a rule in launch to fire pageview call using the extensions pageview option, setting a condition to only activate on a specific page url, set the event to fire on "page bottom"
build and deploy the rule to your site.
verify that the url you specified has the pixel tag.
Results

Page in the conditional has the pixel tag
every other page using the Launch library that rule is made within also implements the pixel tag.
Problems

this implements in China when china is not specified. The call to the pixel is to en_US/fbevents.js which is blocked by the country's firewall. this causes pages to become slow, unresponsive, or blank as the firewall assumes the entire page is trying to access restricted content.
this implements outside of all GDPR solutions that require customer consent to start providing tagging. This in turn then causes all EU pages to break the law by implementing the tag outside of the conditionals.
Solution
Disable the extension and implement the pixel via Adobe Launch's custom code. This works as expected and respects the page conditionals even though the extension implements the very same pixel code.

Initially found by @TroyGottier in the original extension code