How does CustomerLabs send data through outgoing webhooks?

Configure the destination URL, payload format (JSON), authentication headers if needed, and event triggers. CustomerLabs fires a POST request to the URL in real time with identity-resolved data attached.

How does CustomerLabs receive data through incoming webhooks?

CustomerLabs generates a unique webhook URL for each incoming source. Send your data to that URL via POST request, and CustomerLabs receives the payload, runs identity resolution, and routes the data to your connected destinations.

What payload formats are supported?

JSON payloads with custom field mapping. Configure which fields map to email, phone, click IDs, event names, and user properties in CustomerLabs.

Does webhook delivery include identity resolution?

Yes. Outgoing webhooks send identity-resolved profiles with one stable user ID per real buyer. Incoming webhooks pass through identity resolution before reaching downstream destinations.

Can I trigger webhooks based on CustomerLabs segment changes?

Yes. When a user enters or exits a segment (high-LTV, MQL, cart abandoner), CustomerLabs fires an outgoing webhook to the URL you configured. Build real-time event-driven workflows without polling.

How does Webhooks compare to Zapier and Custom Destination?

Use Webhooks for direct connection to any URL with full control of payload format and authentication. Use Zapier for connecting to apps already in Zapier's catalog without code. Use Custom Destination for purpose-built destinations with template-based configuration in CustomerLabs. Most brands use Webhooks for internal systems and Zapier for SaaS app routing.

How long does it take to set up?

5 to 10 minutes per webhook. Configure URL, authentication, payload format, trigger conditions, and go live.

Webhooks Integration with CustomerLabs

Connect CustomerLabs to any system via webhooks, both ways — send identity-resolved events out or receive data from any tool that posts JSON.

Book a demo Start free trial

How brands use CustomerLabs Webhooks

Send Identity-Resolved Events to Any Custom API or Internal App

CustomerLabs sends events, audience updates, and CRM-enriched profiles as outgoing webhooks to any URL. Payloads arrive with full identity resolution applied, click context attached, and signal-engineered events ready to consume.
Reach internal dashboards, custom analytics systems, niche tools, and backend services without building per-integration code.

Receive Data From Custom Apps, Beta Tools, and Backend Systems

Configure incoming webhooks in CustomerLabs to receive data from any system that supports webhook output — custom apps, internal CRMs, backend order systems, niche SaaS.
Identity resolution stitches the incoming data into existing profiles, signal engineering shapes events for ad platforms, and downstream destinations get enriched signals automatically.

Build Real-Time Event-Driven Pipelines Without Code

When a CustomerLabs segment changes, an audience updates, or a CRM stage transitions, an outgoing webhook fires instantly to any URL.
Use webhooks to trigger Slack alerts, internal Slack bots, custom notification services, or backend workflows in real time. Event-driven architecture without managing infrastructure.

View the Webhooks Integration document with CustomerLabs

Handling brands across health & wellness, eCommerce, and ticketing businesses, cross-domain conversion tracking was always a major challenge. CustomerLabs became a lifesaver by helping us build a strong first-party data infrastructure. From accurately tracking conversions across domains to seamlessly activating data across ad platforms, everything became far more reliable, clean, and efficient.