Send your event data from RudderStack to is a popular marketing platform for sending targeted emails and push and SMS notifications to improve customer engagement and overall conversion rate.

Find the open source transformer code for this destination in the GitHub repository.

Getting started

RudderStack supports sending event data to via the following connection modes:

Connection ModeWebMobileServer
Device modeSupported--
Cloud modeSupportedSupportedSupported
In a web device mode integration, that is, using JavaScript SDK as a source, RudderStack loads the native SDK from the domain. Based on your website’s content security policy, you might need to allowlist this domain to load the SDK successfully.

Once you have confirmed that the platform supports sending events to, follow these steps:

  1. From your RudderStack dashboard, add the source. From the list of destinations, select
  2. Assign a name to the destination and click Continue.

Connection settings

The connection settings required to configure as a destination in RudderStack are listed below:

  • Site ID: Enter your site ID.
  • API Key: Enter your API key.
For more information on obtaining your site ID and API key, see FAQ.
  • Event sent after setting device token: Enter the name of the event that is fired immediately after setting the device token.
  • Data center: Choose your data center from US or EU.
To send data to the EU data center using RudderStack Open Source, you should be using rudder-transformer v1.42.0 or later.
  • Client-side Events Filtering: This setting lets you specify which events should be blocked or allowed to flow through to For more information on this setting, see the Client-side Events Filtering guide.
  • OneTrust Cookie Categories: This setting lets you associate OneTrust cookie consent groups to For more information on this setting, see the OneTrust Consent Manager guide.
  • Ketch Consent Purposes: This setting lets you associate Ketch consent purposes to For more information on this setting, see the Ketch Consent Manager guide.

Web SDK settings

  • Use native SDK to send events: Turn on this setting to send the events through’s native JavaScript SDK.
  • Send page name in SDK mode: When sending events in web device mode using the native web SDK, RudderStack sends the page name to if this setting is toggled on. Otherwise, fetches the page name in the form of a URL.
  • Enable in-app message support: Turn on this setting to send in-app messages to your website using the native web SDK. For more information on setting up in-app messages for your website, see the documentation.


The identify call lets you identify a visiting user and associate them to their actions. It also lets you record the traits about them like their name, email address, etc.


userId is a mandatory field for

If it is not present, RudderStack:

RudderStack also sends the createdAt field as created_at to to register the user signup time. If it is not present in the event, RudderStack automatically assigns the event’s timestamp to created_at before sending it to

A sample identify call is shown below:

rudderanalytics.identify("userId", {
  name: "Tintin",
  city: "Brussels",
  country: "Belgium",
  email: ""
You cannot use the same email to make consecutive identify calls with different userId.

To update user information, you can use cio_id - the canonical identifier:

rudderanalytics.identify('<cio_id>', {
  email: '<updated_email>',
  id: '<updated_id>'

Unsubscribing users

You can pass unsubscribed: true in the identify call to unsubscribe a user in

rudderanalytics.identify("userId", {
  email: "",
  unsubscribed: true
Make sure the user ID and the email values match the attributes. You can verify this by selecting that user in the People page in your dashboard and clicking on Attributes.


The track call lets you record the user actions along with their associated properties and send them to

A sample track call is shown below:

rudderanalytics.track("Track me", {
  category: "category",
  label: "label",
  value: "value",

For anonymous users, does not permit an event name of size more than 100 Bytes. RudderStack automatically trims the event names in such a scenario.

For more information on the Track API event limits, see the documentation.


If you are using a native web SDK, RudderStack loads the JavaScript snippet and captures the page views automatically. You can also send the page event to record the page views along with the other page-related information.

A sample page call is as shown below:

// "home" is the name of the page."home", {
  path: "path",
  url: "url",
  title: "title",
  search: "search",
  referrer: "referrer",


The screen call is the mobile equivalent of the page call. It lets you record the screen views on your mobile app along with other relevant information about the screen.

If you have enabled screen views in your app implementation in the iOS or Android SDK, RudderStack registers the screen views as Viewed <screen_name> Screen under the user’s Activities tab.

RudderStack also forwards the event properties to as received.

A sample screen call using RudderStack’s iOS SDK is shown below:

[[RudderClient sharedInstance] screen:@"Main"
            properties:@{@"prop_key" : @"prop_value"}];

RudderStack transforms the above event as Viewed Main Screen before sending it to


The group call lets you link an identified user with a group, such as a company, organization, or an account. It also lets you record any custom traits or properties associated with that group and send this information to

A sample group call is shown below:"group@49", {
  email: "",
  action: "identify"

RudderStack automatically maps the following properties to the corresponding properties:

RudderStack propertyDefault value
Required - if not present, RudderStack sets it to identify by default.
Accepted values are identify, delete, delete_relationships, add_relationships


The alias call lets you merge different identities of a known user. It is an advanced method that lets you change the tracked user’s ID explicitly.

The alias call is applicable only when both the user identities are present in The mapping can be ID to ID, email to email, email to ID, and ID to email.

A sample alias call is as shown below:

rudderanalytics.alias("userId", "previousId");

You can merge two accounts using email as well. RudderStack sets the primary email as userId and secondary email as previousId.

A sample alias call merging two accounts is shown:

rudderanalytics.alias("<>", "<>");

Device token registration

RudderStack registers the device token to for the following Application Lifecycle Events:

  • Application Installed
  • Application Opened

To use this feature, enable the trackApplicationLifecycleEvents feature in your mobile SDK implementation code. Also, you need to register your device token after initializing the SDK.

The following snippets demonstrate registering the device token for iOS and Android:

You can also specify the event name to be fired after setting the device token using the Event sent after setting device token dashboard setting.

Make sure you fire the event just after setting the device token in your app, so RudderStack can immediately register the device token on that event and not delay until the next lifecycle event.

The following snippets demonstrate how you can send a device_token_registered event after setting the device token in your app:

RudderStack also supports removing the device (identified by device_id) whenever you send a custom Application Uninstalled event.


Where do I find the API key and site ID?

To obtain the API key and site ID, follow these steps:

  1. Sign in to your dashboard.
  2. In the left panel, click Settings and select Account Settings.
  3. Then, click API Credentials. You should find the site ID and API key for your project listed here. site ID and API key

Questions? Contact us by email or on Slack