Server-side conversion tracking for ChatGPT ads — no pixel, no scripts, no personal data by design.

PII (personally identifiable information) is data that can identify a specific person — for example names, email addresses, phone numbers, postal addresses, account numbers, or health details. This plugin is designed so that such information is not included in conversion events by default; only that a conversion occurred (plus optional order total and currency). The page URL is sent as recorded — if your confirmation URLs embed personal data in query parameters, remove it at the source.

Yes — we recommend it. This plugin is a technical measurement tool, not legal advice. Laws vary by jurisdiction and industry (e.g. GDPR, CCPA, HIPAA). Thought Bulb does not provide legal, privacy, or compliance advice and cannot guarantee that your use complies with applicable law. Site owners remain solely responsible for their own privacy obligations and should consult qualified legal counsel before sending conversion data to any third party.

The plugin is designed so that no personally identifiable information (PII) or protected health information (PHI) is transmitted by default: no names, email addresses, phone numbers, form field values, addresses, insurance information or diagnoses. Each event contains only an event ID, the event name, a timestamp, the page URL where the conversion occurred and the event type — plus, for order events, the order total and currency if you enable them. The page URL is sent as recorded; if your confirmation URLs embed personal data in query parameters, remove it at the source. This plugin is a technical measurement tool. Thought Bulb does not provide legal, privacy, or compliance advice. Site owners remain solely responsible for determining whether their use complies with applicable law and should consult qualified legal counsel.

All tracking happens server-side: events are built and sent from PHP when a form or order succeeds. There is no browser JavaScript, pixel snippet or tag-manager container to add — which also means nothing can be blocked by ad blockers and no credential can leak into public HTML.

Built-in support covers Contact Form 7, WPForms, Gravity Forms, Fluent Forms, Formidable Forms and Ninja Forms. Each integration can be enabled or disabled individually, and each has an optional form-ID allowlist — enter only the IDs of your Contact Us or enquiry forms and nothing else will fire.

Your developer fires one documented hook right after a successful lead capture — a single line of code. The custom event name is configurable and defaults to lead, matching the events your forms send.

Not by design. Order events are built to send only the order total and the currency code — excluding the customer name, billing or shipping address, email, phone number and line-item product names. You can disable even the totals with a single setting.

Validate-only is on by default: OpenAI checks each request without recording real conversions. To go live, keep it on, click Send Test Event and confirm OpenAI accepts the payload, submit one real form or order and check the Conversion Log — then switch validate-only off and save. Events are now recorded in OpenAI Ads.

No. Events are sent in the background after the submission completes, every API call is wrapped in error handling with a 5-second timeout, and nothing can bubble up into the form or checkout flow. Failures are recorded in the Conversion Log and retried automatically once, five minutes later.

Yes: a fresh install tracks conversions for 14 days without a license key, with an admin notice counting down the remaining days. After that, an active Gumroad license is required — activation is one click inside wp-admin.