Ripe Destination

The Ripe Destination is an Actions-based Destination in device mode that loads and configures Ripe’s SDK script for you. If you’re already using Segment’s Analytics.js for identifying and tracking your users, either directly or through Segment source integrations that you’ve installed, you can configure Segment to send this data directly to Ripe.

Getting started

Before you begin, create a free Ripe workspace to access the API key that you’ll use to configure the integration.

  1. Sign in to your Segment Account
  2. Open the Ripe Destination
  3. Click Configure Ripe Device Mode (Actions).
  4. Select an existing Source to connect to Ripe.
  5. Enter your Ripe API key in the API key field and click save.
  6. Enable the Destination

Destination Settings

Setting Description
API Key Required.

The Ripe API key found in the Ripe App

API Endpoint

The Ripe API endpoint (do not change this unless you know what you’re doing)

SDK Version

The version of the Ripe Widget SDK to use

Available Presets

Ripe Device Mode (Actions) has the following presets:

Preset Name Trigger Default Action
Page view Event type = "page"
Page
Group user Event type = "group"
Group
Track event Event type = "track"
Track
Identify user Event type = "identify"
Identify

Available Actions

Build your own Mappings. Combine supported triggers with the following Ripe Device Mode-supported actions:

Mapping limits per destination

Individual destination instances have support a maximum of 50 mappings.

Track

Send user events to Ripe

Track is a Web action. The default Trigger is: type = "track"

Click to show / hide fields

Field Description
Anonymous ID* Type: STRING

The anonymous id

User ID Type: STRING

The ID associated with the user

Group ID Type: STRING

The ID associated groupId

Event Name* Type: STRING

The event name

Event properties Type: OBJECT

Properties to send with the event

MessageId Type: STRING

The Segment messageId

Context Type: OBJECT

Device context

Page

Register page view in Ripe

Page is a Web action. The default Trigger is: type = "page"

Click to show / hide fields

Field Description
Anonymous ID* Type: STRING

The anonymous id

User ID Type: STRING

The ID associated with the user

Group ID Type: STRING

The ID associated groupId

Category Type: STRING

The category of the page

Name Type: STRING

The name of the page

Properties Type: OBJECT

Page properties

MessageId Type: STRING

The Segment messageId

Context Type: OBJECT

Device context

Identify

Identify user in Ripe

Identify is a Web action. The default Trigger is: type = "identify"

Click to show / hide fields

Field Description
Anonymous ID* Type: STRING

The anonymous id

User ID Type: STRING

The ID associated with the user

Group ID Type: STRING

The ID associated groupId

Traits Type: OBJECT

Traits to associate with the user

MessageId Type: STRING

The Segment messageId

Context Type: OBJECT

Device context

Alias

Alias a user to new user ID in Ripe

Alias is a Web action. The default Trigger is: type = "alias"

Click to show / hide fields

Field Description
Anonymous ID* Type: STRING

The new user ID, if user ID is not set

User ID Type: STRING

The ID associated with the user

Group ID Type: STRING

The ID associated groupId

Group

Group user in Ripe

Group is a Web action. The default Trigger is: type = "group"

Click to show / hide fields

Field Description
Anonymous ID* Type: STRING

The anonymous id

User ID Type: STRING

The ID associated with the user

Group ID* Type: STRING

The ID associated groupId

Traits Type: OBJECT

Traits to associate with the group

MessageId Type: STRING

The Segment messageId

Context Type: OBJECT

Device context

This page was last modified: 06 Dec 2023



Get started with Segment

Segment is the easiest way to integrate your websites & mobile apps data to over 300 analytics and growth tools.
or
Create free account