Skip to main content
With the Segment integration, InstantCampaign becomes a destination in your Segment workspace:
  • identify calls create or update contacts.
  • track and page calls are recorded as events and can start journeys.
Segment needs the Pro or Enterprise plan. Only Owners and Admins can connect, pause, regenerate or disconnect it.

​
Connect

1

Create a write key

Go to Settings → Developers → Integrations. Under Segment CDP, click Connect Segment.
2

Copy the write key now

The write key is shown once, with the warning “Save your write key now — it will not be shown again.” Copy it somewhere safe. Afterwards the card shows only its Write key prefix.
3

Copy the ingest URL

Copy the Ingest URL shown on the card. This is where Segment sends events.
4

Add the destination in Segment

Click How to configure in Segment dashboard for these steps:
  1. In your Segment workspace, go to Connections → Destinations.
  2. Click Add Destination and search for Webhooks (Actions) or HTTP API.
  3. Set the Endpoint URL to the ingest URL.
  4. Add a header named X-Write-Key with your write key as its value.
  5. Enable the destination and map your identify, track and page calls.

​
What each call does

For track and page, the contact is found by traits.email, then properties.email, then userId if it’s an email address. The event is recorded even when no contact matches, but a journey can only start for a known contact. New contacts created by identify have the Active status and the source segment.
Only send identify calls for people who have agreed to receive your email. Contacts created from Segment are Active and can be mailed straight away.

​
Start journeys from Segment events

Create a journey with the Website Event trigger and enter the Segment event name exactly, for example Order Completed. For page calls, use page. When a matching track or page call arrives for a known contact whose status is Active, the contact enters the journey, and the event’s properties are available to later steps. See Automation triggers.

​
Manage the connection

  • Pause stops accepting events and shows the card as Paused. Resume turns it back on.
  • Regenerate Key creates a new write key and shows it once. The old key stops working, so update the header in Segment straight away.
  • Disconnect invalidates the write key and stops receiving events. Existing contacts and events aren’t affected.

​
Limits

Each write key can send up to 200 requests per minute. Requests over the limit are refused with HTTP 429.

​
Troubleshooting