Setting up OpenAI Ads Pixel

Use OpenAI Ads Pixel to measure storefront activity for ChatGPT ads. Nevuto installs the browser measurement pixel using your Pixel ID. An optional Conversions API Key adds server event delivery, including purchases associated with paid storefront orders.

Before you start

• Sign in as the store owner, or use a staff account with access to manage Apps and integration settings.
• Have access to your advertiser account and its conversion setup in OpenAI Ads Manager. Features available to your account determine which controls you can use there.
• Create or select the intended pixel in the Conversions area and copy its Pixel ID. See OpenAI's Measurement Pixel guide.
• If you want server events, obtain a Conversions API key for the intended pixel/account from the conversion setup. This is an advertising measurement credential, separate from a model API key or a ChatGPT subscription. See the official Conversions API guide.

Use a separate test data source where your advertiser setup permits it. Nevuto has no sandbox or test-event-code control for this integration; setup tests can send events to the pixel you configure.

Install or open OpenAI Ads Pixel

1. Open Settings > Apps in Nevuto Admin.
2. Click Explore apps, find OpenAI Ads Pixel, and start its installation for the intended store.
3. Review the Install OpenAI Ads Pixel? permissions and click Install app.
4. For an existing installation, open its app details in Settings > Apps and click Open app.

The installation confirmation shown before the app was added to the demo store. Installation and enabling measurement are separate actions. Select an image to view it at full size.

Configure browser measurement

In the OpenAI Ads Pixel configuration:

1. Enter the copied identifier in Pixel ID. Paste only the ID, without script code or a URL.
2. Turn on Enable OpenAI Ads Pixel when you are ready to collect events.
3. Leave Conversions API Key empty if you want browser measurement only.
4. Click Save. Resolve any error, then reopen the form to confirm the saved ID and enabled setting.

Initial configuration with no identifier or key entered and measurement disabled. Save becomes available after a change. A successful save checks the submitted format and stores settings; it does not confirm event receipt or attribution.

The integration sends browser page visits as page_viewed. The current storefront also includes product-view measurement, and the order-completed screen sends order_created. Avoid installing another independent copy of the same pixel through a theme or tag manager, which can duplicate activity.

Add optional server measurement

Use the Conversions API credential belonging to the same conversion setup as your Pixel ID:

1. Expand Conversions API (Advanced).
2. Paste the credential into Conversions API Key.
3. Check Enable OpenAI Ads Pixel and click Save.
4. Reopen the configuration to confirm the settings before testing delivery.

The advanced section expanded for reference. The key is empty and measurement is off. No advertiser connection or event delivery was tested for this screenshot.

The API key is used by Nevuto's servers; do not paste it into a theme, browser console, public document, or support message. Browser-only measurement does not require this key. Adding it does not bypass the store's marketing-consent settings or guarantee that every event will be delivered or attributed to an ad.

Verify the complete customer flow

After saving your own test configuration:

1. Open the storefront in a separate browser tab and grant marketing consent if requested by your store's privacy settings.
2. Visit a page and open a product. In your advertiser account's measurement diagnostics, check recent events for the intended pixel and website, including page_viewed and contents_viewed.
3. Complete a test checkout using your payment provider's test environment, including successful payment and the return to the store.
4. Compare the paid order in Nevuto with the corresponding order_created event. Check the currency, value, and order reference. For example, verify a 50.00 USD test order against its recorded purchase value.
5. If you supplied a Conversions API key, check server delivery as well as browser delivery. Browser and server copies of one purchase should count as the same conversion rather than two orders.
6. Test a cancelled or failed payment and check that it does not produce a successful paid-order event.

Check soon after your test. OpenAI's measurement troubleshooting guide distinguishes recent event delivery from historical attributed results. Seeing an event arrive does not establish that it will count as a conversion attributed to an ad.

These are steps to run with your own advertiser credentials. The screenshots show Nevuto's settings screens, not an OpenAI Ads Manager dashboard or a completed tracking test.

A browser order_created event reflects checkout completion. For manual payment methods, the order can still be awaiting payment at that point. Server purchase events follow the order being marked paid; use Nevuto's payment status when reconciling measurement with collected payments.

Prepare normal reporting

Before collecting production activity, confirm the intended production Pixel ID and its matching Conversions API key, if used. Turn on Enable OpenAI Ads Pixel, click Save, and reopen settings to verify them. Run a fresh delivery check against that pixel.

Pixel configuration does not create an ad campaign or submit a product feed. Product catalog links shown elsewhere in Settings > Apps serve a separate purpose. Your payment provider's sandbox setting also does not create a sandbox for OpenAI measurement.

Edit or stop measurement

Open Settings > Apps > OpenAI Ads Pixel > Open app to replace the ID or key. To stop this integration's browser and server measurement, turn off Enable OpenAI Ads Pixel and click Save. This does not delete events already received by OpenAI, and does not stop any separate tracking code installed elsewhere.

Troubleshooting

• The settings form is unavailable: Confirm the app is installed for the intended store and that your staff role can manage integration settings.
• Save is disabled: There are no unsaved changes on the form.
• The Pixel ID is rejected: Copy the exact ID from your conversion setup, without spaces, a URL, or script tags. Do not substitute an ad account ID.
• Browser events are missing: Check the saved ID, enabled setting, marketing consent, and browser extensions. Use the storefront, not the admin page.
• Browser events arrive but server purchases do not: Confirm you supplied a Conversions API key for the correct setup, not a model API key, and that the order is paid. Ask support to inspect delivery using the order reference and test time; do not share the key.
• Events arrive but conversions are absent: Confirm you are checking the intended pixel and reporting scope. Receipt and advertising attribution are separate checks.