Conversions: Batch Files
Batch Conversions Overview
While pixels and webhooks are more common, Rockerbox also supports ingesting batch files in order to report on conversions. This is commonly used in cases where the conversion events do not occur online and/or occur asynchronously, such as orders placed from a call center.
Match Rates
Once you provide Rockerbox with a user_id for these conversions, 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.
Requirements
In order to send batch conversion data to Rockerbox, you must do all of the following:
- Fire an Identify Pixel in order for Rockerbox to match users with online activity
- Delivery a regular file—typically daily—to a Batch Endpoint
- Meet our Report Format Requirements
- Include the required fields described in the next section
Report Fields
The below are fields that must be provided to Rockerbox in a batch file.
| 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 |
| 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 | |
| id | string | No | |
| name | string | No | |
| sku | string | No | |
| category | string | No | |
| variant | string | No | |
| price | float | No | |
| quantity | int | No |
Updated about 2 years ago