Check the event definition, website implementation, and reporting window when conversions do not appear as expected.
1. Check the event definition
Open Tools → Custom Conversions. Confirm the account, event name, website source, and attribution window. A custom name must match the name your website sends. Creating the definition in Advarde does not install a pixel or server-side integration.
2. Verify the website action
Complete the action that should trigger the event. Check the browser integration only after the relevant consent has been given. The public ChatGPT Pixel Helper can inspect browser calls and observed events. For a server-side integration, ask the developer to inspect delivery logs and the provider response.
3. Separate event delivery from attribution
A browser observation is not proof that the server accepted an event, and an accepted event is not automatically an attributed ad conversion. Review the selected date range, source, and data availability before comparing results. Keep missing or unavailable values distinct from zero.
If the problem remains
Record the affected screen, event name, time, and steps you took. In the app, use Send feedback and choose the bug-report option. Include a redacted screenshot if useful. Do not paste an advertiser key or customer information. Check for existing results before repeating a purchase or other irreversible action.
