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.

Khmer Lugod

Foreground Digital

The browser Meta Pixel is broken for ~30% of your visitors after iOS 17 and iOS 18 changed how Apple devices handle tracking. Most marketing managers running WordPress have no easy way to tell if their Pixel + CAPI setup actually works.
This plugin runs a 12-check audit against your site’s front page and gives you a score from 0 to 100, plus plain-English explanations of what each failure means and how to fix it.
Free forever. No signup, no upsell harassment, no phone-home. Every audit runs locally on your server.
Need it fixed for you? If your score is below 85 and you’d rather not learn server-side CAPI from scratch, we offer a flat-fee Pixel Fix service: $497, delivered in 4 business days. One link to that service appears inside the plugin admin only when your score is below 85. The audit works completely whether or not you use the paid option.
What it checks
<ul>
<li>Meta Pixel installed and parseable</li>
<li>Domain verification (iOS 14+ critical)</li>
<li>Pixel events firing (PageView, Purchase, Lead, etc.)</li>
<li>Advanced Matching (the single biggest EMQ lever)</li>
<li>CAPI deduplication via eventID</li>
<li>Consent Mode v2 / cookie banner presence</li>
<li>Google Tag Manager container</li>
<li>fbclid first-party capture (iOS 17 / iOS 18 Link Tracking Protection)</li>
<li>external_id in Advanced Matching (iOS 18 Hide My Email answer)</li>
<li>Server-side CAPI plugin presence</li>
<li>Apple Privacy Manifest readiness (if you link to an iOS app)</li>
<li>HTTPS enforced</li>
</ul>
What it does NOT do
<ul>
<li>No phone-home. Every audit runs on your server against your URL. Nothing is sent to Foreground.</li>
<li>No email capture. No signup wall.</li>
<li>No subscription, no paid tier, no upsell harassment.</li>
<li>No automatic re-runs or cron jobs.</li>
</ul>
Made by Foreground Digital
Foreground is a Dubai-based digital agency. We build Meta Ads campaigns and the server-side infrastructure that catches them — Pixel + CAPI, CRM integrations, WordPress + headless. Founded 2024.
<h3>External services</h3>
This plugin makes ONE outbound HTTP request, and it goes only to your own WordPress site. No data is ever sent to Foreground, Meta, or any other third party.
1. Your own site’s home URL (self-audit request)
<ul>
<li>What it is: A standard HTTP GET request to your site’s own front page (<code>home_url()</code>), used to fetch and parse the public HTML so the plugin can detect Pixel installs, fired events, Advanced Matching, eventID dedupe, etc.</li>
<li>What data is sent: Only the HTTP GET itself. The User-Agent header is set to <code>ForegroundCAPIHealth/1.0 (+https://foreground.agency)</code> to identify the audit traffic in your access logs. No personal data, no admin identifiers, no cookies, no user IDs.</li>
<li>When: Only when a WordPress administrator manually clicks “Run audit on this site” inside Tools → Meta CAPI Health. There is no cron, no front-end trigger, and no automatic re-run.</li>
<li>Where: The request loops back to your own server (the same WordPress installation that has the plugin installed). It does not go to any external service.</li>
<li>Fallback chain: If HTTPS fails due to a local certificate issue, the request is retried once with <code>sslverify=false</code>, and as a last resort over <code>http://</code> to the same hostname. This is purely a local recovery path; no external host is ever contacted.</li>
</ul>
2. References to third-party services in the plugin’s UI (documentation only — no external call)
The plugin’s “How to fix” instructions name several third-party services so administrators know where to go in their existing accounts. The plugin does not connect to any of these. They are mentioned for instructional purposes only:
<ul>
<li>Meta / Facebook — <code>connect.facebook.net</code>, <code>graph.facebook.com</code>, Meta Events Manager, Meta Business Manager. Used as documentation references when explaining how to install a Meta Pixel, set up domain verification, or wire Conversions API. The plugin does not call any Meta endpoint. Meta’s terms: https://www.facebook.com/legal/terms — Meta’s privacy policy: https://www.facebook.com/privacy/policy</li>
<li>Third-party WordPress plugins mentioned by name in the fix steps (PixelYourSite, Meta for WordPress, CAPI Suite, Cookiebot, CookieYes, Complianz, Termly, Iubenda, OneTrust, GTM for WordPress). These are recommendations only. The plugin does not call, depend on, or communicate with any of them.</li>
<li>Foreground.agency — appears in the audit traffic User-Agent string for self-identification, and as the destination of an optional “Get the Pixel Fix” link shown in the admin UI only when an administrator clicks it. The plugin itself does not phone home to foreground.agency. Foreground privacy policy: https://foreground.agency/privacy</li>
</ul>
The “Fix it for me” CTA shown when an administrator’s score is below 85 is a plain HTML link that opens <code>https://foreground.agency/pixel-fix/?ref=wp-plugin</code> in a new tab. Nothing is transmitted unless the administrator chooses to click it.

Foreground CAPI Health Check

Audit your site's Meta Pixel + Conversions API setup. 12 checks against the 2026 iOS 17/18 stack. Free, no signup, no phone-home.

Track Combo — Conversions API for WooCommerce vs Foreground CAPI Health Check