Settings and operation

Open the settings via Modules → Module Manager → WEB Vision – Meta Pixel a Conversions API → Configure.

If you run several shops (multistore), the settings are saved for the shop selected in the admin header. Settings saved for “all shops” apply to shops that have no settings of their own.

• Setup status: shows what is still missing (Pixel ID, token, consent).
• Basic settings: Pixel ID, access token, test code, product marking, how consent is handled and the API version.
• Event queue: events waiting to be sent, sent, failed, the latest errors and the Send again button.
• Cron: the address for the events cron.
• Product feed: see Product feed.

The product marking in the feed and in the Pixel must be the same as in the catalog in Meta:

• Product ID,
• Product ID and combination,
• Reference.

Meta occasionally ends support for an old API version. Then change the API version in the settings to a higher one.

The Pixel starts only after consent to the Marketing category. If consent is handled by a tool other than the Cookie banner module, choose Handled by another tool. Details are in the chapter Installation.

Page view, product and category view, search, add to cart, begin checkout, payment selection and purchase.

• Page events are created on the server. The browser sends them to the Pixel after consent. The module puts the same events into a queue for the Conversions API (only if the visitor has consented).
• Add to cart and payment selection are reported to the module by the browser, but the event is built by the server from the shop’s data. The price and product are not taken from the browser.
• Purchase is created on the order confirmation page, only with a valid order key. The event ID is fixed, so reloading the page does not duplicate the purchase.
• Customer data (e-mail, phone, name, city, ZIP, country) is sent only as a SHA-256 fingerprint. The IP address and browser go to Meta unchanged, as the Conversions API requires.
• The queue is sent after the page has been delivered to the visitor. Failed attempts are repeated with a growing wait (at most 8 attempts). Sent events are deleted after 7 days, failed ones after 30 days.
• Robots and search engines are not measured.
• Cookie banner: the Meta Pixel is loaded by JavaScript, so the Cookie banner does not find it in the page. The module notifies it itself. Meta appears in the settings window under Marketing, and when consent is withdrawn the cookies _fbp and _fbc are deleted.
• For guests (without registration) Meta receives data from the moment they enter their details at checkout.