Destinations
Capture on your domain. Enforce consent on the server. Route enriched events to Meta CAPI, GA4, TikTok, Segment, and more — then confirm delivery in your dashboard.
Capture vs delivery
Most attribution tools report on incomplete client-side pixels or server-side pipes you cannot audit. Intently gives you both — complete first-party capture via an SDK on your site and a delivery log that proves conversions reached each ad platform. Use the delivery log and Attribution dashboard to confirm each destination accepted the event and which channel earned the revenue.
Supported destinations
Analytics
Requires analytics consent
Advertising
Requires marketing consent
Advertising
Requires marketing consent
Advertising
Requires marketing consent
Advertising
Requires marketing consent
Advertising
Requires marketing consent
Advertising
Requires marketing consent
CDP
Requires analytics consent
fbp, fbc, gclid, ttclid, and other click IDs are collected by the SDK and forwarded server-side.
Analytics destinations need analytics consent. Ad platforms need marketing consent. Evaluated independently.
Each dispatched destination logs success or failure after the server-side send — open Pixels → Delivery log to audit.
We'll walk through the delivery log, consent gating, and how events map to Meta CAPI and GA4 on your stack.
“No single stack gives ad buyers complete first-party capture, nine inspectable attribution models, CRM + spend ROAS, delivery proof with match quality, and AI that cites the math — in one pipeline you can audit end to end.”