How to Set Up Meta, TikTok, Snapchat and Other Ad Pixels on Magento 2 From One Admin

TL;DR

Nine pixels, one Magento admin, two menu homes. Every section asks the same questions in the same order, except that Klaviyo wants a public API key, X wants an event ID for every event, and OpenAI Ads needs the complete snippet. Since July 2026 the extension also writes the Content Security Policy hosts for the pixels its change log names while you have them switched on, which, on our reading, is the practical reason to keep pixels out of theme templates. And the Track Events lists differ from platform to platform.

Key Takeaways

• All nine client-side pixel sections are marked PRO VERSION ONLY in the user guide [1].
• Meta, Reddit, TikTok and Bing UET live under Admin → WeltPixel → Google Analytics 4 eCommerce PRO GTM Settings; the other five are separate Admin → WeltPixel → <Platform> Pixel Tracking entries [1].
• Klaviyo takes a Public API Key and has no Product Identifier field, X needs a unique event ID from your X Ads account for each event, and the OpenAI Ads snippet must contain both the oaiq loader and the init call [1].
• Since v1.17.1 (July 7, 2026), the extension adds CSP hosts for the eight pixels its change log names only while each is active [1]. Add pixels through the admin and delete any theme copy (our reading of the change log).
• Reddit's pixel list has nothing between AddToCart and Purchase, and OpenAI Ads offers no search or wishlist event [1]. Choose optimization events from each section's own list.
• Every section closes with the same instruction: save the configuration and flush the Magento cache [1].

The six settings most pixel sections share

Open any pixel section in the GA4 PRO admin and the sequence is the same, apart from the three exceptions below [1]:

1. An enable switch, for example Enable Snapchat Pixel Tracking, set to Yes.
2. The code field, where the platform's snippet goes (Meta Pixel Tracking Javascript Code, TikTok Pixel Base Tracking Code and so on).
3. Track Events, a multiselect of the events this pixel may send.
4. Product Identifier [ ID / SKU ], the product reference the platform receives.
5. Grand Total Calculation Settings, where Order Success Page Total Calculation offers Default (Uses GA4-level settings), Grandtotal or Subtotal.
6. The closing line: "Save the configuration and flush the Magento Cache."

Two of these deserve a decision before you paste anything. The product identifier should match how your catalog on that platform is keyed, since SKUs reported against a catalog built on IDs can fail to match. The grand-total block starts on the GA4-level setting, and what happens when one platform's value drifts away from GA4 is covered in our article on why GA4 and Magento sales reports don't match.

The flush in step six matters because pages already stored in Full Page Cache were rendered before your change, and they keep serving the old markup until they are cleared.

Where does each pixel live, and what does its code field take?

Four pixels sit inside Admin → WeltPixel → Google Analytics 4 eCommerce PRO GTM Settings (shortened to GA4 PRO GTM Settings in the table), each in its own settings group, for example Meta Pixel Tracking Settings → Meta Pixel Tracking Configuration. The other five are top-level entries such as Admin → WeltPixel → Snapchat Pixel Tracking [1]. If you are adding a pixel to a store that already runs Meta, the new one may well not sit next to it.

Meta documents its base code under Ads Manager > Events Manager [4], and TikTok sends you to Tools, then Events Manager, in TikTok Ads Manager [5]. For the rest, take the code from your ads account's events tool and paste the whole snippet.

Three sections ask for something else.

Klaviyo takes a key in place of a script, found in your Klaviyo account settings under API Keys, and its section has no Product Identifier choice at all [1]. It is also the one email and SMS platform on this page.

X asks for more than a snippet. Twitter Event IDs wants "unique Twitter ID values for each GA4 tracking event", each one issued by your X Ads account [1], so create the events on the X side first. If you configured X before v1.15.7 (September 2, 2025), check the mapping: that release fixed Purchase and Add Payment Info arriving with zero parameters, and mappings lost when the extension was disabled and re-enabled [1].

OpenAI Ads is specific about what you paste. The field expects the Measurement Pixel snippet, which "must contain both the oaiq loader and the oaiq('init', { pixelId: '...' }) call" [1], so a bare pixel ID will not do. This pixel is the newest of the nine, added in v1.17.3 on August 3, 2026 [1].

What enabling a pixel does to your Content Security Policy

The v1.17.1 change log, July 7, 2026: "Hosts for Meta, TikTok, Reddit, X Ads, Bing, Klaviyo, Snapchat and Pinterest are only added to the store's policy while the respective pixel is active, instead of all supported hosts being whitelisted at all times" [1]. Stores enforcing strict CSP need no manual whitelisting for the enabled integrations [1]. The list names eight because it predates the OpenAI Ads pixel, which shipped in v1.17.3.

The Magento half is Adobe's: "In Adobe Commerce 2.4.7 and later, CSP is configured in restrict-mode by default for payment pages in the storefront and admin areas, and in report-only mode for all other pages" [2]. A module can add domains to the policy, for example through a csp_whitelist.xml file [3]. What restrict mode does to a script whose host is not listed is covered in our piece on ad blockers and browser privacy on Magento 2.

