Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.upstackdata.com/llms.txt

Use this file to discover all available pages before exploring further.

​
How to Use Upstack Data Pixel Helper

Once you’ve installed Upstack Data Pixel Helper, you can use it to monitor and validate all pixel events firing on your website in real time. This guide explains how to navigate the extension and interpret the data it displays.

​
Prerequisites

  • Upstack Data Pixel Helper installed in Chrome (see How to Install Upstack Data Pixel Helper)
  • The Upstack Data pixel installed on the website you want to test
  • Pixel Helper pinned to the Chrome toolbar for easy access

​
Open Pixel Helper

To open Upstack Data Pixel Helper:
  1. Navigate to any page on your website.
  2. Click the Upstack Data Pixel Helper icon in your Chrome toolbar (the pinned extension icon, in the top-right of the browser).
  3. A panel opens showing real-time pixel event monitoring.
The extension automatically displays any pixel events currently firing on the page.

​
Understanding the Interface

When you open Pixel Helper, you’ll see a list of events. Each event in the list displays:
  • Event Name — The name of the pixel event (e.g., “PageView,” “AddToCart,” “Purchase”)
  • Timestamp — When the event fired
  • Event Count — A counter showing how many times each event has fired
The panel updates in real-time as new events fire on the page.

​
Viewing Event Details

To see detailed information about a specific event:
  1. Click on any event in the list
  2. An expanded view will show all parameters and values associated with that event

​
Common Event Parameters

Typical event data includes:
  • Event Value — The monetary value associated with the event (e.g., product price for AddToCart, total purchase amount for Purchase events)
  • Product Name — The name of the product involved
  • Product ID — The SKU or internal product identifier
  • Click ID — The unique identifier linking this event to the original click/ad impression
  • Event Time — The precise timestamp when the event fired
  • Currency — The currency code for monetary values

​
Checking Event Values

To verify that event values are being captured correctly:
  1. Perform an action on your website (e.g., add a product to cart, complete a purchase)
  2. Open Pixel Helper
  3. Look for the corresponding event in the list
  4. Click the event to expand it
  5. Verify that the Event Value field shows the correct amount
  6. Check that other relevant parameters (product name, product ID, etc.) are populated

​
What to Look For

  • Prices should match — AddToCart event values should match actual product prices
  • Product names should be present — Events should capture the product being acted upon
  • Values should be consistent — Similar actions should show similar event values

​
Verifying Click ID Capture

Click ID is critical for attribution. To verify it’s being captured:
  1. Open Pixel Helper
  2. Find the purchase or conversion event you want to check
  3. Click to expand the event details
  4. Look for the Click ID parameter
  5. Verify it contains a value (not blank or “undefined”)
If Click ID is missing or empty, your attribution chain may be broken. This is a common issue that prevents proper conversion tracking.

​
Identifying Duplicate or Excessive Events

One of Pixel Helper’s most useful features is identifying duplicate events:
  1. Perform a single action on your website (e.g., click an “Add to Cart” button once)
  2. Open Pixel Helper
  3. Check if the same event appears multiple times in the list
  4. Review the timestamps — are they almost identical?
Duplicate events cause: Inflated conversion counts, incorrect revenue attribution, higher reported CPA than actual, and skewed performance metrics.
If you notice the same event firing 2–3 times for a single user action, you likely have duplicate tracking code or multiple pixel implementations on the page.

​
Using Pixel Helper During Troubleshooting

​
Verify Events Are Firing

  1. Perform the action you want to track
  2. Check if the event appears in Pixel Helper within 1–2 seconds
If it doesn’t appear, the event isn’t being tracked at all.

​
Check Event Completeness

  1. Expand the event details
  2. Verify all expected parameters are present
  3. Look for null, undefined, or blank values
  4. Confirm data matches what you expect

​
Spot Real-Time Issues

  1. Monitor the panel while using your site
  2. Watch for unexpected events or missing events
  3. Note any patterns (e.g., events only missing on certain pages)

​
Event Firing Patterns to Know

Healthy Event Flow: Events fire 1–2 seconds after the user action. Each action produces exactly one event (no duplicates). All parameters are populated with correct values. Click ID is present on conversion events.
Problem Patterns: Events fire multiple times for a single action (duplicates). Events don’t fire at all. Parameters show “undefined” or are blank. Click ID is missing from conversion events. Events fire for actions you didn’t perform.

​
Tips for Effective Monitoring

  • Keep Pixel Helper open while testing your website to catch all events.
  • Test from a non-admin account to ensure you’re seeing real user tracking, not admin-only behavior.
  • Clear your browser cache before testing to ensure you have the latest pixel code.
  • Test on different pages — tracking issues are sometimes page-specific.
  • Document what you find — take screenshots of Pixel Helper for support discussions.

​
Verify your testing session

Before you wrap up a debugging session, confirm:
  • The Upstack Data pixel is loaded (open Chrome DevTools → Network and search for ups.min.js).
  • You see at least one event in Pixel Helper after performing the test action.
  • Each tracked action produces exactly one event with the expected parameters.
  • Conversion events include a populated Click ID.
Need help? If you’ve identified issues, see our guides on diagnosing Meta pixel issues or contact Upstack Data support with screenshots.