How to integrate Unify with Segment
To integrate Unify with Segment, create a Webhook (actions) destination for the website source. Forward selected Page, Track, and Identify events to Unify’s analytics endpoint using the Unify Write Key. Inspect ingestion before relying on an audience or Play that uses those events.[1]
- Connection
- Webhook destination
- Product analytics
- Tool
- Segment
- Unify
- Data flow
- Segment → Unify
- Account-specific configuration
At a glance
- Forward only supported event types that your workflow needs
- Use the Unify analytics endpoint and X-Write-Key header
- Use the documented JSON encoding and inspect actual ingestion
When this workflow makes sense
Start with the decision your team needs to make, then choose the connection that supports it.
An event stream is an input to a workflow. Choose the relevant Page, Track, or Identify events and explain why each is needed. Keep the collection path deliberate so overlapping tags do not confuse the activity you are using to prioritize accounts.
A good fit when
Teams already collecting website analytics in Segment that want supported events to inform outbound decisions in Unify.
Reconsider the plan when
If no one can explain how an event changes the next action, leave it out of the first workflow and focus on the signals the team can interpret.
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 |
|---|---|
| Event choice | Select supported events that supply context for a specific follow-up decision. |
| Collection | Check whether a Unify Tag overlaps with the same pages before enabling forwarding. |
| Ingestion | Inspect the event in Unify before relying on an audience or Play that uses it. |
| Action | Define who reviews the resulting account or prospect and what would change the proposed follow-up. |
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.
Forward a focused event set
The website already sends analytics through Segment and the team wants a useful subset in Unify.
Select the supported event types intentionally. Do not forward events simply because they are available.
- Choose the website source and relevant Page, Track, and Identify events
- Configure the destination endpoint and Write Key
- Test delivery and then inspect ingestion in Unify
Prevent duplicate website collection
Segment is active and another Unify Tag installation may collect the same page activity.
Resolve the collection overlap before interpreting counts or building triggers.
- Check the pages that run Segment
- Locate any Unify Tag on those same pages
- Validate the chosen collection path with a controlled visit
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
The destination reports that the test event was received, and the intended event is visible in Unify.
Check the destination response and actual event ingestion before evaluating an audience or Play. JSON encoding is supported by the cited Segment source; successful delivery to your Unify account still needs a live test.
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 Segment.
Does Segment send events into Unify or receive Unify webhooks?
This article covers Segment sending website analytics into Unify. It uses Segment Webhook (actions) as the sender and the Unify analytics endpoint as the receiver.[1]
Which Segment event types does Unify support?
The integration guide lists Page, Track, and Identify. Add an any condition for the event types you want to forward and omit the ones your workflow does not need.[1]
Which endpoint should Segment use?
Use https://analytics.unifygtm.com/api/v1/webhooks/segment, with the Unify Write Key sent in the X-Write-Key header.[1]
Can I keep the Unify Tag on the same pages as Segment?
The documentation warns that doing so can double-count events. Choose and validate the intended collection path before running both on the same pages.[1]
Which Content-Type should I use for the Segment webhook?
Use application/json for JSON event data. The Unify guide prints application-json, but Segment’s Webhook Send action uses its JSON request option, which sets application/json. This resolves the encoding discrepancy from primary sources; it is not a claim that this account connection has been tested.[4]
Limits & decisions
Check these boundaries before designing a live workflow around the connection.
- Validate JSON encoding and destination delivery with your own sample event before rollout
- A successful destination response is not proof of a completed downstream Play
What the connection supports
Understand the connection, the data involved, and the behavior that matters for a Unify + Segment workflow.
Webhook (actions) destination
| Decision | What to know |
|---|---|
| Supported event types | Page, Track, and Identify[1] |
| Destination | Webhook (actions), using a Send mapping[1] |
| Endpoint | https://analytics.unifygtm.com/api/v1/webhooks/segment[1] |
| Authentication header | X-Write-Key: YOUR_UNIFY_WRITE_KEY[1] |
| Content-Type | application/json for JSON events; the application-json spelling in the Unify guide is a documentation discrepancy[4] |
Keep the generated Segment sample event and mapping intact rather than replacing it with the fictional prospect payload used in the outbound webhook guides. Segment’s Send action JSON-encodes event data; validate the mapped event in the destination test before enabling delivery.
Technical setup reference
References and requirements for the Segment connection.
Connection requirements and setup checklist
Before connecting
- A Segment website source containing the events you intend to forward
- Permission to create a Webhook (actions) destination in Segment
- A Write Key generated in Settings → Integrations → Segment in Unify
Generate the Unify Write Key
In Unify, open Settings → Integrations → Segment, choose Setup, and copy the Write Key.[1]
Add the destination
In Segment, select Add destination and choose Webhook (actions). Select your website source, name the destination, and choose Fill in settings manually.[1]
Configure the event mapping
Open Mappings → New Mapping → Send. Add the supported Page, Track, and Identify event types using any, omitting events you do not want to forward. Generate a sample event.[1]
Set the URL and authentication
Use https://analytics.unifygtm.com/api/v1/webhooks/segment with POST. Send your key as X-Write-Key and use Content-Type: application/json for the JSON event. The Unify guide prints application-json; the JSON media type here follows Segment’s documented request encoding and Webhook Send implementation.[1][3][4]
Send and inspect a test event
Use the destination test, then inspect the event in Unify. The Segment success message establishes delivery to the destination, not completion of an audience or Play.[1]
Troubleshooting
Start with the stage where the expected data or action stops appearing.
The destination rejects the request
Check the endpoint and X-Write-Key value. For JSON events, use application/json rather than the application-json spelling printed in the Unify guide, then inspect the destination response and actual event ingestion.[1][3][4]
Only some events arrive
Review the any conditions and confirm that the source emits the selected Page, Track, or Identify events.[1]
Events are duplicated
The Unify guide warns against running the Unify Tag on the same pages as Segment. Review which collection path is active.[1]
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: . Report a correction to Unify with the tool name, source URL, and behavior you observed.
Keep exploring
