NewsBreak Pixel: Quick Verification Checklist

Accelerate Verification with the Pixel Helper (Alpha)

Skip the manual steps by installing our Chrome Extension. While the Pixel Helper is currently in alpha testing, it is designed to provide instant feedback on your implementation.

Note: For comprehensive troubleshooting, please refer to the manual verification steps below.

Estimated Time: 2–3 minutes 

Tools Needed: Google Chrome (or any Chromium-based browser)

Use this checklist to ensure your NewsBreak Pixel is capturing data correctly and attributing conversions to your campaigns.

1. Verify Pixel Presence

The first step is to confirm that the NewsBreak Pixel code is active on your website.

1. Open your website in a new browser tab.
2. Right-click anywhere on the page and select Inspect.
3. Navigate to the Network tab in the developer tools panel.
4. Refresh the page to capture initial loading activity.
5. In the Filter box, type: pixelv2.

Expected Result: You should see at least one pixelv2 request (usually an init call) firing immediately as the page loads. 

2. Confirm Correct Event Firing

Once you know the pixel is present, you must ensure it triggers the specific actions (events) you want to track.

1. Keep the Network tab open and filtered for pixelv2.
2. Perform an action on your site (e.g., click "Add to Cart" or "Purchase").
3. Click on the new request that appears in the list.
4. Navigate to the Payload (or Headers/Query String) tab.
5. Look for the ev parameter. Confirm that the value matches your intended action (e.g., ev: view_content or ev: purchase).

3. Verify nb_cid Persistence (Attribution)

The nb_cid (NewsBreak Click ID) is essential for attributing conversions to your ads. If this ID is lost during the user journey, your data will be inaccurate.

How to Test:

Enter your url and click on Go Test during events creation flow

Or

Manually simulate an ad click by adding a dummy ID to your URL. Replace “[replacewithyourwebsite]” with your website and add “?nb_cid=test12345

• Example: https://www.[replacewithyourwebsite].com/?nb_cid=test12345

Check the following:

• Landing Page: Does the nb_cid appear in the URL when you first land on the site?
• Funnel Persistence: Navigate through your site (Add to Cart → Checkout → Success Page). Does the nb_cid remain in the URL or stay stored in the session?
• Domain Hops: If your checkout process moves from one domain to another (e.g., from yourlandingpage.com to checkout.shopify.com), ensure the nb_cid survives the transition.

Warning: If the nb_cid disappears at any point before the final conversion, the conversion might not be attributed to NewsBreak.

4. Check for Duplicate Fires

Duplicate pixels can lead to inflated data and inaccurate ROAS (Return on Ad Spend) reporting.

• The Issue: Look for multiple view_content or pixel_init calls firing for a single page load or a single button click.
• Common Cause: This often happens when a pixel is installed manually in the theme code and via a third-party app or plugin simultaneously on a website.
• The Fix: Audit your installation methods and remove one of the duplicate instances to ensure only one pixel fires per event.

Troubleshooting: Common Pixel Issues & Solutions

If your verification results don't match the "Expected Results" above, use this table to identify and fix the issue.