Skip to main content

​
Overview

Destination Type: and The Segment destination sends your Converge events to Segment, using event names from the where one exists. From there, you can route them to any tool connected to Segment. Converge sends events in two ways:
  • Client-side: Converge loads Segment’s analytics.js on your site with your client write key, then sends browsing events like Product Viewed and Checkout Started from the browser.
  • Server-side: Converge sends orders and subscription events from your server-side sources to the Segment Track API with your server write key.
Both use the same Segment anonymousId (the ajs_anonymous_id cookie), so Segment links browser and server events from the same visitor.

​
Installation instructions

  1. In Segment, copy the write key of the source you want browser events in. We recommend a JavaScript source. This is your client write key.
  2. In Segment, copy the write key of the source you want server events in. We recommend an HTTP API source. This is your server write key.
  3. In the Converge sidebar, click on Destinations and then click Create new destination.
  4. Select the Segment destination and click Next.
  5. Give your destination a name (e.g. Segment) and click Next.
  6. Fill in the Client write key and Server write key and click Next.
  7. If your Segment workspace uses EU data residency, open Advanced configuration (optional) and set Segment region to EU. Otherwise, server-side events won’t arrive in your Segment source. Click Next.
  8. Select Use default mapping and click Next.
You can find the default mapping for the Segment destination here. For more information on setting up custom mappings, look here.
  1. Select the sources you want to forward events from, then click Next.
  2. Review any issues and click Submit.
Converge loads analytics.js for you. Remove any Segment snippet you added to your site yourself, or Segment receives events from both.

​
Configuration

Open your Segment destination, click Configuration, and open the Advanced configuration (optional) or Custom properties (optional) section.

​
Converge functionality

This integration supports the following Converge destination functionality.

​
Event mapping

Converge automatically maps the following events to Segment. Events without a link aren’t documented in the Converge event spec yet, but Converge forwards them when your sources send them.

​
FAQ

Check the Segment region setting first. If your Segment workspace uses EU data residency and the destination is set to US, Converge sends server-side events to Segment’s US endpoint, so your EU workspace never receives them. Also check that the Server write key belongs to the source you expect.
No. Converge sends events with Segment’s anonymousId only. Browser events use the ajs_anonymous_id cookie. Server events use the same ID when Converge has seen it for that visitor, otherwise an ID based on the Converge profile.