Analytics Mania

Meta Offline Conversion Tracking with Google Tag Manager

The video walks through configuring server‑side Google Tag Manager (GTM) to capture offline purchase events from a physical store and forward them to Meta’s Conversions API. It uses a Stape‑hosted GTM container, creates a custom data client to accept webhook payloads from a point‑of‑sale (POS) system, and maps the incoming JSON to the fields required by Facebook. Key steps include importing the Stape data client template, defining an accepted path (e.g., /webhook), publishing the container, and handling preview‑mode headers so test requests appear in GTM. The presenter also shows how to extract customer identifiers—email, first and last name—from the POS payload and feed them into user‑data parameters for accurate offline matching. A concrete example demonstrates a loyalty‑card purchase where the email address is tied to the card. The POS sends a sample request containing customerInfo and purchaseDetails; the tutorial uses an array‑map variable to rename SKU, QTY, and unit_price to Facebook’s required ID, quantity, and item_price fields. The speaker highlights firewall or CDN blocks as common pitfalls and offers a Stape preview‑header power‑up to simplify debugging. By publishing the configured tag with the Facebook pixel ID and access token, retailers can push offline sales data into Meta’s ad platform, enabling better attribution, optimized bidding, and a unified view of online and offline performance.