How to integrate Unify with RudderStack

To integrate Unify with RudderStack, configure a Unify Play Webhook action to call the documented API with POST, the required credentials, and the destination-specific JSON body. Use this connection to send a defined sales handoff event into RudderStack.[1][2][3]

By UnifyDocumentation reviewed September 15, 2026

Explore scenarios Technical setup Open Unify

Connection: Via API; Product analytics
Tool: RudderStack; RudderStack
Data flow: Unify → RudderStack; JSON payload

At a glance

Via API: RudderStack receives the handoff
POST request with an explicit JSON contract and destination authentication
Test scenario: Limit destination fan-out

When this workflow makes sense

Start with the decision your team needs to make, then choose the connection that supports it.

A data pipeline can distribute a single defined event without teaching every destination about Unify. Start with an event contract that analytics and sales both understand. Keep destination routing intentional so a review event does not enter unrelated conversion audiences.

A good fit when

Teams that want to send a defined sales handoff event into RudderStack and have an owner for the receiving process. The destination account must permit the documented request and the chosen downstream action.

Reconsider the plan when

The receiving team has not agreed how this RudderStack operation should behave when the same record arrives again. Resolve the matching rule before enabling retries.

Design the handoff

Use this framework to agree on the input, the next action, and who owns the result.

Suggested workflow design, based on the documented capabilities below.

Stage	Decision to make
Business decision	Send a defined sales handoff event into RudderStack
Receiving contract	Agree which of the 3 example data fields the receiving process actually needs. Set missing-value and identity rules in the field mapping below.
Execution boundary	Give one owner access to inspect the RudderStack request and its resulting action.
Completion	Decide who can confirm the RudderStack outcome and recover a failed or repeated handoff. Use the completion check below as the acceptance criterion.

Explore the scenarios

Choose the situation that fits your team and work through the proposed plan.

Open a scenario to explore its plan. Checklists track your selections in this page only.

Send a defined sales handoff event into RudderStack

Start with one controlled record and one intended RudderStack outcome. Keep the test destination separate from live operations.

The decision that matters

The receiving owner must distinguish accepted input from completed work. Agree on the evidence required before treating this handoff as successful.

Prepare the destination using the RudderStack setup checklist
Resolve the sample fields for one known record and inspect the request before sending it
Trace that handoff through the receiving operation and compare the actual destination values with the source

Your validation checklistThe RudderStack destination and record identity are correctThe required fields match the controlled recordThe completion evidence is saved and the next action has an owner

0 of 3 checks marked by you

Limit destination fan-out

Limit destination fan-out: send a test event and inspect each configured delivery. Disable destinations that do not have an agreed use for prospect context.

The decision that matters

Decide whether this case should be held for review, corrected, or retried. Make that decision before running RudderStack against live records.

Isolate the test in a controlled destination and record the starting state
Run the edge case described above and capture the actual response and destination state
Recover the record once, then check that recovery did not create unintended additional work

Your validation checklistThe intended edge case has an observable resultRecovery does not create unintended additional workThe RudderStack owner has a documented recovery decision

0 of 3 checks marked by you

Illustrative workflow, not a preconfigured automation. Complete these checks in your own account.

Define success before launch

Inspect the data and the intended outcome separately. Connection status is only the first check.

Expected, not tested

Send a defined sales handoff event into RudderStack

Inspect the source event and delivery to the selected destination. Validate the receiving schema and identity there as a separate checkpoint.

Documentation-based reference. This workflow has not been tested end to end. Use a record or event you control before enabling live activity.

Questions answered

Common decisions when connecting Unify and RudderStack.

Which HTTP event types are supported?

The HTTP source supports the standard track, identify, page, screen, group, alias, and batch paths. This example uses track for an actual sales handoff event.[3]

Limits & decisions

Check these boundaries before designing a live workflow around the connection.

Ingestion into RudderStack does not establish successful delivery to every connected destination.[3]
API and trigger access depend on the destination account, permissions, and configuration. This request pattern is not a claim of native Unify sync.[3]

What the connection supports

Understand the connection, the data involved, and the behavior that matters for a Unify + RudderStack workflow.

Connection flowVia API

Unify

RudderStack

Prospect data

POST / JSON

Documented behavior at a glance
Decision	What to know
Unify action	Outbound HTTP request with configurable method, authentication, headers, and body[1]
Receiving operation	Create an HTTP source and copy its write key and data plane URL. Connect only the destinations that should receive this event.[3]
Response handling	Webhook response bodies are not available as inputs to later Unify Play actions[2]

Technical setup reference

References and requirements for the RudderStack connection.

Unify reference: Webhook action RudderStack reference: official connection reference

Connection requirements and setup checklist

Before connecting

