Learn how to set up tools like PostHog, ClickFunnels, WordPress, and Shopify in a way that actually matches your business model, fixes broken attribution, and surfaces opportunities for profit.
This guide explains how to send conversion events such as CompleteRegistration, Lead, AddToCart, InitiateCheckout, and Purchase to Meta, along with all available customer context and event metadata, including email address, first and last name, phone number, address information, order value, currency, and other matching parameters that help improve attribution and event match quality.
A filtered pageview transformation copies a real client $ip to the current person property and sets $initial_ip only once; it affects new events, not existing profiles.
The useful hiring test is whether a provider can reconcile customer journeys and revenue against your CRM or checkout, not merely install scripts and make pixels fire.
Ask candidates for a sample tracking plan, QA evidence, and an experiment decision process; the handover should let your team audit and extend the setup independently.
Reserve UTMs for incoming campaign links: tagging on-site links can overwrite the original source. Keep approved names in a shared registry and test attribution through conversion.
Convert each transaction at an explicit rate date, then reconcile refunds and duplicate IDs; for experiments, revenue per participant includes nonbuyers, unlike average order value.
Choose a code manager for flexible browser tracking or a dedicated plugin for easier setup and WooCommerce events; Zapier alone cannot provide replay or autocapture.
A storefront snippet or app covers replay and browser behavior, while Customer Events or Web Pixels cover checkout; verify both layers and avoid duplicate purchase events.
Start with spend by product and event volume, then narrow replay capture and noisy events; a $0 billing limit caps charges but stops ingestion when reached.