Integrations
Delivery proof: knowing your conversions actually landed
Sent is not the same as accepted
Most stacks treat “we fired the webhook” as success. Destination APIs disagree: payloads get rejected for missing fields, consent mismatches, or rate limits, and the failure never appears in your channel report.
Incomplete delivery looks identical to incomplete capture. Without a log, you cannot tell whether Meta never saw the purchase or never accepted it.
What proof looks like
A delivery log should show each destination that was dispatched, whether it succeeded or failed, and enough payload context to debug enrichment — especially match quality on Conversions API sends.
Match quality is not vanity. It tells you whether the event carried the hashed identifiers and parameters platforms need to attribute spend back to real people.
- Per-destination success and failure on attributed conversions
- Match quality visibility on Meta CAPI enrichment
- Consent enforced before storage or routing, so blocked events stay blocked
Closing the loop
Capture on your domain and delivery to ad platforms are two halves of the same pipeline. Intently keeps both visible: the debug overlay on your site, and the delivery log in the dashboard.
When ROAS looks wrong, start by asking what was captured, what was credited, and what each destination accepted — in that order.