Contact Ridoway
For questions, partnerships, or support — reach out via the links below. Most tracking problems are already answered in the docs, so check there first if it saves you a round trip.
Include the URL and the tool you were using. A screenshot of the failing state saves a reply.
Social
X (Twitter)Answered before you write
These are the questions support receives most. Each answer links straight to the tool or guide that solves it.
My OpenAI pixel fires in the browser but Conversions API events never arrive. Where do I start?
Check the plugin docs for the CAPI setup path first — most failures are a missing data source ID or a duplicated event_id on both sends. The Pixel Helper extension shows live network requests so you can confirm whether the server call is being made at all.
Pixel Helper docsDoes the Ridoway Pixel plugin support WooCommerce?
Yes. Install the plugin, then follow the WooCommerce guide — it wires purchase, refund and custom events and documents the event_id deduplication rules so browser and server events do not double-count a sale.
WooCommerce guideAm I eligible to run ChatGPT Ads?
The eligibility tool checks your account, brand review and data source state in about a minute. It reports the specific requirement you are missing rather than a yes or no.
Eligibility checkerI want to report a bug in a free tool.
Open an issue on the extension repository with the URL, the tool you used, and what you expected. If the tool is not firing correctly in your browser, the network log from Pixel Helper speeds up diagnosis considerably.
Extension docsWhat to include in a bug report
A short, complete report gets fixed faster than a long one. These four details are usually enough:
- 1. The URL you were on, and whether the problem reproduces on a private window.
- 2. The tool or page involved, by name.
- 3. What you expected versus what you saw, quoted exactly.
- 4. Browser and extension version, if a browser tool or the extension is involved.
Ridoway is an independent team, so response times are not 24/7. Public GitHub issues are usually the fastest route because they are not queued behind email.