Step-by-step guide to send event data from RudderStack to Indicative.

Indicative is a popular customer analytics platform, designed especially for product managers, marketers, and data analysts. Indicative allows you to have an easy access to your data by connecting directly to your data warehouse. As a result, you can also avoid any errors that arise due to duplication of data during the collection stage, or any form of data mismatch.

RudderStack allows you to seamlessly configure Indicative as a destination to which you can send your event data seamlessly.

Find the open-source transformer code for this destination in our GitHub repo.

Getting Started

To enable sending data to Indicative, you will first need to add it as a destination to the source from which you are sending your event data. Once the destination is enabled, events from RudderStack will start flowing to Indicative.

Before configuring your source and destination on the RudderStack, please verify if the source platform is supported by Indicative, by referring to the table below:

Connection Mode




Device mode




Cloud mode




To know more about the difference between Cloud mode and Device mode in RudderStack, read the RudderStack connection modes guide.

Once you have confirmed that the platform supports sending events to Indicative, please perform the steps below:

  • Choose a source to which you would like to add Indicative as a destination.

Please follow our Adding a Source and Destination guide to know how to add a source in RudderStack.

  • Select the destination as Indicative to your source. Give your destination a name and then click on Next.

  • On the Connection Settings page, fill all the fields with the relevant information and click Next.

Indicative Connection Settings in RudderStack

Configurable settings

The following are the settings to be configured:

  • Indicative API Key: This API key can be found under Project Settings in your Indicative account.


When an identify call is made, RudderStack calls the Identify Users API of Indicative and sends the data accordingly.

A user is identified byuserId. If the field is not passed in the call, the event is not sent.

A sample identify call is as shown:

[[RSClient sharedInstance] identify:@"test_user_id"
traits:@{@"foo": @"bar",
@"foo1": @"bar1",
@"email": @"[email protected]",
@"key_1" : @"value_1",
@"key_2" : @"value_2"

We pass the user traits passed along with the identify call to Indicative as properties.


When the page method is called, the RudderStack server sends a track event to Indicative with the userId, and eventName parameters.

A sample page call is as shown in the snippet below:{
path: "path",
url: "url",
title: "title",
search: "search",
referrer: "referrer"


The screen call is the mobile equivalent of the page. When called, it sends a track event to Indicative with a userId and eventName .

A sample screen call is as shown:

[[RSClient sharedInstance] screen:@"Main"];


When the track call is made, RudderStack calls the Indicative Track Events API to send the events. The event properties are sent as data fields in the request, while the name of the event is sent as a custom event.

A sampletrack call is as shown in the snippet below:

[[RSClient sharedInstance] track:@"Accepted Terms of Service"
@"foo": @"bar",
@"foo_int": @134


Where can I get the Indicative API key?

You can get the Indicative API key under the Project Settings section in your Indicative account.

Contact Us

If you come across any issues while configuring or using Indicative with RudderStack, please feel free to contact us. You can also start a conversation on our Slack channel; we will be happy to talk to you!