WooCommerce · WordPress · Custom HTML
One pixel. Every ad platform. GDPR-ready.
Install the Woo plugin or paste a single bootstrap snippet. Track PageLoad and ecommerce events, gate tags on consent, and forward to Meta, Google, TikTok, and more—with browser tags and CAPI from the same event.
clinker("bootstrap", {
pixelId: "CL-…",
apiHost: "api.…",
appHost: "app.…",
cmpKey: "…"
});Cookie banner (EU)
Reject → no clinker.gif PageLoad
Accept → PageLoad + destination bridge
8
Ad destinations
Meta, Google, Bing, GA4, TikTok, Reddit, Pinterest, GTM
2
Install paths
Woo plugin or head snippet
GDPR
Consent-first
cmpKey → banner before tags
CAPI
Server + browser
Same events, mapped outbound
Encrypted in transit
TLS for pixel and API traffic
Consent-gated tags
Marketing scripts after Accept
EU geo banner
cc_country / CMP for GDPR visitors
Server-side CAPI
Pushbacks when OAuth is connected
One clinker('event') fans out to every connected platform
Woo autotrack or manual events hit clinker.gif first. After consent, the public destination-bridge config drives fbq, gtag, ttq, dataLayer, and more—with ecommerce contents[] preserved.
- ✓Marketing events wait on CLConsent.has(analytics|marketing)
- ✓GTM appears once in bridge—not per-platform duplicates
- ✓Purchase ed includes order_id and contents for ads
- ✓Reject non-essential: no PageLoad until user accepts
The old stack vs ConversionLinker
Stop patching pixels every time you add a channel or a new storefront.
Pixel soup
- ✕Separate pixels per ad network in theme header
- ✕Duplicate GTM containers and conflicting tags
- ✕No consent gate—tags fire before Accept
- ✕Browser and CAPI configured in different tools
- ✕Manual event payloads that do not match ads APIs
One linker
- ✓One ConversionLinker bootstrap or Woo plugin
- ✓Single GTM row in destination-bridge
- ✓cmpKey loads consent-sdk; reject blocks PageLoad
- ✓Browser tag + CAPI pushbacks from same catalog
- ✓Mapped ViewContent, Lead, Purchase with contents[]
Everything you need
From first PageLoad to Purchase contents on Meta and TikTok.
Pixel & bootstrap snippet
Generate install code from the dashboard—pixelId, apiHost, appHost, optional cmpKey. Custom sites call clinker("bootstrap") once in the head.
dashboard → Install snippet
WooCommerce autotrack
ViewContent, AddToCart, InitiateCheckout, and Purchase fire from the plugin with Woo-shaped payloads—no manual dataLayer wiring.
product / cart / order-received
GDPR consent SDK
EU visitors see the cookie banner. Reject keeps clinker.gif quiet; Accept All enables analytics and marketing categories before tags load.
Accept all · Reject non-essential
Campaign analytics
Pixels, campaigns, offers, and ecommerce reports in one app— tied to the same events you forward to ad platforms.
ROI · funnel · event details
How it works
Three steps from signup to forwarded Purchase events.
Create a pixel
Pick WooCommerce, WordPress, or custom HTML. Enable GDPR and connect your consent banner in the dashboard.
Install
Use the WordPress plugin or paste the bootstrap snippet. Verify PageLoad in the browser network tab.
Connect destinations
Add Meta, GA4, GTM, TikTok, and CAPI pushbacks. Events map automatically from the event catalog.
Woo plugin or custom head snippet
Stores get autotrack. Custom sites get runGeneric PageLoad plus manual clinker('event', …).
WooCommerce / WordPress
Plugin injects bootstrap with platform: woocommerce. Product, cart, and checkout events match what destination-bridge expects.
- ✓ ViewContent on product pages
- ✓ AddToCart from classic and blocks
- ✓ Purchase on order-received
Custom HTML / JavaScript
Paste generatePixelBootstrapCode output. Pass cmpKey when GDPR applies. Fire Lead and Purchase yourself with contents[] and order_id.
- ✓ Same clinker.js runtime as the plugin
- ✓ Consent SDK from appHost
- ✓ browser-scripts when GDPR is off
Works with the ad platforms you already use
Connect browser tags and server APIs from the Integrations panel—one GTM container, not eight.
Built for operators, not slide decks
Illustrative scenarios—replace with customer stories when ready.
“We stopped hand-copying Meta payloads at checkout. Purchase contents show up in Events Manager the way catalog ads expect.”
“One destination-bridge response tells me GTM is configured once. Consent reject actually blocks PageLoad in our EU tests.”
“Custom HTML with cmpKey was the missing piece—same clinker runtime as our Woo properties without autotrack magic.”
What makes ConversionLinker different
First-party CL events
clinker.gif is the source of truth before any ad network sees data.
Consent before tags
GDPR mode returns empty browser-scripts until the user accepts.
GTM once
destination-bridge dedupes google_tag_manager rows with GA4 eventMap.
CAPI + browser
Pushbacks and script tags share catalog mappings—fewer double counts.
Frequently asked questions
WooCommerce vs custom HTML?
The plugin sets platform woocommerce and autotracks ecommerce. Custom sites use the head snippet and manual clinker("event") calls.
Does reject block tracking?
Yes for GDPR visitors: no clinker.gif PageLoad until Accept All (or analytics/marketing consent).
When do browser-scripts load?
When gdpr_mode is off on the linked banner—the public API returns marketing script HTML to inject.
How is GTM handled?
One GTM destination with GA4-style eventMap; avoid stacking extra GTM chips per platform in UI.
Ready to unify your conversion tracking?
Install the Woo plugin or paste one head snippet. Connect destinations and stay GDPR-ready from day one.