Conversions: Batch Files

Batch Conversions Overview

Rockerbox supports receiving conversion data via batch files in the following cases:

  • If you have offline conversion data that can’t be captured via an onsite pixel.
  • If you have a complex funnel or site-flow which leads to challenges tracking onsite conversions using pixels.

Common examples of when Rockerbox will leverage batch files to capture conversion data include:

  • Retail orders
  • Call center events
  • Server-side events (i.e. recurring subscriptions)

Requirements

In order to send batch conversion data to Rockerbox, you must do the following:

  • Fire an Identify pixel onsite in order for Rockerbox to match users with online activity. You can implement this Identify pixel via Google Tag Manager as outlined in our documentation. If you are implementing this pixel outside of Google Tag Manager, here is our documentation.
  • Automate daily file delivery to a Rockerbox-hosted SFTP or S3 endpoint at 00:30 UTC or as early as possible. We recommend SFTP.
  • Meet our Report Format Requirements

Report Fields

The below are fields that must be provided to Rockerbox in a batch file.

Field Name

Format

Required

Notes

order_timestamp

string (UTC)

Yes

If the timezone of the timestamp is not in UTC, this is not a blocker. Please let your Implementation team at Rockerbox know what timezone the timestamp is in so that they can convert to UTC.

Example: 07/27/2024 17:14:22

order_id

string

Yes

Please ensure this is aligned with the order_id from your internal source of truth

revenue

decimal

Yes

Please do not include the $ sign and do not include commas (for example: revenue of $2,000.10 should be 2000.10 in the file)

Please include a maximum of two decimal points

email

string

Yes

This should match the format of email collected on the onsite pixel

customer_id

string

Yes

This should match the format of external_id collected on the onsite pixel

promo_code

string

No

products

array

No

customer_type

string

No

This field should have a value of new if the user has never made a purchase before and a value of returning if the have made a purchase in the past. Rockerbox will use this field for new vs returning classification

order_type

string

Required if you have different types of purchases (for ex: one-time purchases and subscription starts)

This should be populated with the different types of purchases that occur (for ex: one-time purchase vs subscription start vs subscription renewal or retail vs online)

street_address

string

Required if you are running direct mail

This is your street address without the apartment or unit number (for ex: 100, First Street)

city

string

Required if you are running direct mail

For ex: Los Angeles

state

string

Required if you are running direct mail

For ex: CA

zip_code

string

Required if you are running direct mail

5-digit zip code (for ex: 94133)

currency

string

Required if revenue is not always in USD

For ex: USD or GBP

Looking to break out specific conversion categories in your Rockerbox data? See here for required fields that need to be passed on your conversion data to support these breakouts.

Sample File

You will need to deliver a sample file with one full day of data to a Rockerbox-hosted endpoint so that Rockerbox's Implementation team can run through QA.

Once the sample file has been validated, Rockerbox will set up an SFTP or S3 endpoint based on your preference and share endpoint details so that regular transmission of batch files can begin.

How did we do?