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.
- Sign in to your Segment Account
- Open the Ripe Destination
- Click Configure Ripe Device Mode (Actions).
- Select an existing Source to connect to Ripe.
- Enter your Ripe API key in the API key field and click save.
- 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"
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"
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"
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"
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"
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
Need support?
Questions? Problems? Need more info? Contact Segment Support for assistance!