Click "Monitor the site data passed to Rockerbox via on-site pixel for implementation, troubleshooting, and anomaly detection"

Monitor the site data passed to Rockerbox via on-site pixel for implementation, troubleshooting, and anomaly detection

Select the date range you'd like to review. Keep in mind that:

1. All dates are in UTC

2\. "Today" may be delayed by a few hours due to the nature of the aggregations

3\. The max lookback is 14 days. To see aggregate conversion data over a longer time period, visit the Cross-Channel Report.

Use the chart to examine pixel volume over the selected range, rolled up by hour or by day. \
\
To examine a single action more closely, use the filter panel to select or search for the action.

Aug 07Aug 08Aug 09Aug 10Aug 11Aug 12Aug 13Aug 14

Use the table below the chart to drill into each action more granularly. \
\
The count will equal total pixel fires while uniques are de-duplicated per user per day.

Note, the raw pixel volume may differ from the conversion volume you see in other Rockerbox reports due to deduplication, filtering, exclusions, etc.

View all of the actions Rockerbox pixels have fired against within the selected time period.  \
\
The count will equal total pixel fires while uniques are de-duplicated per user per day. 

Note, the raw pixel volume may differ from the aggregate conversion volume you see in other Rockerbox reports due to deduplication, filtering, exclusions, etc. 

Click into each action to see the ecommerce variables passed on each pixel.\
\
The % indicates % of pixels where the variable is populated.  

For example, 98% means that the variable is populated on 98% of all pixels for the time period.

Click into each action to see the variables passed on the pixels.\
\
The % indicates % of pixels with non-null variables.  For example, 98% means that the variable is populated on 98% of all pixels for the time period. 

Click into an individual variable to understand any changes in how often the variable has been passed on the pixel.  \
\
From here, you will see a chart of the % of non-null variables over time. \
\
This is particularly helpful when diagnosing if a change made to your implementation has the desired effect.

To drill into the non-null variables on each action in more detail, click the variable. \
\
From here, you will see a chart of the % of non-null variables over time. \
\
This is particularly helpful when diagnosing if a change made to your implementation has the desired effect. 

12am1am2am3am4am5am6am7am8am9am10am11am12pm1pm2pm3pm4pm5pm

For more nuanced QA into specific user level events, you may download a log file as a .csv. \
\
This may be helpful for use cases like a discrepancy analysis, where you need to investigate where pixels may not be firing (based on missing order_ids, user agents, etc).\
\
Note, these files are very large and may take a few minutes to download. 

Pixel Event Status