Distribution Overview
After a user makes a consent decision, ConsentForge distributes that signal to your connected downstream systems automatically.
Distribution targets
| Target | Method | Use case |
|---|---|---|
| Google Tag Manager | dataLayer push + Consent Mode v2 | Tag activation/deactivation |
| Google Consent Mode | gtag('consent', 'update') | GA4, Google Ads modeled conversions |
| Webhooks | HTTP POST to your endpoint | Backend systems, CRM, custom integrations |
| ConsentForge API | Pull-based via REST API | Server-side verification |
How it works
Distribution happens synchronously after the user's decision is recorded:
- User clicks Accept / Reject / Save preferences
- Consent stored in browser (and server if enabled)
- Evidence receipt written
- Distribution targets notified in order:
- GTM/Consent Mode (synchronous, same page)
- Webhooks (async HTTP POST, retried on failure)
Webhook retries
If your webhook endpoint is unavailable, ConsentForge retries with exponential backoff:
- Attempt 1: immediate
- Attempt 2: 1 minute
- Attempt 3: 5 minutes
- Attempt 4: 30 minutes
- Attempt 5: 2 hours
After 5 failed attempts, the delivery is marked as failed. You can view failed deliveries in Dashboard → Webhooks → Delivery Log.