Interactive demo · Synthetic events
See a booking event
in Pixel Helper.
Try consent, a successful booking, and a rejected action. Everything stays in this page’s memory. No booking is made and no event is sent to OpenAI.
Three steps to your first inspection
- Install Pixel Helper in desktop Chrome, then return here and open the extension.
-
Look for
pixel_advarde_demo_onlyand denied consent. Choose Allow demo consent below. -
Choose Confirm new demo booking. Reopen the helper: expect one
appointment_scheduledcall.
The helper observes calls. It cannot confirm OpenAI receipt or attribution. This demo uses Advarde’s generated helper with a synthetic SDK; it does not run a GTM container.
Try the different outcomes
Demo consent: Denied. This only changes the simulation.
0 booking calls in the synthetic SDK
What should happen?
- Consent denied or withdrawn: a confirmed booking adds no call. Allowing consent later does not replay it.
- Successful booking with consent: one new call with a new demo booking ID.
- Rejected booking: no completed-action call.
- Repeated callback: no extra call. This demo’s application code guards repeats; the generated tracking helper does not deduplicate them.
Reload to reset the demo. After a reload, open the extension again to start a new inspection.
Follow the full GTM installation guide →