Payment pages means checkout. That is the stretch of the funnel you can least afford a silent pixel on.

Put the two together and a working rule follows. The change log does not spell it out, so take it as our reading: a pixel enabled in the extension's admin brings its hosts onto the allow list, while a snippet pasted into a theme template brings none, and on a restrict-mode payment page that snippet's script can be refused. Add pixels through the admin. When you move one out of a theme, delete the theme copy in the same deploy, both to avoid sending events twice and because the hosts now come and go with the admin switch.

Which events can each pixel send from the browser?

The Track Events options in each pixel section, labels as the guide prints them [1]:

Read across the rows, not down one. Reddit's list has nothing between AddToCart and Purchase, so its browser pixel offers no checkout or payment step to optimize on. OpenAI Ads has InitiateCheckout but no payment step, and neither search nor wishlist. Category views exist only for Meta, Microsoft Ads, X, Klaviyo and Pinterest. Page views appear in three lists (Pinterest's PageVisit, Klaviyo's View Page, OpenAI's PageView), and Meta gained a PageView event in v1.17.4 that can be enabled on the browser pixel [1]. TikTok's list carries PlaceAnOrder, CompletePayment and Purchase side by side; why it has three is told in our TikTok Events API guide.

Every list above belongs to a browser pixel. Each server-side addon has its own section and its own event list, and nothing in this table describes it. Pick each campaign's optimization event from the pixel section it will actually run on.

What the pixel section leaves to other settings

Consent is decided elsewhere: with Consent Management Method set to Magento Cookie Restriction Mode the extension holds the pixels until the visitor accepts cookies (the fix that extended this beyond Meta shipped in v1.15.9), under External CMP that is your CMP's job (which method fits your store), and server-side events wait for consent only since v1.17.4, with Require Visitor Consent for Server-Side Events switched on (it is off by default) [1]; the Conversions API addons follow the same setting, and our guide to server-side events and consent covers the per-addon details.

Server-side delivery is decided elsewhere too. Each pixel section points to a matching addon that is installed and enabled separately [1], and each has its own setup walkthrough: Meta Conversions API, Snapchat, Pinterest, Microsoft Ads, Klaviyo and OpenAI Ads, with TikTok covered in the Events API guide above. For Reddit and X, the addon pages are the reference: the Reddit Conversions API addon and the X (Twitter) Ads Conversions API addon, plus our step-by-step X Conversions API setup guide.

How do you check a new pixel after saving?

1. Flush the Magento cache, as the section tells you to [1].
2. Load a product page and a category page in a fresh browser session, then watch the events arrive in the platform's own events tool.
3. Open the developer console on the checkout page. A script blocked by Content Security Policy is reported there [2], which is a quick way to catch a theme copy that the policy no longer covers.
4. If your pixels have been running since before April 2025, confirm you are past v1.14.19 (April 8, 2025), which fixed social pixel events sometimes being sent with cached IDs so that an event registered only the first time [1].

FAQ

Where do I find the Meta pixel code for Magento 2?

Meta documents the base code under Ads Manager > Events Manager [4]. Paste the whole base code into Meta Pixel Tracking Javascript Code, set Enable Meta Pixel Tracking to Yes, then save and flush the cache [1].

Do I need the server-side addon to use a pixel?

No. The pixel sections are part of GA4 PRO itself, and each platform's addon is a separate install you add when you want server-side events for that platform [1].

Does the pixel send the same events as the addon?

Treat them as two configurations. The lists on this page are the browser pixels'; each addon has its own event setting in its own section, and the per-platform setup guides linked above describe those.

Can I leave my Snapchat or Reddit pixel in the theme?

You can, but on our reading of the change log a theme copy gets no allow-list entry from the extension [1], and on a restrict-mode payment page [2] its script can be refused.

Every pixel on this page is configured inside the PRO edition of the Magento 2 Google Analytics 4 extension, currently v1.17.5, released September 16, 2026 [1], with a matching server-side addon per platform. The differences between editions are laid out in GA4 Standard vs PRO on Magento 2.

Sources

1. WeltPixel Google Analytics 4 User Guide and Change Log, v1.17.5, September 16, 2026, retrieved September 29, 2026, https://docs.weltpixel.com/GA4/User-Guide-WeltPixel-Google-Analytics-4.html
2. Content security policy overview, Adobe Commerce Operations documentation, page last updated August 19, 2026, retrieved September 28, 2026, https://experienceleague.adobe.com/en/docs/commerce-operations/security-and-compliance/content-security-policy
3. Content security policies, Adobe Commerce PHP Developer Guide, retrieved September 28, 2026, https://developer.adobe.com/commerce/php/development/security/content-security-policies
4. Get started with the Meta Pixel, Meta for Developers, retrieved September 28, 2026, https://developers.facebook.com/docs/meta-pixel/get-started/
5. Set up and Verify Pixel, TikTok Ads Manager Help Center, article last updated June 2026, retrieved September 28, 2026, https://ads.tiktok.com/help/article/get-started-pixel?lang=en