OpenAI Book Demo Conversion Tracking
Implemented and QA’d the client’s OpenAI Ads Book Demo conversion tracking. The existing setup sent appointment_scheduled and registration_completed, but the real business action was a Book Demo form submit. GTM Preview showed the live form emitted gtm.formSubmit, while the old tags depended on form_submission. The fix kept the working OpenAI base pixel, created a dedicated book_demo_form_submit event, scoped the trigger to /book-demo, and removed the misleading OpenAI conversion tags from this flow. Network inspection confirmed OpenAI SDK/config/event requests were accepted. A separate QA/Audit ticket was recommended for legacy Google Ads, LinkedIn, and Reddit tags observed during the review.
The fix corrected not just a trigger, but the meaning of the conversion event itself.
Role: GTM and OpenAI Ads tracking implementer
The Problem
The client needed OpenAI Ads conversion tracking installed for Book A Demo so paid media could measure lead-generation performance.
Existing OpenAI conversion tags used appointment_scheduled and registration_completed, which did not represent the actual action. They also depended on form_submission, while the live site preview showed gtm.formSubmit on /book-demo and /register-interest.
The OpenAI base pixel did load and send requests, so the issue was not simply missing pixel installation. The conversion event taxonomy, trigger logic, user data coverage warning, and possible legacy platform tags had to be separated carefully to avoid over-scoping the ticket.
Approach & Architecture
Verified that the OpenAI base pixel was firing by checking DevTools network calls to the OpenAI SDK, pixel config, and events endpoint. Replaced the misleading conversion model with a dedicated book_demo_form_submit custom event. Created a GTM trigger for the /book-demo form submit and configured the new OpenAI conversion tag while removing or pausing previous OpenAI tags for appointment_scheduled and registration_completed. Documented that other platform tags appeared legacy/misaligned and should be handled through a separate QA/Audit ticket.
The GTM container retained the OpenAI base pixel GRYoePGa867BBnWKL6vmGr for page-level tracking. A new Book Demo form trigger scoped to /book-demo fired a Custom HTML tag calling oaiq('measure', 'book_demo_form_submit', { type: 'customer_action' }). The implementation was validated in GTM Preview and browser network tools.
Key Decisions & Trade-offs
Hardest Part
Separating base pixel delivery, event naming, trigger failure, and user data coverage into distinct issues instead of treating all OpenAI warnings as one problem.
Technical Detail
OpenAI Book Demo action modeled as custom event book_demo_form_submit; appointment_scheduled and registration_completed excluded from this flow.
Browser GTM container on client.com.
Used GTM Preview, DevTools Network, and OpenAI Ads data source/event stream validation. Network calls showed oaiq.min.js 200, pixel-config 200, and events request 202 Accepted.
Code
if (typeof window.oaiq === "function") { window.oaiq("measure", "book_demo_form_submit", { type: "customer_action" }); }
ChatGPT was used to inspect ticket details, reason through GTM preview findings, correct event taxonomy, produce implementation steps, troubleshoot GTM trigger warnings, and draft final Asana documentation.
Measured Results
The ticket was closed with OpenAI Book Demo tracking configured and tested. Pablo deliberately left Google Ads, LinkedIn, and Reddit tag cleanup out of scope and recommended a separate QA/Audit ticket because those platforms had legacy or misaligned conversion triggers.
| Metric | Value | Before | Source |
|---|---|---|---|
| OpenAI email coverage warning Warning noted but not fully remediated because no stable external_id/schema/consent approval was confirmed. | 0.0% / 733 events | n/a | OpenAI Ads data source warning screenshot |
| OpenAI external ID coverage warning No external_id was invented because no stable user/contact ID was available in browser. | 0.0% / 733 events | n/a | OpenAI Ads data source warning screenshot |
Every figure above was recorded during the work itself. Where no number was measured, none is claimed.