Ripe Device Mode (Actions) Destination

Ripe is a sales conversion tool that enables B2B revenue teams to surface and meet their best leads at the best possible time - when they are using your product.

The Ripe Segment integration is an Actions-based Destination in web mode that lets you send your product events data to Ripe.

Ripe maintains this destination. For any issues with the destination, contact the Ripe team.

Getting Started

1. From the Destinations catalog page in the Segment App, click Add Destination.
2. Search for “Ripe Device Mode (Actions)” in the Destinations Catalog, and select the “Ripe Device Mode (Actions)” destination.
3. Choose which Source should send data to the “Ripe Device Mode (Actions)” destination.
4. Go to Ripe integrations page (or onboarding) and click on the “Segment” integration.
5. Copy the “Segment API key”.
6. Enter the “Segment API Key” in the “Ripe” destination settings in Segment.

Supported Methods

Ripe supports all the following methods out of the box.

Identify

Take a look at the Identify method documentation to learn about what it does. An example call would look like this:

analytics.identify('userId123', {
  email: 'steve@apple.com',
  firstName: 'Steve',
  lastName: 'Jobs'
});

Segment sends Identify calls to Ripe as identify events. Ripe displays these events as Users by default. Identify event data is augmented with traits. It’s important to include email as a trait, as soon as it is known. Ripe will use email to populate User views by default. We fully support the Segment’s Identify Spec, and we recommend using the standardized names for the reserved traits covered there.

Track

Take a look at the Track method documentation to learn about what it does. An example call would look like:

analytics.track('Clicked Book a Demo Button')

Segment sends Track calls to Ripe as track events. Track events should be flattened whenever possible. For example, rather than Button Click as a track event with Book a Demo as a property, use Clicked Book a Demo Button. Product Events can be filtered and grouped by userId or groupId. Both of these will be appended automatically if they have been fired prior to the track call for web/client-side events.

Page

Take a look at the Page method documentation to learn about what it does. An example call would look like this:

analytics.page()

Segment sends Page calls to Ripe as a pageview event. Ripe displays these events as Page views by default.

Group

Take a look at the Group method documentation to learn about what it does. An example call would look like this:

analytics.group("0e8c78ea9d97a7b8185e8632", {
  name: "Apple Inc.",
  industry: "Technology",
  employees: 164000,
  plan: "enterprise",
  "total billed": 1000000,
  website: "apple.com"
});

Segment sends Group calls to Ripe as a group event. Group events can be augmented with group traits. Ripe displays these events as Workspaces by default. Including a name and a website (domain) as a trait is recommended, as Ripe will use the traits to populate Workspace views by default.

Destination Settings

Available Presets

Ripe Device Mode (Actions) has the following presets:

Available Actions

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

• Track

• Page

• Identify

• Alias

• Group

Track

Send user events to Ripe

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

Click to show / hide fields

Page

Register page view in Ripe

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

Click to show / hide fields

Identify

Identify user in Ripe

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

Click to show / hide fields

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

Group

Group user in Ripe

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

Click to show / hide fields