Overview
Forward Segment events to Unify to use website visits and product activity in audiences and plays. Unify supports Segment Page, Track, and Identify events. Identify events can associate activity with a person using their email address. You need a working Segment source and permission to configure its destinations. Send each event through one source: forwarding the same pageview through Segment and the Unify Intent client can double-count it.Connect Segment
1
Get your Unify write key
Open Settings → Integrations → Segment.
Click Setup if you haven’t generated a write key, then copy the key.
2
Create a Webhooks destination
In Segment, open Connections → Destinations and click Add destination.
Search for Webhooks (Actions) and add it. Select the source whose events
you want to forward, then click Next.Name the destination, select Fill in settings manually, and click
Create destination.
3
Choose the events to send
Open Mappings, click New Mapping, and choose the Send action.
Under Define event trigger, add Event Type conditions for Page,
Track, and Identify, using any so each type can match.Omit an event type if you don’t want to forward it. You can add more filters
to narrow the activity sent to Unify.
4
Configure the webhook
Under Map fields, use these values:
Add two entries under Headers. Segment places the value on the left and
the header name on the right:
Keep batching disabled so each request contains one event.
5
Test the mapping
Generate or load a sample Page, Track, or Identify event. Under Send test
record, send the test event and check Segment’s delivery result.Review the event in the
Unify event console,
allowing a few minutes for processing. Finish saving the mapping and enable
the destination when its test data is correct.
Use incoming events
Page events supply website visits, Track events supply named custom activity, and Identify events associate visitors with known people. Include the person’s email in Identify traits so Unify can make that association. For example, combine a recent pricing-page visit with company size and CRM status in the filter builder. Save an audience to keep that group current, then use a play to follow up when new records qualify.Troubleshooting
Segment reports a failed delivery
Segment reports a failed delivery
Check the endpoint, POST method, write key, and
application/json header.
Confirm that Data contains the complete event and batching is disabled.Delivery succeeds but the event is missing
Delivery succeeds but the event is missing
Confirm the event type is Page, Track, or Identify and allow a few minutes
for processing. Then check the event console’s date range and source.
Visits appear more than once
Visits appear more than once
Check whether the same activity is being forwarded through multiple
destinations or collected by both Segment and the Unify Intent client.
Keep one path for each event.