Ripe Web (Actions) Destination

Ripe is a product-led sales platform that empowers you to unlock revenue pipeline with product data. By identifying and showing which prospects to focus efforts on, you can convert leads into meetings inside your product.

This destination enables you to send product data to Ripe. Sales teams can identify decision-makers and product champions by understanding what properties they have and what events they have triggered. The Ripe destination is built as an alternative to directly adding Ripe’s SDK script to your app or site.

The Ripe Segment integration 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.

Analytics.js 2.0

Actions-based destinations may require features found in Analytics.js 2.0. If the destination has Web actions and is connected to a javascript source, upgrade your Analytics.js source to ensure compatibility.

Benefits of Ripe

Ripe provides the following benefits:

  • Be relevant. The Ripe destination understands key events in Segment to identify relevant leads, and shows its widget selectively to them.
  • Quick integration. Using the Ripe destination is the fastest way to start combining key product events with sales data and start targeting ripe leads.
  • More control. You can customize the conditions under which the events are sent to Ripe.

Getting started

Before you begin, create an API key in Ripe that you’ll use to configure the integration.

  1. From the Segment web app, navigate to Connections > Catalog, then click the Destinations tab at the top of the catalog.
  2. Search for Ripe Device Mode (Actions) in the left navigation, and click it.
  3. Click Configure Ripe Device Mode (Actions).
  4. Select an existing Source to connect to Ripe (Actions).
  5. Enter your Ripe API key in the API key field.

Destination Settings

Setting Description
API Key Required.

The Ripe API key found in the Ripe App

API Endpoint Required.

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

SDK Version Required.

The version of the Ripe Widget SDK to use

Available Presets

Ripe has the following presets:

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

Available Actions

Build your own Mappings! Combine supported triggers with the following Ripe-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

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

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

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

This page was last modified: 28 Mar 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