trackcombo

lucaswhiather

Track Combo — Conversions API for WooCommerce turns your store into a unified tracking source. One plugin, one tag, and every relevant event reaches Meta (Facebook/Instagram), Google Ads, TikTok, Pinterest, Kwai and any destination you configure in your Track Combo workspace — both from the browser and from the server via the WooCommerce Webhook.
Instead of juggling multiple pixels, conflicting event IDs, and broken deduplication after the iOS 14 / browser tracking updates, Track Combo captures the event once on the storefront, enriches it with first-party data on the server, and fans it out to all destinations with proper event_id deduplication between client and server.
<h3>What the plugin does</h3>
<ul>
<li>Injects the Track Combo web tag in the storefront <code><head></code>.</li>
<li>Exposes <code>window.tcWoo</code> with structured product, cart, order, and customer data so events do not depend on DOM scraping.</li>
<li>Registers a native <code>WC_Webhook</code> that sends <code>order.updated</code> to the Track Combo backend when the order reaches the purchase status you choose.</li>
<li>Deduplicates <code>purchase</code> between the client-side <code>complement_data</code> event and the server-side webhook using the order ID as <code>transaction_id</code>.</li>
<li>Declares compatibility with High-Performance Order Storage (HPOS) and works with both classic shortcode and Checkout Blocks checkouts.</li>
</ul>
<h3>Events sent</h3>
<ul>
<li><code>page_view</code>, <code>search</code>, <code>view_item_list</code>, <code>view_item</code></li>
<li><code>add_to_cart</code>, <code>initiate_checkout</code>, <code>add_shipping_info</code>, <code>add_payment_info</code></li>
<li><code>complement_data</code> (client-side on thank-you page, merged server-side)</li>
<li><code>purchase</code> (server-side via webhook — reliable even when the browser tab is closed)</li>
</ul>
<h3>Why Conversions API</h3>
Tracking quality on WooCommerce stores dropped sharply after iOS 14.5 and the phase-out of third-party cookies. Conversions API (CAPI) is Meta’s, Google’s and TikTok’s answer: send events directly from your server. Track Combo wraps all of them behind one integration.
<h3>Why Track Combo instead of multiple plugins</h3>
<ul>
<li>One plugin instead of one per ad network.</li>
<li>One dedupe boundary handled by Track Combo — no <code>event_id</code> mismatches.</li>
<li>No tag-manager containers to maintain.</li>
<li>Full visibility of every event in the Track Combo dashboard.</li>
</ul>
You need a Track Combo account to use this plugin. Sign up at <a href="https://trackcombo.com/" rel="nofollow ugc">trackcombo.com</a>.
<h3>External services</h3>
This plugin relies on Track Combo (https://trackcombo.com), the service operated by the plugin author, to deliver first-party event tracking and server-side conversion delivery to advertising platforms (Meta Conversions API, Google Ads, TikTok and others). It connects to the following Track Combo endpoints:
<ul>
<li>
Configuration API — <code>https://server.trackcombo.com/integrationwoocommerce</code>. Called only when the store owner saves the plugin settings in WordPress admin (validate the API key, persist the purchase status filter, register the store domain). Data sent: the API key (HTTP header), and the purchase status or store domain string when those are updated. No customer data is sent through this endpoint.
</li>
<li>
Web tag — <code>https://track.track-combo.com/tag/{container_id}.js</code> (or your configured first-party CNAME, e.g. <code>https://tracks.yourstore.com/...</code>). Loaded on every storefront page view to enable client-side event tracking. The tag itself dispatches tracking events from the browser to the Track Combo events endpoint.
</li>
<li>
Order webhook — a WooCommerce webhook registered by the plugin that POSTs the WooCommerce order payload to a URL on <code>server.trackcombo.com</code> whenever an order reaches the purchase status you configure in the plugin settings (default: “Processing”). This enables reliable server-side <code>purchase</code> events even when the customer closes the browser tab.
</li>
</ul>
Track Combo terms of use: https://trackcombo.com/termos-de-uso/ 
Track Combo privacy policy: https://trackcombo.com/politica-de-privacidade/

Track Combo — Conversions API for WooCommerce

Send WooCommerce events (view, add-to-cart, purchase) to Meta CAPI, Google Ads, and TikTok through Track Combo — no extra pixels needed.

shan

Stop paying $30–150/month for a GTM Server Container. Send Conversions API events to Meta, Pinterest, and TikTok directly from your WordPress server. No premium tier, no SaaS subscription.
Three CAPI integrations in one install. Most plugins ship Meta only, or sell Pinterest and TikTok as paid add-ons. This one runs server-side dispatch to all three plus a bundled GTM template for GA4 + Google Ads (Enhanced Conversions, Conversion Linker, click-ID recovery for iOS Safari post-ITP). The same <code>event_id</code> flows browser-side and server-side so each platform deduplicates instead of double-counting.
Aggressive bot filtering, no false-positives on real customers. Layered detection (behavioral signals + ~9,500-CIDR datacenter list + AI-crawler classification for GPTBot / PerplexityBot / ClaudeBot / Google-Extended / Bytespider / etc.) blocks Lighthouse audits, scrapers, and ad-fraud bots. Multi-layered customer bypass — Apple iCloud Private Relay whitelist, ad-click ID recognition (<code>fbclid</code> / <code>gclid</code> / <code>ttclid</code>), logged-in customers, prior-visit <code>_fbp</code> / <code>_ga</code> cookies, Cloudflare Bot Management validation — keeps real shoppers visible. Purchase events are never blocked; pre-Purchase events held by the filter are replayed on eventual checkout so Meta sees the complete funnel.
<ul>
<li>Server-side CAPI to Meta, Pinterest, TikTok — every checkout & cart event, classic + block-based checkout, HPOS compatible. Per-platform retry isolates transient failures.</li>
<li>GTM template for browser-side tags — GA4 + Meta Pixel + Pinterest Tag + TikTok Pixel + Google Ads (Enhanced Conversions enabled, Conversion Linker auto-attached).</li>
<li>Event Log with By-IP view — paginated audit log, customer-protection badges prevent excluding real buyers, one-click exclude for confirmed bots, per-provider breakdown.</li>
<li>GDPR / CCPA modes — honors CMP opt-out signals, strict server-side consent strips PII when consent is denied (browser↔CAPI dedup still works on <code>event_id</code>).</li>
<li>Cache-safe — works with LiteSpeed, WP Rocket, Varnish, Cloudflare full-page cache. Click IDs captured into 1st-party cookies client-side; landing pages stay cacheable.</li>
<li>WP Dashboard widget — queue health at a glance: backlog, oldest pending, last successful dispatch, datacenter exclusions today.</li>
</ul>
If it helps your store, please <a href="https://wordpress.org/support/plugin/easy-meta-capi/reviews/#new-post" rel="ugc">leave a review</a> — it genuinely helps other merchants find this plugin.
<h3>External Services</h3>
This plugin connects your website to external services to send event data.
<ul>
<li>Service Used: Meta Conversion API (graph.facebook.com)
<ul>
<li>Purpose: To send user interaction and e-commerce event data from your server to Meta’s servers for ad performance measurement, optimization, and audience building.</li>
<li>Data Sent: Event details (product ID, price) and user parameters (IP address, user agent, hashed email/name/phone, Facebook cookies) are sent when a user performs a key action.</li>
</ul>
</li>
<li>Service Used: TikTok Events API (business-api.tiktok.com)
<ul>
<li>Purpose: Same as Meta CAPI, providing server-side conversion tracking for TikTok Ads optimization and attribution.</li>
<li>Data Sent: Event details (product ID, price, currency) and user parameters (IP address, user agent, hashed email/phone/external_id, ttp / ttclid cookies) are sent upon user action. Optional under the merchant’s TikTok credentials — the plugin only sends to TikTok if the credentials are configured.</li>
</ul>
</li>
<li>Service Used: Pinterest Conversions API (api.pinterest.com)
<ul>
<li>Purpose: Same as the Meta CAPI, providing reliable tracking for ad performance and audience building on Pinterest.</li>
<li>Data Sent: Event details and hashed user parameters are sent upon user action.</li>
</ul>
</li>
<li>Service Used: Google Tag Manager (googletagmanager.com)
<ul>
<li>Purpose: To load a JavaScript container from Google’s servers that allows you to manage and deploy marketing and analytics tags.</li>
<li>Data Sent: The plugin provides your GTM Container ID to Google to fetch the correct script. GTM itself may collect data based on how you configure your tags.</li>
</ul>
</li>
<li>Service Used: Cloud-provider IP range list — <code>raw.githubusercontent.com/rezmoss/cloud-provider-ip-addresses</code>
<ul>
<li>Purpose: Used by the optional Datacenter IP filter to keep the bot blocklist current. Daily background fetch downloads CIDR ranges for AWS, Google Cloud, Azure, Cloudflare, DigitalOcean, Linode, Vultr, Oracle Cloud, and Fastly so events from those ranges can be filtered out before reaching Meta / Pinterest / TikTok.</li>
<li>Data Sent: None. The plugin only downloads public IP-range manifests; no visitor data is sent to GitHub.</li>
<li>License: Source repository is CC0-licensed.</li>
</ul>
</li>
<li>Service Used: Apple iCloud Private Relay egress IP list — same <code>raw.githubusercontent.com/rezmoss/cloud-provider-ip-addresses</code> source (folder <code>apple_private_relay/</code>)
<ul>
<li>Purpose: Used by the optional Datacenter IP filter to whitelist real Apple visitors who exit through Apple’s relay infrastructure. Daily background fetch downloads the merged CIDR list so iOS Safari users on Private Relay aren’t mistaken for datacenter bots.</li>
<li>Data Sent: None. The plugin only downloads the public manifest; no visitor data is sent.</li>
</ul>
</li>
</ul>
Shared hosting note. Some restrictive shared hosts block outbound HTTPS by default. If event delivery silently fails after install, ask your host to whitelist the following domains for outgoing connections: <code>graph.facebook.com</code>, <code>business-api.tiktok.com</code>, <code>api.pinterest.com</code>, and <code>raw.githubusercontent.com</code> (only needed if you keep “Auto-fetched” enabled on the Blocked Traffic tab — covers both the datacenter blocklist and the Apple Private Relay whitelist).
<h3>Advanced Configuration</h3>
Setup details for Consent Mode v2, the strict server-side consent mode (GDPR PII gating), CMP auto-block compatibility, and the WooCommerce Subscriptions integration. None of these are required for a basic CAPI setup — turn them on as your store needs them.
<h3>Consent Mode v2 Setup (GDPR / EU Compliance)</h3>
If you serve EU visitors, GA4 and Meta browser tags don’t fire when consent is denied — typically losing 20–50% of measured event volume. Google Consent Mode v2 recovers this: when consent is denied, GA4 / Meta tags switch to cookieless pings (anonymous beacons carrying event name, value, currency, timestamp but no client identifier). Google’s ML models the conversions from these pings and shows them mixed with observed ones in your reports. A single CMP integration repairs both GA4 and Meta attribution because the Meta Pixel template reads the same consent signals.
How to enable. Popular CMP plugins (Cookiebot, CookieYes, Complianz, Iubenda, Termly, OneTrust) all have a native Consent Mode v2 toggle in their settings — find and enable it. The CMP then calls <code>gtag('consent', 'default', {denied})</code> before GTM loads and <code>gtag('consent', 'update', {granted})</code> after the visitor accepts.
The bundled GTM template includes a paused “Consent Defaults (Pre-CMP)” tag. Enable it only if your CMP doesn’t set <code>gtag('consent', 'default', ...)</code> on its own (rare with modern CMPs).
<h3>Strict server-side consent mode (PII gating for CAPI)</h3>
Consent Mode v2 only controls browser tags. Server-side CAPI fires from PHP, never sees <code>gtag('consent', ...)</code> signals — so it transmits hashed PII regardless of cookie-banner choice. Fine outside the EU; a GDPR concern inside it.
The Privacy & Consent (Server-side) section has a Strict server-side consent toggle (default OFF). When enabled and the visitor has denied marketing consent in your CMP, identifying PII (<code>em</code>, <code>ph</code>, <code>fn</code>, <code>ln</code>, address, <code>fbp</code>, <code>fbc</code> …) is stripped from the CAPI payload. The event still ships with <code>event_id</code>, <code>value</code>, <code>currency</code>, <code>contents</code> — Cookiebot, CookieYes, and Complianz cookies are read automatically; other CMPs supply state via the <code>mcapi_marketing_consent_granted</code> filter.
Why this matters alongside Consent Mode v2. Denied-consent browser pixels switch to cookieless pings — modeled, not observed. With Strict server-side consent ON, your server-side CAPI ships alongside that ping carrying the same <code>event_id</code>. Meta dedupes by <code>event_id</code> and now has an observed server signal feeding the same conversion record the cookieless ping created — cleaner Event Match Quality than browser-only or naïve “send everything” CAPI, and GDPR-defensible because no identifying data leaves your server.
Default OFF preserves match quality for existing non-EU setups. Recommended ON once Consent Mode v2 is configured in your CMP.
<h3>CMP Auto-Blocking and the Plugin’s Inline Scripts</h3>
CMPs with “auto-blocking” (Cookiebot, CookieYes, others) scan every <code><script></code> tag on load and convert anything they suspect of tracking to <code>type="text/plain"</code> until consent. The plugin’s inline scripts only POST first-party events to your own REST endpoint — but a generic auto-blocker can’t tell. To avoid a silent break, every plugin-rendered inline script ships with opt-out attributes for Cookiebot (<code>data-cookieconsent="ignore"</code>), CookieYes (<code>data-cookieyes="cookieyes-necessary"</code>), and Complianz (<code>data-cmplz-no-cookielaw="1"</code>). For other CMPs (OneTrust, Quantcast, in-house), append your own attribute via the <code>mcapi_inline_script_attrs</code> filter.
<h3>WooCommerce Subscriptions Integration</h3>
By default, every WooCommerce Subscriptions auto-renewal sends a fresh <code>Purchase</code> to Meta CAPI — credited to the original acquisition ad. Reported ROAS keeps climbing month after month from the same conversion, polluting optimization signals.
The plugin auto-detects WooCommerce Subscriptions and exposes:
Subscription Renewal Behavior (radio):
<ul>
<li>Default — renewals send as regular <code>Purchase</code>. Existing setups unchanged.</li>
<li>Skip — renewals not sent. Cleanest ROAS hygiene; you forfeit Meta’s LTV signal from renewals.</li>
<li>Tag — renewals still send <code>Purchase</code> but with <code>custom_data.customer_status = "subscription_renewal"</code> so you can filter them in Events Manager.</li>
<li>Subscribe / SubscriptionRenewal events — Meta’s standard <code>Subscribe</code> for sign-ups + a <code>SubscriptionRenewal</code> custom event for renewals. <code>Purchase</code> stays clean, advertisers using LTV-bidding can opt into both.</li>
</ul>
Tag every Purchase with customer_status (checkbox): adds <code>custom_data.customer_status</code> (<code>new_customer</code> / <code>returning_customer</code> / <code>subscription_renewal</code>) to every <code>Purchase</code> so Meta Advantage+ can bid acquisition vs. retention differently. Guest checkouts fall back to billing-email lookup.
<h3>Disclaimer</h3>
This plugin is an independent, community-driven implementation of server-side Conversions API protocols. It is not affiliated with, endorsed by, or sponsored by Meta Platforms, Inc., TikTok Ltd., Pinterest, Inc., Google LLC, Automattic Inc., or any other trademark holder referenced herein.
“Meta”, “Facebook”, and the Meta Pixel are trademarks of Meta Platforms, Inc. “TikTok” is a trademark of TikTok Ltd. “Pinterest” is a trademark of Pinterest, Inc. “Google Tag Manager”, “Google Ads”, and “GA4” are trademarks of Google LLC. “WooCommerce” is a trademark of Automattic Inc. All trademark references are used solely for descriptive interoperability purposes — to indicate which platforms this plugin can transmit data to under the merchant’s own configured credentials.
No user data is transmitted to any external service until the merchant explicitly configures their own platform credentials in the plugin settings. The plugin does not “phone home” or contact any developer-controlled server. The only outbound HTTP calls are: (1) merchant-configured CAPI endpoints, (2) the public CIDR manifests at raw.githubusercontent.com used by the optional Datacenter IP filter — no visitor data is sent in those manifest fetches.

CAPI Suite: Meta, Pinterest, TikTok, GTM

Free multi-platform server-side CAPI for Meta, Pinterest, TikTok + GTM dataLayer. Cache-safe, theme-agnostic, no cloud server needed.

Track Combo — Conversions API for WooCommerce vs CAPI Suite: Meta, Pinterest, TikTok, GTM