Verify Events in the Events Manager

Verifying your Reddit Pixel or Conversions API (CAPI) integration will let you know it's accurately sharing events across all browsers and devices. If you don't do this, you may experience ad delivery and measurement challenges.

We recommend implementing the Reddit Pixel and the Conversions API to optimize campaign performance. Sharing the same events using both implementations can help you minimize signal loss and achieve more efficient results, but may cause events to be double-counted. Learn about event deduplication to avoid attribution and reporting discrepancies.

We also recommend passing customer match keys for better match rates and higher attribution rates. This lets you pass high-quality match keys and identifiers (like email, IP, and click ID) using your implementations to increase conversion attribution.

Before you start

Set up the Reddit Pixel or the Conversions API (CAPI). If you're using CAPI, we strongly recommend streaming events to verify them in real-time to reduce delays.

1. Check conversion events

1. Go to the Events Manager and check that all your standard and custom conversion events are listed. If any of your events aren't listed, add those events to your integration.
   • Recommendations for conversions: Ensure Purchase, Lead, and SignUp are included.
   • Requirements for dynamic product ads (DPA): Ensure ViewContent, AddToCart, and Purchase are included. 
2. Verify that your total event counts make sense. For example, if you get a lot of traffic on your site, PageVisit shouldn't be low.
3. Check that your domain is listed if you've set up the Reddit Pixel. Learn more about undetectable domains.
   You'll always see undetectable domains for Conversions API, so you can safely ignore this step. 

2. Test event pass back

Third-party cookies must be enabled for Event Testing to work. Some browsers disable cookies by default, so you'll need to change those settings.

In Event Testing, provide the HTTP or HTTPS URL for a page where you've installed the Reddit Pixel or Conversions API (CAPI) and select Test. If you're testing CAPI without the Reddit Pixel, we strongly recommend streaming events instead of sending them in bulk to reduce delays.

Your page will open in a new tab, and a new PageVisit event should be registered in the Event Testing table. Review your integration setup if the PageVisit event or the correct pixel ID doesn't appear.

Don't close the tab with Event Testing or the tab with your site. Closing either of these tabs will require you to restart testing.

3. Trigger conversion events

Explore your site to manually trigger events and ensure the correct events are being captured. For example, when you add an item to your cart, an AddToCart event should fire.

If you're using the integration with DPA, we recommend configuring at least these actions:

Action	Event
View a variation of a product	ViewContent
Add product to cart	AddToCart
Make a test purchase	Purchase

The event status will be received if the event was configured correctly.

Some events may not be captured in Events Testing. If you don't see any event, try checking it with the Pixel Helper.

As you do that, those events will appear in the table with their status, timestamp, and setup method. Expand each event to reveal more information:

• Pixel ID: Your Pixel ID
• Referrer URL: The page URL where the event is firing on
• Customer match keys: Any configured customer match keys for this event
• Metadata: Any configured event metadata for this event

You'll also be able to see error and warning messages if you have any misconfigurations.

If you don't see an event or you see a warning, the event was improperly configured and isn't firing. Your page action isn't being tracked, which will affect your analytics. We strongly recommend troubleshooting errors as soon as possible.

4. Troubleshooting errors

If any of your events have issues, you can review them in Diagnostics to view your most recent conversion event issues. Expand an issue to get more details and learn how to resolve it. If you decide not to fix it, select Ignore to move it to the Ignored tab. Issues may take up to 24 hours to clear after they've been resolved. 

See more information on errors and warnings by expanding each conversion event. You must resolve errors for your integration to work properly. Warnings should be resolved, but your integration will still work if left unresolved. 

Diagnostics will not call out product metadata not passing. We strongly recommend using the Pixel Helper to check that this type of metadata is being passed.

Common errors

Issue	Description
Metadata value is provided, but currency is missing	A value was provided without a currency. We’ll try to default to your account's chosen currency if available. Otherwise, it will be left empty. Check that a currency is being passed to remove this error.
The same conversionId was provided for too many events	The same conversion ID was provided for more than 100 events. Pass a unique conversion ID for distinct conversion events.
Invalid conversionId provided for event	An invalid conversion ID was provided for the event. Change the conversion ID to a value not equal to one of the following: Undefined Null Empty 00000000-0000-0000-0000-000000000000
Invalid UUID	An invalid UUID was provided for the event. Ensure the UUID is formatted like XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX. Learn more about the standard GUID format.
Invalid phone number	An invalid phone number was provided for the event. Ensure the phone number is formatted like +15554441234.
Invalid click ID	An invalid click ID was provided for the event. Ensure the number matches the one provided for rdt_cid in the URL. Open your ad and select your destination URL to find your click ID. Learn more about generating test URLs.
Placeholder value provided	Placeholder values for customer match keys haven’t been changed. Replace these values or remove the parameters from your integration.
Invalid data processing mode provided for event	An unsupported value was provided for the data processing mode. Check that the data processing mode is set to LDU.

Common warnings

Issue	Description
Event not supported	The event type provided isn’t supported. Set one of our supported events.
Missing custom name	You’ve set this event as a custom event, but haven’t added a custom event name. Set a custom event name and try again.
Invalid metadata	Check that you’re passing supported event metadata and that values are in the right format: Item count: integer Value: number Currency: string that matches a 3-letter currency code Conversion ID: string
Currency doesn’t match your account’s currency	The currency doesn’t match your account’s currency. Check that the event currency matches your account's currency.
Currency was provided without a value	Currency was provided, but a value is missing. Check that value metadata is being passed.
Invalid email	The email provided is invalid or equal to the email of your ad account. Ensure the email is formatted like example@email.com.
Product not in catalog	The provided product ID doesn’t match a product in your catalog. Ensure that this ID can be found in your catalog.
Missing integration type	Your 1x1 Image Pixel is missing its integration type. Add integration=noscript to your implementation.
Invalid integration type	Your 1x1 Image Pixel is using an invalid integration type. Ensure integration is set to noscript.