Validate Pixel Installation

Overview

 

Validating your pixel helps confirm that the GroundTruth JavaScript is loading correctly and that tracking events are being triggered as expected. Follow these steps for both GroundTruth Pixels and Legacy Pixels.

While this article is written for Google Chrome (using Chrome DevTools), the process is similar in Firefox and Safari. Select the verification method or pixel type below to review step-by-step instructions.

GroundTruth Pixel
  1. Open an Incognito Window and navigate to your website page where the pixel has been placed.
  2. Right-click anywhere on the page and select Inspect to open Chrome DevTools.
  3. Click on the Network tab at the top of the developer tools panel.
  4. Refresh/reload the page.
  5. Use the filter bar (Filter Icon) and search for pixel.v2.js in the Network tab search field.
  6. Check Response Status: If pixel.v2.js appears in the Network tab with a 200 OK status, this confirms that the browser successfully requested and downloaded the GroundTruth JavaScript file.
    1. Important: A 200 OK response does not confirm that the pixel itself fired or that an event was successfully sent to GroundTruth. It only confirms that the JavaScript file required by the pixel was successfully downloaded and is available for the browser to execute.
  7. GroundTruth Pixel DevTools Verification

Verify That Your Pixel Is Firing

Confirming that the GroundTruth JavaScript file loaded successfully is only the first step. To verify that your pixel is actually firing and sending events to GroundTruth, use the Network tab in Chrome DevTools to look for the event request itself.

  1. Open an Incognito Window and navigate to the webpage where the pixel is installed.
  2. Right-click anywhere on the page and select Inspect.
  3. Select the Network tab.
  4. Refresh the page or perform the action that should trigger the event.
  5. In the Network Filter bar, enter event.
  6. Select the event request and confirm:
    • Request URL: https://vela.groundtruth.com/v2/event
    • Request Method: POST
    • Status Code: 204 No Content

A 204 No Content response confirms that the V2 event request was successfully sent to and accepted by GroundTruth.

Screenshot 2026-09-03 at 1.55.31 PM.png

 

Verifying Custom Event Placement

  1. Right-click anywhere on the confirmation page where the custom event is placed and select Inspect.
  2. Go to the Elements tab to view the live HTML source code.
  3. Press Ctrl + F (PC) or Cmd + F (Mac) to open the code search bar at the bottom of the panel.
  4. Type gtpx into the search box:
    • The first result will typically be the base pixel script.
    • Click the "Next" arrow in the search bar to find your specific custom event snippet.
  5. Ensure the custom event matches the required syntax and label string (e.g., gtpx("conversion",{label: "my_goal_name"})):

    Custom Event Inspection

Legacy Pixels (Conversion & Site Retargeting)
  1. Navigate to the webpage where the legacy pixel has been placed.
  2. Right-click anywhere on the page and select Inspect.
  3. In the developer tools panel, click on the Network tab.
  4. Refresh/reload the page.
  5. In the filter bar (Filter Icon), type xad in the Network tab search field.
  6. If xad populates as a result and returns a 200 OK or 304 Not Modified status code, this confirms that the browser successfully requested and downloaded the GroundTruth JavaScript file.

    Important: A 200 OK response does not confirm that the pixel itself fired or that an event was successfully sent to GroundTruth. It only confirms that the JavaScript file required by the pixel was successfully downloaded and is available for the browser to execute.

  7. Legacy Pixel DevTools Verification

Verify That Your Pixel Is Firing

  1. Open the webpage where the legacy pixel is installed.
  2. Open Chrome DevTools and select the Network tab.
  3. Refresh the page or perform the action that should trigger the event.
  4. In the Network Filter bar, enter events.
  5. Select the event request and confirm:
    • Request URL: https://engagement-flow-np.groundtruth.com/v1/events
    • Request Method: POST
    • Status Code: 200 OK

A 200 OK response from the /v1/events endpoint confirms that the Legacy Pixel event request was successfully sent to and accepted by GroundTruth.

Screenshot 2026-09-03 at 1.54.16 PM.png

Important: Do not confuse the status code returned when the browser downloads the GroundTruth JavaScript file with the status code returned by an event request. A 200 OK for pixel.v2.js or the legacy xad JavaScript only confirms that the browser successfully downloaded the JavaScript. To confirm that the pixel is firing, look for the event request described above.

Google Tag Manager Debugging
  1. Open GTM and click Preview in the top right corner to enter Tag Assistant debugging mode.
  2. Enter your website URL and click Connect.
  3. Perform the test pageview or conversion action in the opened browser window.
  4. Verify under the Tags Fired section in Tag Assistant that your GroundTruth Pixel tag triggered successfully.
  5. Publish Workspace: Ensure you click Submit / Publish in GTM to push your changes live to your production website.

Frequently Asked Questions

  1. What's the difference between seeing a 200 (OK) and a 304 (Not Modified) status code?
    These status codes tell you how the GroundTruth JavaScript file was loaded by the browser. They do not, by themselves, confirm that the pixel fired successfully.
    • 200 (OK): The browser requested the JavaScript file from the server and successfully downloaded it.
    • 304 (Not Modified): The browser checked the JavaScript file, determined that it had not changed, and can continue using the previously cached version.
  2. Why should I use the "Filter" function instead of the "Search" function in the Network tab?
    The Filter bar (Filter Icon) isolates network request file names, giving a clear "yes" or "no" answer on whether the request fired. The Search tool (Search Icon) searches inside page source files, which can cause false positives by finding the keyword text in static page content without confirming the script actually executed.

Troubleshooting Common Pixel Issues

Issue Root Cause Solution
Pixel status shows "Blocked" Security / Content Security Policy (CSP) rules blocking external script execution. Whitelist *.groundtruth.com in your site's Content Security Policy.
Pixel not firing in GTM Strict URL trigger matching failing due to landing page query strings. Switch GTM triggers from Exact Match to RegEx Matching to account for appended parameters (e.g., ?rid=...).
No events firing in console Active browser extension or ad-blocker blocking tracking requests. Disable browser ad-blockers or perform verification testing strictly in clean Incognito mode.
V1 DB out of sync GTID identifier string not linked in database tables. For V1 legacy accounts, confirm the GTID was added to the xadcms.pixels database table.

⚠️ Using Classic Ads Manager? Setup workflows and UI views in this guide reflect the updated platform experience. If you are using our legacy interface, please contact a GroundTruth representative for guidance.

 

Need Help?

For additional support and to ensure your campaign is set up for success, please reach out to your dedicated GroundTruth representative, or contact our Self-Serve team directly at selfservehelp@groundtruth.com.

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.