Verifying Conversion Pixels are Firing

When you’re first setting up Rockerbox, adding a new landing page, or making changes an existing webpage, it’s highly recommended you confirm the pixels are firing correctly on site.

This help doc will guide you through verifying the pixel is firing as expected when you take actions on your site.


You’ll need to know:

  • The website user flow and how to complete a conversion or conversions.
  • The action associated with the conversion. This usually looks like conv.[conversion event], such as conv.purchase or conv.add_to_cart. Review GTM: Conversion Pixels for additional info.
  • The fields you expect each Conversion event to include. For example, a conv.purchase will include order_id, revenue, external_id, and email, but a conv.add_to_cart may have no additional parameters.
  • If you are using a Custom Tracking Domain, then you will need to know your custom domain.

Onsite Verification

To verify the pixel is firing:

  1. Open up Chrome, and right-click to select the Inspect option, and switch to the Network tab.
  2. As a filter, use either or your Custom Domain, if you have one.
  3. Go to your website landing page.
  4. Verify you see network traffic under that domain.
  5. Look for the “rb?pageReferrer” row. If you click on that, you should find one that is an action=view. You may also find an action=identify if you have Identify Calls firing.
  6. Continue with your Checkout flow. For each step where you expect a Conversion event to be firing, then you want to make sure there’s a corresponding action=[conversion event] pixel firing.
  7. For any pixel where you expect additional parameters such as order_id, revenue, external_id, and email, verify they appear in the Querystring Parameters section.

If the pixel is firing with the correct query string parameters, then you’ve verified the pixel is firing correctly.

Other Potential Issues
Note this method only verifies the pixel fires for your specific use case. It will not cover all cases.

For example, if the pixel is not set up correctly to fire on a specific device, subdomain, or geography, then it’s possible it fires correctly during your testing but not for others.

How did we do?