Retail Data

Retail Overview

Tracking retail purchases in Rockerbox unlocks the ability to identify the unique marketing mix and path to conversion for your users that purchase in your retail locations vs. online.

In order to attribute marketing touchpoints back to users, Rockerbox requires a consistent user ID to be passed to Rockerbox across web and retail.

For example, if a user purchases from one of your retail locations - but you have no email address or customer ID associated with that user, there is no way for Rockerbox to attribute marketing touchpoints back to that user.

Having a loyalty program signup in your retail locations is a great way to encourage users to provide their email address during the checkout process.

The more consistent you are with capturing email address/user ID - the more retail conversions Rockerbox can attribute back to marketing.

Integration Types

There are two ways to send Rockerbox in-store purchase data:

JSON

The below are fields that must be provided to Rockerbox via a JSON integration. This can be sent to Rockerbox via either the Live or Batch methodology.

Field Name

Field Type

Required

Notes

timestamp

string (UTC)

Yes

order_id

string

Yes

revenue

decimal

Yes

USD, with cents up to 2 decimal places

email

string

Yes (or user_id)

Either email or user_id must be sent and it must match the web based user identifier that is being sent in your pixel.

user_id

string

Yes (or email)

Either email or user_id must be sent and it must match the web based user identifier that is being sent in your pixel.

store_id

int

No

products

array

No

This is required if you want to execute product level returns

id

string

No

name

string

No

sku

string

No

category

string

No

variant

string

No

price

float

No

quantity

int

No

{
    "email": "bob@example.com",
    "user_id": "0987654",
    "order_id": "1234567",
    "store_id": "NYC1234",
    "revenue": 310.99,
    "products": [
        {
            "id": "M083-FQFLA-ALEXAN-SKY",
            "sku": "ABCDEF123456",
            "name":" Shirt",
            "category": "Mens",
            "price": 275,
            "quantity": 1,
            "variant": "Blue Large"
        },
        {
            "id": "N209-ALWOK-MARCIA-FAL",
            "sku": "LSKEIP990812",
            "name":" Pants",
            "category": "Mens",
            "price": 325,
            "quantity": 1,
            "variant": "Red Large"
        }
    ]
}

Batch file requirements

Customer Order File: Provide one row per order, with the following columns:

  • order_id
  • customer_id
  • timestamp
  • email
  • revenue
  • store_id
  • products

If you have more than one product per order, then you can send a JSON list of products in that column.

How did we do?