Skip to app content
Skip to main content
Zero login · Deterministic client & SSRF-guarded tools
Pixel & CAPI Auditor · Criteo × Webflow

Criteo Pixel & CAPI Auditor for Webflow

Scan any public website for Criteo Commerce Conversion Pixel leaks, cid / utm_id preservation, and Consent Mode v2 gaps — then apply the copy-ready Webflow server-side CAPI blueprint.

Live Criteo & Webflow Pixel Scanner

Scans any public domain via SSRF-guarded /api/tools/pixel-audit (24h cached · 5 uncached scans/hr/IP). Checks Criteo Commerce Conversion Pixel, cid / utm_id persistence, and server-side CAPI signals.

Try an example:

Webflow Remediation Blueprint for Criteo

Target surface: Site Settings Custom Code + Edge Worker CAPI

Browser Tag & Click-ID Capture (cid / utm_id)

Place Consent Mode defaults before GTM/pixel scripts in Head Code and capture click IDs into hidden Webflow form inputs.

Server-Side CAPI Relay

Route Webflow Form Submission webhooks through a serverless endpoint to send deterministic CAPI Lead events. (Criteo server-to-server order and SKU conversion event API.)

// Webflow (Site Settings Custom Code + Edge Worker CAPI)
// 1. Persist cid / utm_id in a first-party cookie on landing
// 2. Fire Criteo Commerce Conversion Pixel with deterministic event_id
// 3. Mirror conversion via server-side CAPI (Criteo server-to-server order and SKU conversion event API.)
const eventId = crypto.randomUUID();
window.dataLayer = window.dataLayer || [];
window.dataLayer.push({
  event: "synter_conversion",
  ad_platform: "criteo",
  event_id: eventId,
  click_id_param: "cid / utm_id",
});
Synter Universal Ads Control Plane

Auto-fix Criteo tracking leaks on Webflow

Run free read-only diagnostics ($0.00 reads, 0% ad spend markup) or launch SOLO at $20/mo with $20.00 claimable credits.

Connect Criteo Free

Frequently Asked Questions

How do I fix Criteo pixel signal loss on Webflow?

Capture cid / utm_id in a first-party cookie on Site Settings Custom Code + Edge Worker CAPI and mirror browser events via server-side CAPI with a shared event_id for deduplication.

Does this Webflow pixel auditor require logging in or installing an SDK?

No. It runs a deterministic, SSRF-guarded inspection of public HTML, script tags, headers, and Consent Mode signals with zero login.

Why does Criteo lose conversions on Webflow sites?

Ad blockers, Safari ITP cookie expiration, and client-side hydration delays routinely drop 15–35% of client-only pixel beacons when no server-side CAPI relay is configured.

Can Synter automate Criteo CAPI on Webflow?

Yes. Connect Criteo and your site in Synter for free read-only diagnostics ($0.00 reads) or automated server-side event forwarding on SOLO ($20/mo).

Related Tools & Stacks

Free Criteo Pixel & CAPI Auditor for Webflow | Synter