1. Install & activate
- Download the zip from your purchase email or your account.
- WordPress › Plugins › Add New › Upload Plugin › choose the zip › Install › Activate.
- Go to WooCommerce › Tracking Hub. On the General tab, tick Enable UnifiedTrackingHub and save.
- On the License tab, paste your key and click Activate (for automatic updates).
Requirements: WordPress 6.3+, WooCommerce 8.0+, PHP 8.1+.
2. Connect Meta (Pixel + Conversions API)
- In Meta Events Manager, open your dataset (pixel) and copy its ID.
- In the dataset's Settings, under Conversions API, click Generate access token and copy it.
- In WordPress, open the Meta tab: tick Enable Meta module, paste the Pixel ID and the access token, keep Browser pixel and Conversions API on, and save.
3. Connect GA4 (optional)
- GA4 › Admin › Data streams › your web stream: copy the Measurement ID (G-…).
- In the same stream, open Measurement Protocol API secrets › Create, and copy the secret.
- In WordPress, open the GA4 tab: enable, paste both and save.
If GA4 is already loaded by Google Tag Manager, either leave the GA4 module off or turn off Browser tag and keep only Measurement Protocol for purchases. Don't send the same purchase from two tools.
4. Consent
- Consent mode Off: everything is tracked. Use this when you don't need a cookie banner. You are responsible for meeting the privacy laws that apply to your visitors.
- Consent mode On: Meta waits for marketing consent and GA4 for statistics consent. Supported: WP Consent API, Complianz, CookieYes, Cookiebot, or custom (PHP filter
uth_has_consent, JSwindow.uthConsent({marketing:true, statistics:true})). - Without consent, the server Purchase is skipped (default), or sent with hashed order details only if you choose that option.
5. Test before going live
- In Events Manager › Test events, copy the test code (e.g. TEST12345).
- Paste it into Meta › Test event code, and on General tick Debug / test mode.
- Click Send test event on the Meta tab. A server PageView should appear in Test events.
- Place a real low-value order (or use your gateway's test mode). Within a minute, Purchase appears in Test events, and in GA4 DebugView if GA4 is on.
- Turn Debug mode off. While it's on, server events go to Test events only and don't count as conversions.
Tip: set Live event panel to "admins only" to see each event fire on your own shop pages.
6. Verify orders
Every order gets a note per platform, for example:
Tracking Hub · Meta: Purchase sent (USD 25.00, event_id uth_purchase_1234)
The Tracking Hub box on the order screen shows the status and a Resend button. WooCommerce › Tracking Hub › Logs lists the last 100 sends. Failed sends retry automatically after 1, 5 and 15 minutes.
Custom thank-you pages & redirects
If buyers are sent to a course page, funnel or members area after paying, the browser Purchase on the thank-you page may never fire. That's fine: the server Purchase is sent when WooCommerce marks the order as paid (payment_complete, processing or completed), whatever page the buyer sees next.
Using Google Tag Manager
If your Meta pixel is already in GTM, turn off Meta › Browser pixel and keep Conversions API on. Purchases are then sent server-side only, so nothing is counted twice. UnifiedTrackingHub still saves first-party fbp/fbc IDs for good match quality.
Troubleshooting
- No order note at all: check the master switch, that the order is paid (processing/completed), and that WP-Cron / Action Scheduler runs (WooCommerce › Status › Scheduled Actions, group "unified-tracking-hub").
- "Invalid OAuth access token": generate a new Conversions API token and paste it again.
- Events in Test events but not in reports: Debug mode is still on.
- Duplicates: another plugin, theme or GTM tag also sends Purchase. Turn one of them off.
- Skipped – no consent: consent mode is on and the buyer didn't accept marketing cookies.
Developer hooks
uth_modules: add your own platform module (implementsUTH\Modules\Module).uth_has_consent($consent, $category): decide consent yourself.uth_meta_purchase_event,uth_ga4_purchase_params: change payloads.uth_item_brand,uth_browser_config.- REST:
GET /wp-json/unified-tracking-hub/v1/health(shop managers).
Privacy & uninstall
Stored per order: fbp/fbc, GA client and session ID, IP, user agent, UTM values, consent state. Customer contact data is hashed (SHA-256) before it is sent. WordPress' personal-data export and erase tools include this data. Deleting the plugin removes its settings, logs and scheduled tasks. Tick "Also delete tracking data stored on orders" to remove order data too.