Segment
AvailableAPI key
Segment is a customer data platform rather than a destination, so the connection is about routing: events collected by Segment can feed En Garde segmentation, and En Garde audiences can be published back for Segment to fan out to your other destinations.
What moves, and which way
Integrations run in both directions. What follows is what this connection is for.
En Garde to Segment
- Audience membership published back to Segment for distribution to your other destinations.
Segment to En Garde
- Track and identify events flowing through your Segment source.
- User and account traits, used to match against En Garde audience data.
Connecting it
You generate a key in the platform and paste it into En Garde. The key is tested against the live API before it is stored, so a wrong or under-scoped key fails at setup rather than silently later.
- Generate an API key in the platform, with the permissions its documentation lists for third-party access.
- Open Integrations in your Brand Space and find the platform on the Integrations tab.
- Click Connect. Paste the key into the API key field — the eye toggle reveals what you pasted so you can check it.
- Click Test Connection. En Garde calls the platform with the key and reports whether it worked.
- Save. The Save button will not store an untested key, so a failing test has to be fixed first.
Worth knowing
- Connecting Segment does not replace the individual integrations in this catalog. It is useful when Segment is already the place your events are standardised, and adds a hop when it is not.
- Use a write key scoped to the source you want, not a workspace-wide key.