Pixels Event Status: Pixel QA + Monitoring
The Pixel Event Status page can be used to monitor that the expected actions are being passed to Rockerbox, at the expected volume and with the expected variables.
This is especially critical when implementing Rockerbox pixels or troubleshooting any unexpected behavior of the on-site data passed to Rockerbox.
Navigating the Pixel Event Status Page
QA'ing your pixel events
1. Confirm that all expected actions that pixels were implemented against are shown. Same-day conversions are available, but on a slight delay due to the nature of the data aggregation.
- all Rockerbox customers should see "view" and "identify" actions firing
- all other conversion events will be custom for each customer. Reference the conversion events you aligned on with your CSM and implementation team to confirm each is firing
2. Confirm that the volume of pixel fires against your conversion events are aligned with your expectations
- Select a date range to compare conversions against. Dates and hours are reported in UTC timezone.
- See aggregate counts and unique pixel fires in the table, or use the chart to examine hourly pixel fire volume
- For more comparison analysis against your souce of truth, download the .csv of raw pixel fires. Due to size, this may take a few minutes to download.
3. Confirm that the required variables are being passed on each action by examining the % of non-null variables. For a guide on the standard expected % non-null variables passed per action, please see below. Note, the required variables per action may vary based on your specific implementation.
Action | Variable Requirements (based on standard implementation) |
view | N/A |
identify | Passed on >0% of pixels: - email and/or external_id |
purchase | Passed on 100% of pixels: - email and/or external_id - order_id - revenue - coupon - rb_country - rb_state - rb_city - rb_street_1 - rb_street_2 - rb_zip_code |