Curve Pixel Helper

Shows each Curve event as it fires on the page you are viewing, with its status and any possible personal data flags.

Curve Pixel Helper lists each Curve event a page sends while you test it, with the event's name, the time, the page it came from and a status that says whether Curve received the event, held it, blocked it, or could not send it. Each row is one event. When Curve did not send an event, the row gives the reason. Read the status and the reason together before you decide what to change on your site. Pixel Helper only reads the page. The events your site sends do not change. Use it to check a form, a booking flow or a single button before you rely on it. Start with one page. Run it before a campaign goes live. Any page with the Curve script works, in Google Chrome or Microsoft Edge. To use it: 1. Open a page on your site where the Curve script is installed. 2. Select the Pixel Helper icon. The first time you check a site, select Allow Pixel Helper on this site, then reload the page. 3. Do the thing you want to check. The event appears in the list, and its status updates as Curve replies. Pixel Helper reads only the sites you allow. Each site is allowed on its own, so allowing example.com does not allow www.example.com. Removing a site stops it reading that site and clears that site's rows. What it shows: - The name, time, status and page address of each event. The address shows the site and the path only. The query string and the fragment are never shown. - Flags for values that may be personal data: five or more digits in a row, a date like 10/29/2026, or a code such as AB1234. A flag never includes the value. A flag can be wrong, so check the event before you change anything. - A short account code, so you can see whether the page uses your account's tracking key. - An optional check of event names against a list of names copied from Curve. What it does not do: - The values an event carries are never shown. - Whether an ad platform received the event is not shown. Event Logs in Curve show that. - Events, tracking keys and page addresses are never sent anywhere. The only network request checks for a newer version. Curve's tracking script must be on the page you test. Event Logs and the optional list of event names need a Curve account.