This reference describes the named events in Advarde’s conversion presets. It is not an exhaustive catalog of every event OpenAI may support. Choose an event because it accurately describes your application’s completed action.
Supported preset events
The table is generated from the same event definitions used by the application. Review the event name, category, and successful-action trigger before installing a snippet.
| Event name | Category | When it should fire |
|---|---|---|
| page_viewed | contents | When the page is viewed after measurement consent. |
| contents_viewed | contents | When a specific product or content item is viewed. |
| items_added | contents | After an item is successfully added to the cart. |
| checkout_started | contents | When the customer begins checkout. |
| order_created | contents | After a purchase is confirmed by your payment system. |
| lead_created | customer_action | After your server accepts a lead form, not on the submit-button click. |
| appointment_scheduled | customer_action | After the booking system confirms an appointment. |
| registration_completed | customer_action | After an account or event registration succeeds. |
| trial_started | plan_enrollment | After the trial is activated. |
| subscription_created | plan_enrollment | After a paid subscription is activated. |
Choose the primary conversion deliberately
A booking funnel can record page views, accepted leads, and confirmed appointments while using the appointment as its primary goal. A SaaS funnel can record registration, trial activation, and paid subscription as distinct stages.
Changing the suggested primary goal in a setup is not a promise that existing campaigns are automatically updated. Review the actual campaign’s conversion configuration separately.
Keep payload identity and value consistent
Provide a stable event ID for the business action. Use a different ID for a different action and preserve the ID across retries of the same action. Confirm the deduplication behavior when browser and server paths both send the event.
When an event carries an amount, use the units required by that measurement endpoint. For the generated integration, amounts are integer currency minor units with an explicit currency. Do not copy advertiser budget micros into an event amount.
Test negative cases as well as success
A rejected payment, failed form, or abandoned booking should not trigger the completed-action event. A page-view event may still be appropriate because the page was viewed; that does not make it a completed purchase.
Test the same action after a refresh and through a retry. Keep evidence of the business record and the emitted event so a future reviewer can distinguish intentional behavior from duplication.
Sources and verification
Platform details checked on September 11, 2026. Your account may expose a different set of features. Examples are illustrative unless a dataset is explicitly supplied.