OpenAI Ads Conversions Setup

Overview

Use this skill to add, extend, or review OpenAI Ads conversion instrumentation in an advertiser repository. It supports browser Pixel setup, server-side Conversions API setup, Pixel+CAPI deduplication, and incremental reruns after the app adds new pages or flows, while keeping diffs small and avoiding secret exposure.

Use only public OpenAI Ads documentation and repository-local patterns for implementation choices. If the docs are unavailable or unclear, ask for clarification or leave a documented follow-up instead of relying on undocumented behavior.

Required Inputs

Before editing code, identify:

• Setup mode: pixel, capi, or pixel+capi.
• Frontend/runtime surface: browser JavaScript/TypeScript, server-rendered web, backend-only, mobile/native, or unknown.
• Pixel ID, if Pixel is in scope.
• CAPI authentication plan, if CAPI is in scope: existing secret/env var name, secret manager path, or placeholder-only.
• Conversion events to instrument and where they occur in the product flow.
• Whether this is a first-time setup or an incremental rerun extending existing OpenAI Ads instrumentation.
• Whether the desired behavior is propose patch, apply local patch, or review existing integration.