Documentation

What Ridoway Pixel actually does

Ridoway Pixel connects your WordPress site to OpenAI Ads (ChatGPT Ads) so that the actions people take on your site are recorded as measurable conversions. It works on two paths at the same time, which is the reason it is more reliable than a snippet pasted into your theme.

The browser path injects the oaiq.js SDK and fires events client-side, which is fast and requires no server configuration. The server path sends the same events from WordPress through the OpenAI Conversions API, which means they survive ad blockers, script timeouts and consent banners. When both succeed for the same action, the plugin deduplicates them so you are never double-counting a purchase.

Events you can track

• page_viewed and contents_viewed — every page load, plus product views for WooCommerce products.
• items_added and checkout_started — cart and checkout steps, fired from WooCommerce hooks rather than from button clicks.
• order_created — includes line-item data such as SKU, quantity, price and currency, which OpenAI needs to optimise against value.
• lead_created — fired on successful Contact Form 7 or WPForms submission, server-side, so it works even when the browser path is blocked.

Requirements

• WordPress 6.0 or newer, running the classic or block editor. WooCommerce 7.0+ for store events.
• An OpenAI Ads account with pixel access, plus the pixel ID from that account.
• For server-side events: a Conversions API key, created in OpenAI Ads under Settings. Keys are stored only in your own WordPress database.
• Outbound HTTPS from your server to the OpenAI endpoint. Most security plugins allow this by default; some do not.

Start here

If you have not installed the plugin yet, begin with the installation guide, then complete the WooCommerce or form integration that matches your site. Only the contact form and WPForms guides are needed if you run a lead-generation site rather than a store.

After setup, verify it rather than assuming. Open your site in a private window, complete one conversion, and confirm the event appears in the plugin's event log. If nothing arrives, the most common cause is outbound requests being blocked rather than a plugin fault.