Documentation
Consent
How consent gates touchpoints, conversions, and destination dispatch.
Intently can respect consent before storing marketing attribution data or dispatching to destinations. Exact behavior depends on your consent configuration under Consent settings and related surfaces at Consent management.
What gets gated
When server-side consent blocks a request:
- Touchpoints may not be written
- Attributed conversions may not be recorded from
/api/v1/track - Destination delivery may be skipped
That means a paid click with no stored touchpoint cannot be credited later — even if Stripe metadata is perfect.
Practical checklist
- Confirm consent mode matches how you market (necessary vs marketing categories)
- After a consented visit with UTMs or
gclid, confirm a touchpoint appears (Attribution readiness / Events) - After a conversion, confirm the conversion row and any destination proofs
Privacy pages
Public privacy / terms pages describe legal commitments. Product enforcement is configured in Settings → Consent, not in marketing copy alone.