Webhook
Fidero POSTs each enriched event to your HTTP endpoint in real time, with attribution, identity and full context attached. Point it at an internal service, an automation platform or anything you build.
| Channel | Server |
| Consent category | dataSharing |
| Deduplication | No event ID rewriting – every payload carries the event's messageId, so your endpoint can dedupe on it. |
| Identifiers | The full identity set – user ID, anonymous ID, external ID and group ID – plus traits, campaign and page context, all passed through unmodified. |
What it delivers
- The enriched event. Each event is POSTed as JSON – its type, name and properties, plus identity, attribution and full device and page context
- Real-time delivery. Events are sent to your endpoint as they arrive, not batched
What you provide
| Item | Detail |
|---|---|
| Endpoint URL | The HTTPS URL Fidero POSTs each event to. |
| Shared secret | Optional – a secret used to sign requests so your endpoint can verify them. |
| Custom headers | Optional – any headers your endpoint requires, such as an authorisation token. |
That's everything. Mapping, formatting, hashing and deduplication are already built in – you switch the destination on by requesting it, and the flow is on the Destinations overview.
What's automatic
- Signature verification. With a shared secret set, the JSON body is signed with HMAC-SHA256 in an
x-signatureheader - Automatic retries. Delivery retries until your endpoint accepts the event, so a brief outage doesn't drop data
- Event filtering. An allowed-events list, or a per-event flag, controls exactly which events reach your endpoint
Enrichment, consent enforcement, delivery monitoring and managed adapter updates apply to every third-party destination – what every destination receives covers the standard treatment.