Discrepancies between internal data and Rockerbox data

When comparing your internal data to Rockerbox data, you may see slight discrepancies and don’t worry, that’s normal!

We expect to see a 5-10% discrepancy between the two data sets. There are a number of causes for this, which include:

  • Timezone differences: Rockerbox reporting is standardized to UTC time
    • Due to the timezone differences, day over day variances > 5-10% are expected. The variance will normalize over a longer time period (week, month).
    • If you spend more after UTC hours, this variance will be greater.
  • Returns or cancellations: Rockerbox does not account for returned or cancelled orders -- meaning they will appear in Rockerbox data
  • If Rockerbox tracks conversions via an on-site pixel (GTM)
    • Normal discrepancies caused by pixel based tracking, where the pixel may not fire 100% of the time
    • Differences in implementation: Rockerbox pixels firing through GTM versus other internal tracking
    • Page load times (if the Rockerbox pixel is based on that as a trigger)

How We Handle Reporting Discrepancies : We monitor conversion data closely, but small variances between your source of truth and Rockerbox are expected and normal. To keep our team focused on issues that actually impact your decision-making, we apply the following guidelines when determining whether a discrepancy warrants investigation.

For events you use to optimize campaigns and reporting:

-We will not investigate discrepancies under 5% for events tracked in batch (e.g., server-side or file-based data).

-We will not investigate discrepancies under 10% for events tracked via pixel (e.g., browser-based tracking).

-Example: An event like "View Product" typically isn't used for campaign optimization, so it would not fall under these thresholds.

How did we do?