Integrations
Connect delivery, qualification and outcomes
Set up buyer delivery, map real responses, enrich leads before routing and send conversion feedback to connected advertising and CRM systems.
How it works
- 1
Choose the connection
Start from an available native provider, a supported delivery template or a Custom HTTP setup. Native lifecycle sync, a one-way delivery template and an outbound event webhook are different integration types.
- 2
Map and test
Map outgoing fields and defaults, choose transformations and define how the receiving system signals success, rejection or a duplicate. Preview parsing with sample responses, then run a real test when the destination is ready.
- 3
Use the result
Captured IDs tie later postbacks to the sale. Enrichment can change buyer eligibility, and conversion events can feed advertising systems. Logs and connection health help operators track down failures.
Build an integration from real inputs and responses
Make the field mapping visible before sending live traffic.
Native connections and templates
Native Zoho lifecycle sync connects supported CRM outcomes. Google Sheets and supported buyer-system templates speed up delivery setup. Custom HTTP handles other endpoints. A template for an endpoint does not mean there is a native, two-way CRM connector; check the provider hub for current availability.
Visual field and response mapping
Select fields from a parsed response to create mappings and outcome rules. Use past or custom samples to preview the result. A searchable list of field transformations covers text, dates, numbers, state names, encoding and output types, along with per-buyer defaults.
Test the actual delivery path
Test Ping and Test Delivery run through the same paths as live traffic. An offline response preview evaluates a sample; a test send makes a real request to the destination. The delivery inspector shows captured requests, responses and timing, with Copy as cURL for troubleshooting.
Chain deliveries and track recipients
After the Primary succeeds, a Secondary can use the captured Buyer Lead ID. Turn on Track dispositions for this delivery on a later recipient to keep its case ID and outcomes; redelivery reuses the tracking record. That tracking record does not create a second priced sale or CPA conversion.
Use data before routing and outcomes after delivery
Connections can qualify supply, inform matching and close the loop on acquisition.
Enrichment and prescreens
Configured IPQualityScore, Blacklist Alliance and VeracityHub connections can add supported outputs or apply rejection rules. Each provider needs its own inputs, and some need specific consent language. Turn on enrichment for the offer explicitly; the added values can then take part in buyer filters. Custom HTTP prescreens support other configured checks.
Advertising conversion feedback
Supported Google Ads, Meta and AXON connections send configured outcomes back to your acquisition systems. Choose the named Meta connection when you use more than one pixel, and map identifiers, event timing and values to what the receiving platform requires.
Lead and call event webhooks
Choose lead or call events, the records they cover, and whether all or any of your conditions must match. Custom JSON payloads can carry supported tokens. Call events include incoming, dialed, connected, duration and billed events; duration anchors and rule-specific billed values keep downstream reports consistent.
Connection health and auditability
Inspect delivery attempts, mapped response messages and webhook logs. Raw delivery payloads are for admins; portal views are scoped and masked as required. Agent Connect events use their signed integration flow. Provider credentials and live acceptance still need a valid setup.
What your account needs
Each connection needs its supported credentials, required lead fields and permitted event scope. Some modules and enrichment providers must be turned on explicitly and carry usage or provider charges. A provider listed on the roadmap is not an available native integration. Native CRM lifecycle sync is currently Zoho; set up other supported destinations through their templates or HTTP interfaces.
Frequently asked questions
Can I connect an endpoint without a native connector?
Use a supported template or Custom HTTP setup when the endpoint accepts the available request and authentication formats. Map fields and response rules, then test with that provider before sending live traffic.
Does HTTP 200 always mean the lead was accepted?
No. Response rules check the configured body fields as well as the request result. A response that says rejected or duplicate must map to that outcome instead of counting as a successful delivery.
Can two recipients report separate outcomes for one lead?
Yes. Turn on disposition tracking on a secondary delivery to store its own case reference and outcomes. The tracking record has no sale price of its own and cannot create a CPA conversion; configured disposition costs attach to the real sale.
Is enrichment enabled on every offer?
No. Enrichment is turned on per offer, and each provider has its own required inputs, output fields and rejection behavior. Check those requirements before adding the returned fields to buyer filters.
Explore the platform
Set up your buyer network
Choose how buyers get leads and calls. Keep their setup and routing rules in one place.
Every feature is part of the plan. Usage is billed in credits.