A Unify Play with a Webhook action and a controlled record for testing
Access to the intended RudderStack environment and the permissions required by the cited API or trigger
The destination identifiers, credentials, and schema used by the request below
An agreed record identity, duplicate policy, and owner for failed handoffs

Prepare the RudderStack destination
Create an HTTP source and copy its write key and data plane URL. Connect only the destinations that should receive this event.[3]
Configure the destination action
Choose a documented event type such as track and provide a stable user identity. Map the commercial event separately from website or product usage events.[3]
Configure the Unify request
Use POST, the endpoint and authentication below, and JSON body format in the Webhook action. Replace setup placeholders, then inspect Expand preview with a controlled record. The receiver must respond within 8 seconds; webhook response bodies are not exposed to later Play steps.[1][2]
Validate the complete handoff
Run the success and edge-case scenarios in Explore the scenarios with a controlled record. Save the request identity and destination evidence, then apply the completion check before enabling live traffic.[3]

Request configuration

Method: POST
URL pattern: https://YOUR_DATA_PLANE_URL/v1/track
Headers: Content-Type: application/json
Authentication: Use HTTP Basic Auth with the HTTP source write key as username and an empty password. Copy the data plane URL and write key from the same source.

Choose JSON as the body format. Unify sets Content-Type automatically. The receiver must respond within Unify’s 8-second timeout; request responses are not passed to later Play steps.[2]

Replace URL placeholders with the actual receiver URL from your account or deployed application. These example URLs are not working endpoints.

Example handoff payload

Start with a fictional prospect. Validate the resolved values before using a real record.

Inspect the sample payload and field mapping

Example request body

{
  "userId": "example-person-001",
  "event": "Prospect handoff",
  "properties": {
    "company_domain": "example.com",
    "source": "Unify"
  },
  "messageId": "example-handoff-001"
}

Fictional data. Replace sample values before using a real Play.

Illustrative JSON for the documented receiving operation. All prospect values are fictional. Replace credentials, identifiers, schema-specific fields, and fixed example values before a controlled test. Use the field mapping to distinguish record data from fixed settings. Select available fields in your Play and inspect Expand preview; do not replace configuration values with prospect data.[1][2][3]

Payload field	Value to send
`userId`	string / dynamic / Agreed person identityMap the stable identity used by this destination to the same person or company in your source. This example identifier is not a documented Unify variable. If missing: Hold the handoff rather than creating an anonymous or incorrectly matched record.
`event`	string / static / Request configurationKeep the literal "Prospect handoff" required by this example request; change it only when deliberately changing the receiving contract. If missing: Keep this configured value in the request; do not replace it with a blank prospect field.
`properties.company_domain`	string / dynamic / Company domainSelect the available company domain field for the controlled person or company record in Unify. Keep the receiving field a string. If missing: Skip or hold the handoff if this value is required by the destination; omit it only when the destination contract permits omission. Do not send a guessed value.
`properties.source`	string / static / Request configurationKeep the literal "Unify" required by this example request; change it only when deliberately changing the receiving contract. If missing: Keep this configured value in the request; do not replace it with a blank prospect field.
`messageId`	string / dynamic / Handoff identity chosen by your implementationSupply a stable identifier for this logical handoff. Reuse it on a retry, and use a different identifier for a genuinely new event. Do not assume Unify automatically creates this sample field. If missing: Hold the handoff until the receiver or upstream workflow can establish its identity.

userId represents the person; messageId represents the event. properties holds the business context and must not redefine what the event actually means.

Troubleshooting

Start with the stage where the expected data or action stops appearing.

The request is rejected

Use HTTP Basic Auth with the HTTP source write key as username and an empty password. Copy the data plane URL and write key from the same source. Check the receiving account, permissions, endpoint, and required fields against the cited documentation.[3]

The values or destination are wrong

Compare the resolved JSON with the field-by-field contract in Example handoff payload. Check identifiers against the selected RudderStack environment, and distinguish an absent source value from an intentional static value. Fix the mapping before repeating the write.[3]

Receipt does not match the expected result

Find the request in the receiving logs, then inspect the actual RudderStack resource or execution. If the request was accepted but no result exists, investigate the destination failure before retrying. Keep the same logical handoff identity when recovering a repeat.[3]

Sources & review

Official documentation reviewed on September 15, 2026.

Technical claims link to primary documentation from Unify and the destination tool. Scenarios, field choices, and recovery plans are editorial implementation examples. Documentation review is separate from execution testing.

Documentation reviewed; end-to-end execution not tested. No named technical reviewer has signed off on these articles yet.

Content updated: 2026-09-16. Report a correction to Unify with the tool name, source URL, and behavior you observed.

How to integrate Unify with RudderStack