Insider Destination

Insider Growth Management Platform (GMP) helps digital marketers drive growth across the funnel. Insider GMP helps marketers deliver personalized journeys across the web, mobile web, mobile apps, messaging, email, and ad channels using the unified data.

This destination is maintained by Insider. For any issues with the destination, contact the Insider Support team.

Getting Started

1. From the Destinations catalog page in the Segment App, click Add Destination.
2. Search for “Insider” in the Destinations Catalog, and select the Insider destination.
3. Choose which Source should send data to the Insider destination.
4. Go to the Insider dashboard, navigate to Settings > Integration Settings, then find and copy the Segment.com API Key.
5. Enter your Partner Name and API Key in the Insider destination settings in Segment.

Page

If you aren’t familiar with the Segment Spec, take a look at the Page method documentation to learn about what it does. An example call would look like:

analytics.page("Home", {
    url: "https://useinsider.com",
    referrer: "http://google.com"
});

Segment sends Page calls to Insider as a page view event with the following event parameters.

"page_name": "Home",
"url": "https://useinsider.com",
"referrer": "http://google.com"

Identify

If you aren’t familiar with the Segment Spec, take a look at the Identify method documentation to learn about what it does. An example call would look like:

analytics.identify("userId123", {
  email: "john.doe@example.com",
  name: "John Doe",
  address: {
      city: "San Francisco",
      country: "USA"
    }
});

Segment sends Identify calls to Insider as a user insert or update request for the userId123 with the following attributes:

"uuid": "userId123",
"email": "john.doe@example.com",
"name": "John Doe",
"city": "San Francisco",
"country": "USA"

Insider uses userId, anonymousId, email and phone number as identifiers.

Track

If you aren’t familiar with the Segment Spec, take a look at the Track method documentation to learn about what it does. An example call would look like:

analytics.track('Product Viewed', {
  product_id: '507f1f77bcf86cd799439011',
  name: 'Monopoly: 3rd Edition',
  price: 18.99,
  url: 'https://www.example.com/product/path',
  image_url: 'https://www.example.com/product/path.jpg'
});

Segment sends Track calls to Insider as a custom event. Only the following Page views are mapped automatically to Insider’s default events:

• Product List Viewed
• Product Viewed
• Cart Viewed
• Order Completed.

"product_id": "507f1f77bcf86cd799439011"
"name": "Monopoly: 3rd Edition",
"price": 18.99,
"url": "https://www.example.com/product/path",
"product_imgage_url": "https://www.example.com/product/path.jpg"

Some Segment Track methods map to Insider’s predefined events. These are detected using the event name in the Track event. The table below lists these event names and their Insider mappings.

Engage

You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.

For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Engage sets that value to false.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.