RAM DSP Pixel Debug / Demo

This page shows what our site sends into the RAM DSP pixel and the browser-visible effects.

RAM DSP Pixel Controls

The RAM DSP pixel script is loaded from:
https://up.pixel.ad/assets/up.js?um=1

When the pixel fires, we wrap cntrUpTag.track() to log:

  • The arguments passed (pixel name, ID, etc.).
  • Any cookie changes we can see on this website’s domain.

Loading RAM DSP pixel and inspector…

What this page shows

  • Exactly what our site calls: cntrUpTag.track('cntrData', 'dd731635ddce362e').
  • Any first-party cookies that change on this domain after the pixel fires.
  • In DevTools → Network, you can see the outbound request to RAM DSP servers.

What it does not show

  • The full RAM DSP cookie ID stored on RAM DSP’s own domain.
  • Any server-side processing or matching that RAM DSP does.

For security and privacy reasons, browser JavaScript on this page cannot read third-party cookies or see the DSP’s internal database. It can only see what we send and browser-visible changes on our own site.

How to demo this to a client

  1. Open this page in Chrome.
  2. Press F12 → Network tab.
  3. Reload the page and filter by “up.js”.
  4. Click the RAM DSP pixel request to show URL, query parameters, and cookies.
  5. Use the button above to fire the pixel again and watch the logs update.

RAM DSP Pixel Activity Log