Rockerbox device mode

RudderStack lets you send your event data to Rockerbox via device mode using the native web SDK.

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

Identify

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.

A sample identify call is as shown:

rudderanalytics.identify("1hKOmRA4el9Z", {
    "email": "alex@example.com"
})

The following table lists the optional properties and their mappings between RudderStack and Rockerbox:

The userId is the ID for a logged-in user. It is a first-party identifier that persists across sessions. A unique user ID is essential in a conversion pixel for capturing the new or returning user’s data. You can include as many user identifiers but only the first-party identifier should be passed to Rockerbox as external_id.

Track

The track call lets you capture user events along with the properties associated with them.

RudderStack supports the track call in both the cloud and device modes for Rockerbox integration. Refer to the Hybrid mode for more information.

A sample track call is as shown:

rudderanalytics.track(
  "Product Added", {
    product_id: "00000",
    product_name: "Pink bolognas",
    product_url: "http://www.yourdomain.com/products/pink-bolognas",
  })

Page

The page call lets you record your website’s page views with any additional relevant information about the viewed page.

The page call sends a RB.track("view") event to Rockerbox by default, along with any additional properties.

A sample page call is as shown:

rudderanalytics.page(
  "Cart",
  "Cart Viewed", {
    title: "new blank page",
    url: "/pages/new"
  }
);

Questions? Contact us by email or on Slack