Case study · Meta Pixel & CAPI

Meta Pixel & Conversions API Setup for the Amanda Trends and Venture Wix Store

Wix browser events and server-side CAPI events, counted once.

Client
Amanda Trends and Venture
Industry
Online Retail (Wix Store)
Channel
Meta Ads
  • Meta Pixel
  • Conversions API
  • GA4 eCommerce
  • Server-side GTM
  • Custom Tracking Domain
Amanda Trends and Venture Meta Pixel & CAPI
Web GTM container pairing Meta Pixel browser tags with server-bound GA4 events
01/ 09

Web GTM container pairing Meta Pixel browser tags with server-bound GA4 events

Setup architecture

Amanda Trends and Venture tracking architecture

How the setup in this project is connected, from the website to each platform.

About Amanda Trends and Venture

Amanda Trends and Venture (amandatrendsandventure.org) is an online store built on Wix, with its Meta Pixel connected through Wix's built-in Meta partner integration.

Project overview

Amanda Trends and Venture's Wix store already sent browser events to Meta through Wix's partner integration, but browser-only events are exposed to ad blockers and tracking prevention. The store needed a Conversions API layer that could send the same funnel events from a server without double counting them.

I built a web GTM container that pairs each Meta event with a server-bound GA4 event, routed that stream to a server-side GTM container on Stape behind a custom tracking subdomain, and forwarded it to Meta and GA4. Every step was checked in GTM preview, GA4 DebugView and Meta Events Manager test events.

Goals

  • Send PageView, ViewItemList, ViewContent, AddToCart, InitiateCheckout and Purchase through the Conversions API
  • Deduplicate server events against the browser events from Wix's Meta integration
  • Serve server-side tracking from a first-party tracking subdomain
  • Track the GA4 ecommerce funnel from product list to purchase
  • Capture Wix checkout steps such as contact and address info submission

Challenges

  • Browser-only Pixel events are lost to ad blockers and tracking prevention
  • Wix already fires its own browser Pixel events, so server events had to match them for deduplication
  • Wix checkout steps are not standard GA4 ecommerce events
  • One GA4 stream had to feed both Meta and GA4 from the server container

Strategy

I kept Wix's Meta partner integration for browser events and added a server-side layer next to it. In web GTM, Meta Pixel tags sit alongside matching "Fb Server" GA4 event tags that send each interaction to a server-side GTM container on Stape, served from a custom tracking subdomain. There, a Conversions API tag forwards the events to Meta with event IDs that line up with the browser events, so Meta deduplicates the pair, while a GA4 tag records the same ecommerce stream.

What I implemented

Web GTM container

  • Meta Pixel browser tags for PageView, View Item List, ViewContent, AddToCart, Checkout and Purchase
  • Matching "Fb Server" GA4 event tags that send each interaction to the server container
  • GA4 events for Contact Info Submit and Address Info Submit on the Wix checkout
  • GA4 configuration tag on all pages

Server-side GTM on Stape

  • Conversions API tag fired from the incoming Meta event stream
  • GA4 ecommerce tracking tag fired on all GA4 events
  • Stape container on a custom tracking subdomain, verified as Ready with a CNAME record

GA4 eCommerce

  • page_view, ViewItemList, view_item, add_to_cart, begin_checkout and purchase events
  • Verified the full sequence in GA4 DebugView during a test order

QA in Meta Events Manager

  • Test events checked for PageView, ViewItemList, View content, Add to cart, Initiate checkout and Purchase
  • Browser copies received through the Wix partner integration and server copies through the manual CAPI setup
  • Server copy of each event marked as deduplicated
  • Wix's own WixOrderPlaced event confirmed alongside Purchase on the test order

Tools used

  • Meta Pixel
  • Meta Conversions API
  • Google Tag Manager (Web & Server)
  • Stape.io
  • Google Analytics 4
  • Wix

Results

  • Purchase and Initiate checkout received from both browser and server, with the server copy deduplicated
  • Add to cart, View content, ViewItemList and PageView received from browser and server and deduplicated
  • Server-side Conversions API and GA4 ecommerce tags each fired 13 times in preview, with no tags left unfired
  • Full GA4 funnel from page_view through view_item, add_to_cart and begin_checkout to purchase verified in DebugView
  • Custom tracking subdomain live on Stape, with 559 requests sent in the current cycle

Want results like Amanda Trends and Venture?

Get a free audit of your tracking and ad account. Usually replies within 1–2 hours.