PixelBridge: ChatGPT Ads Pixel Tracking

PixelBridge, also known as AI Ads Pixel, helps you track ChatGPT Ads and OpenAI Ads conversions on WordPress without building a custom tracking implementation. Install the official OpenAI Ads Measurement Pixel, track leads and WooCommerce actions, optionally send events through the Conversions API, and use built-in diagnostics to check whether your setup is actually working. Official website: AIAdsPixel.com Documentation: Getting started and install the OpenAI Ads Pixel on WordPress. PixelBridge is an independent product and is not affiliated with, endorsed by, or sponsored by OpenAI. Track conversions, not just page views. PixelBridge can connect common WordPress actions to supported OpenAI Ads events, including leads, registrations, appointments and ecommerce activity. Verify your tracking before you rely on it. The Diagnostics tools help identify common problems with the Pixel, consent, attribution, Conversions API and event delivery. What PixelBridge does

• Installs the official OpenAI Ads Measurement Pixel
• Tracks supported conversion events from WordPress
• Tracks WooCommerce ecommerce actions
• Tracks successful form submissions
• Supports optional server-side Conversions API tracking
• Uses shared event IDs for browser/server deduplication where supported
• Respects consent before measurement is activated
• Preserves OpenAI Ads attribution identifiers such as oppref and obref
• Provides diagnostics to help verify that tracking works
• Keeps a local event log for debugging

Know whether your tracking actually works Installing a tracking script is only part of the job. PixelBridge includes diagnostics designed to help identify common OpenAI Ads measurement problems, including:

• Pixel SDK availability
• Pixel configuration
• consent configuration
• attribution handling
• Conversions API configuration and the last validation result
• Content Security Policy issues that may block the Pixel
• duplicate or conflicting setups where currently detectable

The local event log records event names, delivery status and whether attribution identifiers were present, without storing the identifier values or customer form data. This makes PixelBridge useful both for initial setup and for troubleshooting an existing OpenAI Ads implementation. WordPress integrations WooCommerce Track product views, add-to-cart actions, checkout starts and completed orders using supported OpenAI Ads ecommerce events. Contact Form 7 Track successful form submissions as lead events. Validation failures and spam rejections are not counted. Elementor Pro Forms Track successful form records as lead events. WPForms Track successful form submissions as lead events. Cal.com Track completed embed bookings as appointment events when the documented bookingSuccessfulV2 event is available. WordPress Track page views after consent, and optionally track public self-registration. Admin-created users and imports are not tracked. URL conversion rules Track thank-you and confirmation URLs for tools that do not have a dedicated integration. More integrations are planned based on user demand. Supported conversion events Which events run depends on the integrations and rules you enable. Customer actions

• lead_created
• registration_completed
• appointment_scheduled

Commerce

• contents_viewed
• items_added
• checkout_started
• order_created

Plan enrollment

• trial_started
• subscription_created

These two events can be sent with URL conversion rules. There is no separate subscription or trial integration. General

• page_viewed
• custom

Browser Pixel and Conversions API PixelBridge supports the official browser Measurement Pixel and optional server-side conversion delivery through the OpenAI Ads Conversions API. When the same conversion is sent through both methods, PixelBridge uses matching event IDs where supported so OpenAI can deduplicate browser and server delivery. The Conversions API is optional. You can use PixelBridge with browser tracking only. A CAPI key can be stored in WordPress settings or configured securely in wp-config.php. Consent Consent is required before the official Pixel SDK is loaded and before conversion events are sent. Server-side events follow the same decision. Supported modes:

• WordPress Consent API
• Manual JavaScript or PHP consent
• Unmanaged tracking after an explicit acknowledgement

If you select the WordPress Consent API and it is not available, measurement does not start. You remain responsible for configuring consent so it matches the legal requirements of your site. Privacy PixelBridge does not send telemetry to AIAdsPixel.com. Measurement requests go to OpenAI only when tracking is configured and consent allows it. The event log stores event names, statuses, and whether attribution identifiers were present. It does not store the identifier values, emails, phone numbers, or API keys. Getting started

1. Create an OpenAI Ads Pixel ID in Ads Manager.
2. Install and activate PixelBridge.
3. Enter the Pixel ID in PixelBridge settings.
4. Configure consent.
5. Enable the integrations you use.
6. Optionally connect the Conversions API.
7. Open Diagnostics and verify the setup.

Advanced configuration A Conversions API key can be defined as AIADSPIXEL_CAPI_KEY in wp-config.php. The previous AIAP_CAPI_KEY constant is still accepted. The plugin can test credentials with validate_only so a production conversion is not recorded.

0.1.10

• Ask for an honest WordPress.org review after at least 7 days of use and after tracking has succeeded. The prompt is dismissible and offers no reward.

0.1.9

• Switch the text domain and plugin folder to pixelbridge-ads-tracking-for-openai to match the WordPress.org slug.

0.1.8

• Allow activation when WordPress loads the plugin file more than once. The previous guard used wp_die and was reported as a fatal error.

0.1.7

• Prevent a fatal error when the previous ai-ads-pixel folder is still active beside this version.

0.1.6

• Ship the plugin folder as pixelbridge-ads-tracking-for-openai so it matches the WordPress.org slug and text domain.
• Escape the legacy event-log table rename during prefix migration.

0.1.5

• Align the text domain with the WordPress.org plugin slug pixelbridge-ads-tracking-for-openai.

0.1.4

• WordPress.org compliance revision: distinctive aiadspixel_ prefix, display name update, and external-service disclosure.
• Safe migration from previous aiap_ option, cron, and event-log names.
• Consent now fails closed when the WordPress Consent API is selected but unavailable.
• Official Pixel SDK loads only after consent is granted.

0.1.3

• Review-prep release with consent, diagnostics, and Conversions API validation work.

0.1.0

• Initial public testing release.
• Official OpenAI Measurement Pixel loader.
• Consent, page_viewed, Conversions API, diagnostics, form and WooCommerce integrations.