# Ripe Destination

## About this integration

Ripe is a product-led sales platform that helps you unlock your revenue pipeline with product data. By identifying and showing which prospects you should focus your efforts on, you can convert leads into meetings inside your product. This destination lets you send product data to Ripe. Sales teams can identify decision-makers and product champions by understanding what properties they have and what events they trigger. This destination works as an alternative to directly integrating Ripe’s SDK script in your app or site.

[Mode How we forward source data to the destination: through Customer.io's servers or directly from our JavaScript client.](/cdp/destinations/getting-started/#connection-mode)

[Web sources Indicates whether or not this integration supports our the JavaScript client.](/cdp/sources/getting-started/#types-of-sources)

[API sources Indicates whether or not this integration supports our server libraries (Go, NodeJS, Python), API, Mobile SDK, and other data sources.](/cdp/sources/getting-started/#types-of-sources)

[Supported calls The API methods this integration supports.](/cdp/sources/source-spec/source-events/)

[Integration name The name of this integration if you want to enable or disable it in the `integrations` object.](/cdp/sources/source-spec/common-fields/#the-integrations-object)

Standard

[group](/api/cdp/#operation/group), [identify](/api/cdp/#operation/identify), [page](/api/cdp/#operation/page), and [track](/api/cdp/#operation/track)

Ripe Cloud Mode (Actions)

Web

[group](/api/cdp/#operation/group), [identify](/api/cdp/#operation/identify), [page](/api/cdp/#operation/page), and [track](/api/cdp/#operation/track)

ripe-web

## There are two versions of this integration[](#there-are-two-versions-of-this-integration)

You’ll see two entries for Ripe in our [integration catalog](https://fly.customer.io/workspaces/last/journeys/integrations/all/directory), with one labeled *Web*. We typically recommend that you use the standard integration, the one *not* labeled “Web” when possible. The *web* version of this integration only works with our JavaScript client and does not pass data through Customer.io’s servers, which can make it hard to debug your integration, capture a history of events sent to the integration, and so on. Learn more about [Web integrations](/integrations/data-out/getting-started/#connection-modes).

## Getting started[](#getting-started)

1.  Go to **[Data & Integrations > Integrations](https://fly.customer.io/workspaces/last/journeys/integrations/all/directory)** and select the **Ripe** entry in the *Directory* tab.
    
2.  (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration.
    
3.  Configure your integration.
    
    1.  **Api Key**: The Ripe API key found in the Ripe App
        
    2.  **Endpoint**: The Ripe API endpoint (do not change this unless you know what you're doing)
        
4.  Click **Enable Destination**.
    

### Actions[](#actions)

When you’re done setting things up, you can go to the *Actions* tab to see how we map incoming data to your integration.

You may need to add actions for this integration

While we often have default triggers for actions, we don't always add those actions as defaults. You may need to add actions to make sure that you're sending all the data that you want to send to your integration. See our [actions](/integrations/data-out/actions/) page for help setting up actions.

Action

Default Trigger

Description

Group

`type = “group”`

Group user in Ripe

Identify

`type = “identify”`

Identify user in Ripe

Page

`type = “page”`

Register page view in Ripe

Track

`type = “track”`

Send user events to Ripe

## Getting started: web integration[](#getting-started-web-integration)

1.  Go to **[Data & Integrations > Integrations](https://fly.customer.io/workspaces/last/journeys/integrations/all/directory)** and select the **Ripe** entry in the *Directory* tab.
    
2.  (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration.
    
3.  Configure your integration.
    
    1.  **Sdk Version**: The version of the Ripe Widget SDK to use
        
    2.  **Api Key**: The Ripe API key found in the Ripe App
        
    3.  **Endpoint**: The Ripe API endpoint (do not change this unless you know what you're doing)
        
4.  Click **Enable Destination**.
    

### Web integration actions[](#web-integration-actions)

When you’re done setting things up, you can go to the *Actions* tab to see how we map incoming data to your integration.

You may need to add actions for this integration

While we often have default triggers for actions, we don't always add those actions as defaults. You may need to add actions to make sure that you're sending all the data that you want to send to your integration. See our [actions](/integrations/data-out/actions/) page for help setting up actions.

Action

Default Trigger

Description

Group

`type = “group”`

Group user in Ripe

Identify

`type = “identify”`

Identify user in Ripe

Page

`type = “page”`

Register page view in Ripe

Track

`type = “track”`

Send user events to Ripe