Soku provides a self-service path from payment to advertiser setup and conversion tracking. Start from the Soku Brand you want to advertise rather than looking for a separate OpenAI advertiser registration flow.

For agencies, repeat the setup inside each client Brand. Sites, public/server keys, Pixel, CAPI, advertiser, reporting account, events, and verification are isolated by Brand even when two clients use the same website origin. Never copy a key or snippet from one Brand into another Brand's website.

Before you start

Creating a new payment requires:

an active or trialing Starter, Pro, or Enterprise subscription;
Organization Admin access;
a valid Brand website and owner email;
a target daily budget of at least the configured minimum (default $25).

Other Brand members can view setup, Funding, and Tracking status, but they cannot create a Stripe Checkout.

Fund and set up the advertiser

Open the Brand you want to advertise.
Open the top-level Integrations entry in the sidebar.
Find ChatGPT Ads.
Choose the Funding action shown on the card.
Confirm the Brand website, owner email, and target daily budget.
Continue to Stripe Checkout and complete payment.

Soku prepays 15 days of the target budget, so the default $25 daily minimum suggests a $375 advertising deposit. The processing surcharge shown before Checkout is not part of the spendable balance. See ChatGPT Ads funding and balance for how the principal, Funding status, and balance protection work.

Returning from Stripe does not itself confirm payment. The card may show Payment processing while Soku waits for Stripe's signed confirmation. Once payment is confirmed, Soku automatically creates and links a dedicated advertiser, reporting account, Site, Pixel, and CAPI configuration for the current Brand. Normal setup does not require an operations review or manual account mapping.

Optional: install and verify the Soku Pixel

Tracking setup and verification are optional. You can create and activate campaigns without installing or verifying the Soku Pixel. If you want browser-event tracking, follow these steps when setup reaches Ready to install:

Open the ChatGPT Ads setup dialog.
Copy the Soku public key and SDK snippet.
Add the snippet to the Brand website.
Open the installed website so it sends a real browser event.
Return to Soku and choose Verify.

Verification reads real events that Soku successfully forwarded upstream. The Verify action does not create a synthetic event or mark the Pixel valid by itself. If you choose to verify Tracking, real browser events are required to mark that Tracking status ready; this is not a campaign creation or activation requirement. Server Events are reported separately as disabled, pending, valid, or invalid.

The copied pk_ and server sk_ belong only to the current Brand. Switching Brand in Soku shows that Brand's own keys and verification state; an event sent with Brand A's key never verifies Brand B.

Once Soku has created your advertiser and reporting account, the ChatGPT Ads card remains the place to access setup guidance and account funding — but it is not where you look at campaigns. Your live campaigns live in Dashboard → Campaigns.

Where to see your campaigns

Open Dashboard from the left sidebar and switch to the Campaigns tab. It lists your ChatGPT Ads campaigns with their ad groups and ads — name, status, budget, and metrics for the selected date range — and you can create or edit campaigns from there.

For a one-click route, ask Soku in Chat where to see the campaign. It checks the current brand before returning the in-app link, so follow the link in that answer rather than reusing a URL from another brand. If the Campaigns destination is not ready, Soku points to the relevant Integrations setup instead of guessing a dashboard route.

Saving a Draft does not launch it. Managed Launch first creates the hierarchy paused, then enables its ad groups and ads before enabling the campaign. Confirm completion from the returned result and current readback. Active is a configured state; it does not prove OpenAI approval or actual delivery. Review results, observed delivery metrics and reporting freshness are separate facts. The list shows every status by default, so you do not need to change any filter to see a paused campaign.
The Campaigns tab only appears once the brand has a ChatGPT Ads ad account assigned to it. Before that, the tab is hidden; open a ChatGPT Ads account from Integrations first. There is nothing to connect or authorize — Soku creates the account once your payment is confirmed.
If the brand has more than one ChatGPT Ads account, pick the account from the selector in the tab row.
Campaign spend and performance also roll up into the other dashboard views — the Breakdown tab pivots by campaign across every connected platform.

For Server Events, follow the implementation guide linked from the setup dialog and send conversion events from your backend to the Soku CAPI endpoint. Never put a server key in browser code.

Funding status and balance protection

The setup dialog shows the confirmed principal, spend, available budget, and a Funding status. Soku also pauses campaigns automatically when the available budget runs out; after you top up, you resume them yourself. Both are described in ChatGPT Ads funding and balance.

Prepare and launch a campaign

You can prepare campaign materials and ask Soku to create a ChatGPT Ads media plan whether or not you enable Tracking. Campaign creation, review, saving, and launch remain separate from advertiser Funding and Pixel verification; setup status does not silently launch or activate a campaign.

Troubleshooting

Upgrade required: ask an Organization Admin to activate Starter, Pro, or Enterprise.
You can view status but cannot pay: only an Organization Admin can create Checkout.
Payment processing: wait for signed Stripe confirmation; do not start another differently configured Checkout.
Setting up: payment is confirmed and automated advertiser setup is still running.
Waiting for events: if you want to enable Tracking, install the snippet, open the live page, then Verify again. You may leave Tracking unverified; this does not block campaign creation or activation.
Campaign activation rejected: ask Soku to investigate the returned error. An HTTP 422 alone does not establish a funding, Pixel, or creative-asset problem.
Funding is stale or unknown: see ChatGPT Ads funding and balance; do not treat an old value as current.
Needs attention: Soku has preserved the payment and setup evidence. Use the in-app Feedback button or the Soku contact form; do not pay again unless support explicitly asks you to.
You cannot find the Campaigns tab: it renders only when the Brand has a ChatGPT Ads ad account assigned to it. Check Integrations → ChatGPT Ads — either this Brand has not opened an account yet, or the account is assigned to a different Brand than the one you are currently in.

Policy and capability questions

Before preparing campaign content, read the ChatGPT Ads policy and capability guide. It distinguishes policy eligibility, current Soku capabilities and what has actually been checked.