Venon can load the Meta and Taboola browser pixels itself through its storefront tracking script. This depends on the connected ad account settings. Connecting an integration alone is not enough.
When the pixels load
Meta: Venon uses the selected pixel for an ad account with Use Conversion API turned on. It initializes the pixel and sends a browser
PageView.Taboola: Venon uses the Taboola account with Use Conversion API turned on. It loads the Taboola pixel and sends a browser
page_view.
This happens on pages where the Venon storefront script runs, including external pages where you installed the same shop script.
Check the account settings
Open Integrations.
Next to Meta Ads or Taboola, click Manage and open Server-to-Server.
Check Use Conversion API for the intended ad account. For Meta, also check Choose Pixel.
If you change these settings, click Save.
In this demo example, the first Meta account has Use Conversion API enabled and a pixel selected. The second account is disabled. These settings also control server-side conversion sending, so do not change them only as a browser-pixel toggle.
Browser pixels and server-side conversions are different
A browser page view does not confirm that an order conversion was delivered through the Conversion API. Follow Send Conversions to Meta Ads for the Meta setup. For the Taboola connection and ad URL parameters, see Taboola.
If another app or tag manager loads the same pixel
Review the existing setup before adding a second installation. Venon can reuse an existing Meta fbq function, but still initializes the selected pixel and sends a page view. Do not assume that 2 independent installations will deduplicate every browser event. Check the events in the ad platform before removing or adding tracking code.