Retail Data

Suggest Edits

Retail Overview

Rockerbox Attribution Platform is able to ingest and attribute for in-store purchases via our Retail Attribution offering. The key component of Rockerbox's retail attribution is an ability to connect web-based activities to retail purchases. This requires a consistent user ID to be passed to Rockerbox across web and retail.

To facilitate this, you must be collecting a user identifier when a customer purchases in one of your stores for Rockerbox Attribution Platform to be able to attribute the conversion. If you aren't capturing a user ID in person, Rockerbox won't be able to connect the retail user with web-based marketing activities

When those users are authenticated on your website, then you will also need to fire an Identify Pixel.

🚧

Match Rates

Once you provide Rockerbox with a user_id for retail purchases, Rockerbox attempts to match that user with other marketing touchpoints that you may have served to that user. This can only be done if we have a user match -- that is, we've seen the same User ID digitally as you provided to us for the retail purchase. When we don't have a match we don't be able to attribute the conversion and will assign conversion credit to a "No Match" channel

Integration Types

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

There are two different file-formats that can be used 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 NameField TypeRequiredNotes
timestampstring (UTC)Yes
order_idstringYes
revenuedecimalYesUSD, with cents up to 2 decimal places
emailstringYes (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_idstringYes (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_idintNo
productsarrayNoThis is required if you want to execute product level returns
idstringNo
namestringNo
skustringNo
categorystringNo
variantstringNo
pricefloatNo
quantityintNo
{
    "email": "[email protected]",
    "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"
        }
    ]
}

Columnar Data

Retail purchase data can also be sent via CSVs. This data can't be sent live via our webhook and must instead be sent via a Batch Process.

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.

Updated over 3 years ago