How does Custom Destination work?

Configure the destination URL, payload format (JSON), authentication headers, and the events or audience updates you want to send. CustomerLabs delivers data to the URL in real time with identity-resolved profiles, click context, and user attributes attached.

What kinds of systems can receive data through Custom Destination?

Any system that can receive a POST request with a JSON payload. This includes internal dashboards, custom analytics tools, proprietary ad networks, niche SaaS, beta tools, and apps without native CustomerLabs integrations.

Does Custom Destination send identity-resolved data?

Yes. Every payload includes one identity-resolved profile per buyer with email, phone, click IDs (GCLID, fbclid), and user attributes attached. Downstream systems receive complete profiles, not fragments.

Can I trigger Custom Destination on audience changes?

Yes. When a user enters or exits a CustomerLabs segment, Custom Destination fires the payload to the configured URL in real time. Build event-driven workflows across any system.

How does Custom Destination compare to Webhooks and Zapier?

Use Custom Destination for direct push to a system's API with field mapping handled in CustomerLabs. Use Webhooks when you need more granular control over payload format, authentication, and trigger conditions. Use Zapier when the destination app is in Zapier's catalog and you want a no-code connection. Most brands use Custom Destination for internal and niche systems, Zapier for SaaS apps, and Webhooks for full control.

How long does it take to set up?

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

Custom Destination Integration with CustomerLabs

Push identity-resolved events, audiences, and CRM data to any internal app, niche SaaS, or proprietary backend — no native integration required.

Book a demo Start free trial

How brands use CustomerLabs Custom Destinations

Send Identity-Resolved Events to Internal Apps and Proprietary Systems

Internal dashboards, custom analytics tools, proprietary backends, and in-house platforms need clean customer data. Custom Destination pushes identity-resolved events, audience updates, and CRM-enriched profiles from CustomerLabs to any endpoint your team controls.
Every payload includes one resolved profile per buyer with email, phone, click IDs (GCLID, fbclid), and user attributes — complete records, not fragments.

Activate Audiences in Niche SaaS and Beta Tools Without Native Integrations

When a destination tool doesn’t have a direct CustomerLabs integration, Custom Destination bridges it. Configure the outgoing payload, map CustomerLabs properties to the destination’s API fields, and audiences flow in real time as users move between segments.

Pipe Enriched Signals to Proprietary Ad Networks and Analytics Tools

Some ad networks, analytics platforms, and operational systems are too niche or too internal for native integrations. Custom Destination sends signal-engineered events with identity resolution and click context attached, so every system gets ad-platform-ready data.

View the Custom Destination 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.

Sam Follet Strategic Director, Utilise Social

Automotive Consulting Finance Clinics Insurance

Financial Consultants Universities Electricals Health and Wellness

Banking E-Commerce Real Estate Education Coach/Mentor

Explore Other Integrations

BigQuery

Analytics BI Tools

Axon

Advertising

Custom Source

Automation Ecommerce

BigCommerce

Ecommerce

CSV Upload

Automation

Bing Ads

Advertising Lead Gen

Customer.io

Email Marketing Automation

Meta (Facebook)

Advertising Analytics

See all integrations

What is a Custom Destination in CustomerLabs?

Custom Destination is a flexible outgoing connection that sends CustomerLabs data to any system, even when there's no native integration available. Use it for internal apps, niche SaaS, beta tools, and proprietary backends.

What is a Custom Destination in CustomerLabs?

Get started with1PD Signals

Schedule a Demo Start Free Trial

1PD Ops Platform

Signal Engineering

Industry solutions

Case studies

Schedule a 1-1 Demo

Custom Destination Integration with CustomerLabs

How brands use CustomerLabs Custom Destinations

Send Identity-Resolved Events to Internal Apps and Proprietary Systems

Activate Audiences in Niche SaaS and Beta Tools Without Native Integrations

Pipe Enriched Signals to Proprietary Ad Networks and Analytics Tools

Works across every industry