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 Pro or Enterprise subscription;
Organization Admin access;
a valid Brand website and owner email;
a target daily budget of at least $100.

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. A $100 daily budget therefore creates a $1,500 advertising principal. Stripe also adds the processing surcharge estimate shown before Checkout; that surcharge is not part of the spendable advertising balance.

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.

Install and verify the Soku Pixel

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. Browser events are required for the overall Tracking status. 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 your reporting account is linked, 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, the fifth tab of the brand dashboard.

Where to see your campaigns

Open Dashboard from the left nav and switch to the Campaigns tab (after Overview, Breakdown, Quadrants, and GA4). 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.

The Campaigns tab only appears once the brand has a linked ChatGPT Ads ad account. Before that, the tab is hidden; link the account from Integrations first.
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.

Read Funding status

The same setup dialog shows:

confirmed advertising principal;
total spend and available budget;
spend-data freshness;
ready, low, insufficient, stale, or unknown Funding status.

A stale or unknown status means Soku cannot currently prove a fresh balance. It does not mean the balance is zero. Refunds and disputes adjust the advertising principal but do not delete an advertiser that has already been created.

What happens after Tracking is ready

You can prepare campaign materials and ask Soku to create a ChatGPT Ads media plan. 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 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: install the snippet, open the live page, then Verify again.
Funding is stale or unknown: use the displayed timestamp and contact support if it does not recover; 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 linked ChatGPT Ads ad account. Check Integrations → ChatGPT Ads, and make sure the ad account is assigned to the Brand you are currently in.