Documentation
Pixels & destinations
Client pixels, server-side delivery, and conversion delivery proof.
Intently routes conversions via server-side destination deliveries (GA4, Meta CAPI, TikTok, Snapchat, LinkedIn, Pinterest, X, and Segment). Attribution links successful deliveries back to conversions as delivery proof. Client-side ad pixels are not part of the current product.
Where to configure
- Pixels — pixel / destination configuration and Delivery log (
/pixels#delivery-log) - Destinations — product overview of server-side routing
Enable server-side on a destination when you want Intently to POST conversion payloads (e.g. CAPI-style) using first-party click IDs collected by the SDK — not by loading third-party ad scripts for attribution.
Attribution signals for destinations
The attribution module (ADT.Attribution.getContext()) reads sticky click IDs and cookies such as _fbp / _fbc so server routes can forward them with events. See SDK reference.
Delivery proof
When a conversion is recorded and destinations dispatch, Intently can attach ConversionDeliveryProof rows (success/fail per pixel type). Consent-blocked destinations are skipped before send and do not appear as log rows — only dispatched attempts are logged.
The Attribution report shows:
- Verified delivery % on KPIs
- Per-channel delivery success rates
- Expandable proofs on recent deals / conversion detail
If destinations are configured but proofs are empty, check Pixels → Delivery log for failed sends, and confirm consent allowed the dispatch.
Relationship to marketing attribution
Attribution answers which channel deserves credit. Destinations answer whether the ad platform received the conversion. Both appear on /attribution so you can trust the revenue story and the feedback loop to ads.