Conversions: Batch Files
Batch Conversions Overview
Rockerbox supports receiving conversion data via batch files for events that cannot be captured via pixel or webhook.
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 on-site in order for Rockerbox to match users with online activity
- Automate daily file delivery to a Batch Endpoint
- Meet our Report Format Requirements
Report Fields
The below are fields that must be provided to Rockerbox in a batch file.
timestamp | string (UTC) | Yes | |
order_id | string | Yes | |
revenue | decimal | Yes | USD, with cents up to 2 decimal places |
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. |
coupon | string | No | |
products | array | No |