ReachOut + Segment

Use Segment as the CDP, ReachOut as the marketing layer.

Why this matters

Teams already invested in Segment as their CDP get the cleanest integration: identify / track / page calls flow into ReachOut as identified events, attribute to the right contact, and feed both segments and campaign triggers without rebuilding the data pipeline.

What you get

  • identify() updates ReachOut contact attributes; track() creates events for triggered campaigns.
  • Standard Segment field mapping — userId, email, traits all flow through.
  • Identity resolution: ReachOut respects anonymousId → userId merge events.
  • Replay-safe: idempotent on Segment messageId, so historical replays don't double-send.

Setup in 4 steps

  1. Create a ReachOut Webhook destination. Studio → Settings → Webhooks → Add. Source preset: Segment.
  2. Add the webhook in Segment. Segment → Connections → Add destination → Webhooks. Paste the ReachOut URL. Add the API key in headers.
  3. Choose which events to forward. Common pick: identify, track (selected events only), page (only on specific pages). Don't forward everything — focus on events that drive campaigns.
  4. Validate. Run a test event from Segment's debugger; confirm it appears in ReachOut's audit log within ~2 seconds.

Other integrations