When there is an endpoint, there is a path forward.
Send customer events or audience-driven payloads to systems beyond native destinations with configurable methods, headers, authentication, batching and delivery timing.
Deliver the data the receiving system expects
A webhook can react to selected events, synchronize selected audiences or run on a configured schedule. Shape the request without waiting for a dedicated connector.
GET, POST, PUT, DELETE
Sync or asynchronous
Timeout, proxy, delay
Batch-size configuration
POST /customer-journey
Authorization: Basic [credential]
Content-Type: application/json
{
"profile": "{{profileId}}",
"audience": "high-intent",
"event": "product_viewed",
"occurredAt": "{{timestamp}}"
}Event-driven
Select the account events that should notify an order system, automation tool or internal service.
Audience-driven
Synchronize selected audiences so another system can act on the same customer eligibility.
Scheduled
Set execution timing and delay when the receiving workflow should not run immediately.
Native where it helps. Extensible everywhere else.
Choose the integration path that matches the destination.
| Path | Best for | Ownership |
|---|---|---|
| Native destination | Supported advertising and platform workflows | SegmentHub manages provider behavior |
| Webhook | HTTP-capable tools and internal services | You define endpoint and payload |
| REST API | Bidirectional application integration | Your application controls the workflow |
Connect the system already in your stack.
Use native destinations where available and configurable webhooks or APIs everywhere else.
Plan the connection