Ridoway Pixel — conversion tracking for OpenAI AdsInstall free →
← Back to Ridoway Pixel

Changelog

What's new in Ridoway Pixel. Latest updates and improvements.

v1.2.0August 2026

  • Added Conversions API (CAPI) server-side event tracking
  • Automatic event deduplication between browser pixel and CAPI
  • WooCommerce line-item data (SKU, quantity, price, currency)
  • Support for Contact Form 7 and WPForms

v1.1.0July 2026

  • WooCommerce integration (Purchase, AddToCart, BeginCheckout)
  • Admin panel settings page redesign
  • Real-time event log in WordPress admin

v1.0.0June 2026

  • Initial release
  • Browser pixel injection via oaiq.js SDK
  • PageView and ViewContent events
  • WordPress admin settings panel

What changed in 1.2.0, and why it matters

Version 1.2.0 is the release that moved Ridoway Pixel from browser-only tracking to full server-side tracking. Before it, events were fired by the oaiq.jsSDK in the visitor's browser, which meant ad blockers, script timeouts and consent banners could silently swallow conversions. That is the most common reason a ChatGPT Ads account shows clicks but no purchases.

Conversions API support fixes that by sending the same events from your WordPress server instead of from the visitor's machine. The event never touches the browser, so a blocked script no longer means a lost conversion. Automatic deduplication keeps the two paths from double-counting the same purchase when both do succeed.

The form integrations for Contact Form 7 and WPForms, and WooCommerce line-item data, exist for the same reason. A purchase without SKU, quantity, price and currency is a conversion OpenAI cannot use for optimisation, so the plugin captures those fields rather than reporting a bare event.

How to upgrade safely

  1. Update through Plugins → Installed Plugins → Ridoway Pixel → Update. Never upload a new build over an old folder.
  2. Re-enter your Conversions API key in the plugin settings. Keys are not migrated automatically.
  3. Place a test order, then check the event log inside WordPress. You should see the browser event and the server event, deduplicated into one.
  4. Verify from outside your own browser, ideally on a private window, because logged-in WordPress sessions can hide JavaScript problems.

Verifying events after an upgrade

The fastest way to confirm tracking is live is to open your site in a private window with ad-blocking disabled, complete a conversion, and watch the event arrive. Ridoway Pixel's real-time event log inside the WordPress admin shows each event with its source, so you can see whether it came from the browser pixel, the server, or both.

If events are missing, the usual cause is a firewall or security plugin blocking outbound requests from WordPress, not a plugin bug. The Conversions API endpoint must be reachable from your server for server-side events to be delivered.