Triangle Digital
Advertising

Shopify Meta, TikTok and Pinterest Pixel Setup with One GTM Container

By Alessandro Colarossi, Founder, Triangle Digital · Published · 9 min read

Short answer

To run Meta, TikTok, Pinterest and other ad pixels on Shopify from one Google Tag Manager container: build a single GA4-format data layer (view_item, add_to_cart, begin_checkout, purchase), then create each platform's tag in GTM on the same triggers and map the event names and parameters (for example purchase becomes Meta Purchase, TikTok CompletePayment and Pinterest Checkout). Switch off the platforms' separate Shopify apps so nothing is counted twice, and add consent checks to every non-Google tag.

Why use one container instead of a pixel app per platform

Most Shopify stores accumulate tracking one app at a time: a Meta app, a TikTok app, a Pinterest app, each installing its own pixel. It works until it does not: pixels conflict, page weight grows, each platform reports a slightly different revenue number, and nobody can answer what is actually firing.

  • Consistent numbers. Every tag reads the same value, currency and items from the same data layer.
  • One place to debug. GTM Preview shows every tag from every platform on every event.
  • One consent policy. You apply consent rules once, centrally. See Consent Mode v2.
  • Portability. Switching or adding a platform means adding a tag, not installing another app.

The architecture: one data layer, many tags

  1. Shopify produces events: a theme data layer snippet on the storefront and a Customer Events pixel in checkout. See the data layer guide and Customer Events guide.
  2. Every event is pushed to dataLayer in GA4 ecommerce format, which makes it a convenient universal format.
  3. GTM Custom Event triggers listen for those events.
  4. Each platform's tag fires on the relevant trigger and maps the GA4-format fields to the platform's own event names and parameters.

Event mapping across platforms

These are the standard ecommerce events each platform expects, mapped from the GA4 event names in your data layer. Always confirm against each platform's current documentation, since naming and requirements change.

GA4 data layer events mapped to ad platform events
Data layer eventMetaTikTokPinterestSnapchat
page_viewPageViewPage view (automatic)PageVisitPAGE_VIEW
view_itemViewContentViewContentPageVisit (with product data)VIEW_CONTENT
searchSearchSearchSearchSEARCH
add_to_cartAddToCartAddToCartAddToCartADD_CART
begin_checkoutInitiateCheckoutInitiateCheckoutCheckout (start, if used)START_CHECKOUT
add_payment_infoAddPaymentInfoAddPaymentInfo-ADD_BILLING
purchasePurchaseCompletePaymentCheckoutPURCHASE

Each platform also wants its own parameter shapes: Meta takes content_ids, contents, value and currency; TikTok takes a contents array with content_id and price; Pinterest takes line_items, value and order_quantity. In GTM, you map these from your Data Layer Variables, so the data layer itself stays platform-neutral.

Platform-by-platform notes

Meta (Facebook and Instagram)

Use the Meta Pixel template in GTM with the standard events above. If you also use a server-side integration such as the Conversions API, send a shared event_id from both browser and server so Meta can de-duplicate. Client-side GTM is the foundation, and server-side APIs are an optional layer on top.

TikTok

Use the TikTok Pixel template. Make sure contents includes content_id, content_type and quantity. The purchase event is CompletePayment, not Purchase.

Pinterest

Use the Pinterest Tag. Purchases report as the checkout event type. Pass value, currency and order_quantity, and include product data if you use catalogs.

Microsoft Advertising and Microsoft Clarity

Microsoft Ads uses the UET tag: load it on all pages, then send a purchase event with revenue value and currency to power conversion goals. Clarity is behavioral analytics (session replay and heatmaps) and loads on all pages like an analytics tag, so it should respect analytics consent.

LinkedIn, X, Criteo and Hotjar

  • LinkedIn Insight Tag: load site-wide, then track conversions with event-based conversion rules tied to your purchase or lead events.
  • X (Twitter): base tag plus event pixels for purchase and other actions.
  • Criteo: product-level events (view item, view basket, transaction) that need item IDs matching your Criteo catalog feed.
  • Hotjar: behavior analytics loaded site-wide, subject to analytics consent.

Avoid double counting

The most common failure of multi-platform tracking is the same purchase being reported twice. Typical causes:

  • The platform's own Shopify channel app is still installed and still firing its pixel, alongside your GTM tag.
  • Hardcoded pixel code left behind in theme.liquid or old Additional Scripts.
  • A purchase event pushed from both the theme and the Customer Events pixel.
  • No unique order ID passed to platforms that support de-duplication.

Decide, per platform, whether GTM or the channel app owns tracking, and disable the other. Keep the app for catalog and campaign features if you need them, but turn off or remove its duplicate pixel events. Then verify with a test order. See the debugging guide.

Google tags read Consent Mode natively. Meta, TikTok, Pinterest, Snapchat and the rest do not, so each needs an explicit consent check in GTM (for example, require ad_storage before the tag may fire). Without it, these tags fire for visitors who declined.

Test each platform with its own helper

  • Meta: Meta Pixel Helper and the Test Events tab in Events Manager.
  • TikTok: TikTok Pixel Helper and Events Manager diagnostics.
  • Pinterest: Pinterest Tag Helper.
  • Microsoft Advertising: UET Tag Helper.
  • Snapchat: Snap Pixel Helper.

Use GTM Preview as the source of truth for what fired, and the platform tools to confirm it was received and parsed correctly.

The Comprehensive pack covers this

The Shopify DIY Tagging Comprehensive Pack is built for exactly this: one GTM container supporting GA4, Google Ads, Meta, Microsoft Ads, Microsoft Clarity, TikTok, Pinterest, LinkedIn, X, Snapchat, Criteo and Hotjar, with consent-aware tag firing, Enhanced Conversions and duplicate-conversion prevention guidance. See what is included, or compare options in DIY vs agency vs app.

Frequently asked questions

Can I run Meta, TikTok and Pinterest pixels from Google Tag Manager on Shopify?

Yes. Build one GA4-format data layer, then create each platform's tag in GTM on the same triggers and map event names and parameters from the data layer.

Should I use the Shopify channel apps or GTM for ad pixels?

Pick one per platform. Channel apps are quicker but each installs its own pixel. GTM gives you one place to control and debug every pixel. Do not run both for the same events or you will double count.

What is the TikTok equivalent of the Purchase event?

TikTok's standard purchase event is CompletePayment. Meta uses Purchase and Pinterest reports purchases as the Checkout event type.

Do Meta and TikTok tags respect Google Consent Mode?

Not automatically. You need to add consent checks in GTM for each non-Google tag, for example requiring ad_storage to be granted before the tag fires.

Which platforms does the Comprehensive tagging pack support?

GA4, Google Ads, Meta, Microsoft Ads, Microsoft Clarity, TikTok, Pinterest, LinkedIn, X, Snapchat, Criteo and Hotjar, all from one Google Tag Manager container.

Skip the build

Get a ready-to-import Shopify Google Tag Manager container

Shopify DIY Tagging Packs ship a tested GTM container, the Shopify data layer snippet, the Customer Events pixel and a step-by-step install guide. Own the container, no monthly fee, 30 minutes of setup support included.