No Result

RudderStack supports sending event data to Rockerbox 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, the Rockerbox native SDK is loaded from https://${host}/assets/${library}.js domain. Refer to the source code for obtaining the host and library values. Based on your website's content security policy, you might need to allowlist this domain to load the Rockerbox SDK successfully.

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

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

Connection settings

To successfully configure Rockerbox as a destination, configure the following settings:

  • Advertiser Id: Enter your Rockerbox Advertiser ID. It is a required field for sending events to Rockerbox via the cloud mode. To obtain it, contact your Rockerbox account manager.

  • Map your Rockerbox events to RudderStack Events: Use this setting to map your RudderStack events to specific Rockerbox events. You can map multiple RudderStack events to one Rockerbox event and vice versa.

  • Map your event property to Rockerbox custom property: Use this setting to map your RudderStack event properties to specific Rockerbox properties. RudderStack sends these fields to Rockerbox as custom properties. Note that to send these custom properties to Rockerbox, you must include them in the track call.

Client-side events filtering

This setting lets you specify which events should be blocked or allowed to flow through to Rockerbox and is applicable only if you're sending events via the web device mode.

Refer to the Client-side Event Filtering guide for more information on this feature.

Web SDK settings

These settings are applicable only if you are sending events to Rockerbox via web device mode:

  • Client Auth ID: Enter your Rockerbox Client Auth ID.
You can obtain the Client Auth ID from your Rockerbox All Pages tag available in the Rockerbox Attribution platform. For more information on obtaining it, refer to the Rockerbox documentation.
  • Custom Domain: Enter the custom domain from where you want to load the pixels.
Rockerbox lets you use a Custom Tracking Domain to load the Rockerbox trackers and pixels from your website's domain (for example, rb.mysite.com) instead of getrockerbox.com. For more details, refer to the Rockerbox documentation.
  • Enable Cookie Sync: Enable this setting if you are using a custom domain. It ensures that the Custom Tracking Domain functionality works as expected.
  • Use device-mode to send events: Enable this setting to send all the events from the JavaScript SDK to Rockerbox via the device mode.
  • Use device-mode to send track events: Enable this setting to send only track events from the JavaScript SDK to Rockerbox via the device mode. Refer to the Hybrid mode for more information.
  • OneTrust Cookie Categories: This setting lets you associate OneTrust cookie consent groups to the Rockerbox destination.

Hybrid mode

Hybrid mode lets you use a destination in the cloud as well as device mode simultaneously. It means that you can route some calls through server side (cloud mode), whereas others through the client side SDK (device mode). This is helpful in some specific use-cases and scenarios only possible in a particular connection mode.

In Rockerbox, the identify and page calls are supported in device mode whereas the track calls are supported in both the cloud and device mode.

Contact us

For more information on the topics covered on this page, email us or start a conversation in our Slack community.

On this page