A first ChatGPT Ads campaign should not move directly from an idea, a budget and two pieces of ad copy to launch. The channel is new enough that availability, brand review, billing, conversion signals and reporting can stop or distort a test before its message has been evaluated properly. A good checklist does not slow launch; it prevents a business from paying to discover issues that could have been checked in advance.
This guide turns the current documentation into an operating process for a business advertising from Romania. It is not a generic list of boxes. Every stage has an observable result, an owner and an exit condition. For features that differ across accounts, first consult our dated ChatGPT Ads map of options that are live or still rolling out.
The launch criterion: a campaign is ready when the account can pay, the ad can be approved, the landing page can convert, the event can be verified and the team knows what to do if delivery does not begin.
Phase 1: ownership, access and responsibility
The ad account should be created for the legal entity that will advertise and be billed. Ads Manager documentation makes the entity's country, currency and time zone important choices; some cannot later be changed through self-service. An agency should not create a client's account under the agency's identity. The client creates it, retains ownership and invites collaborators into appropriate roles.
Check:
- the legal name and country match billing documents;
- currency and time zone suit financial reporting;
- an internal owner exists rather than access belonging only to an external supplier;
- each user has only the permissions they need;
- budget, creative, tracking and launch approvals have named owners.
Exit condition: the business can independently access the account, payment method and change history. If an external provider is the only party with access, correct the structure before launching.
Phase 2: verify actual availability
Romania appears in the current list of countries with self-service Ads Manager access. Country availability still does not guarantee that every format, product feed, spend control or plugin is active in the account. Verification belongs in the real configuration, not merely in an article or a screenshot from another region.
Record the date and answer for each item: available objectives, bidding strategies, geo targeting, platforms, custom audiences, feeds, conversion events, billing model and the Ads Manager plugin if relevant. A feature that does not appear should not become a critical launch dependency.
Exit condition: the chosen workflow can be built today without relying on a promised but absent feature. A simple campaign that exists now is a better first test than a sophisticated architecture that may arrive later.
Phase 3: commercial outcome and offer
The campaign needs one primary objective expressed in business terms. “Visibility” can be a communication objective, but it does not tell the company which decision to make after the test. A useful formulation is: the chosen audience should complete a defined action, at an acceptable cost or volume, in response to a clear offer.
| Business type | Suitable primary result | Useful intermediate signal |
|---|---|---|
| B2B services | A qualified enquiry accepted by sales | Service-page visit or form start |
| Ecommerce | Paid order with correct value and currency | Add to cart or checkout start |
| Appointments | Confirmed booking | Service or time-slot selection |
| Software product | Activated account or qualified demo | Pricing-page visit or registration start |
The offer must make sense without the whole ChatGPT conversation: what the person receives, who it is for, what the next step is and which important conditions apply. Claims need evidence. OpenAI policies require truthful ads, the necessary rights to materials and a working destination.
Exit condition: the team can describe the offer, audience and measured result in two sentences. If every department gives a different answer, the campaign is not ready.
Phase 4: the landing page
An ad does not repair a slow, ambiguous landing page or one that conflicts with intent. Before producing all creative variants, test the page on phone and desktop, with a cold cache and an ordinary connection. The first message should confirm the ad's promise immediately and the requested action should be easy to find.
Landing-page checklist:
- public URL, valid HTTPS and no accidental authentication;
- a heading that matches the ad offer;
- a concrete benefit and limitations without exaggeration;
- appropriate evidence such as process, examples, certification or genuine testimonials;
- a short form with validation and clear error messages;
- company identity and contact information that are easy to locate;
- suitable privacy, cookie and terms information;
- a confirmation state that cannot fire conversions repeatedly.
Exit condition: someone who did not work on the project can complete the action and explain the offer unaided.
Phase 5: end-to-end measurement
Select one active standard event for the primary outcome and define its exact trigger. For conversion-optimized campaigns, the current documentation requires exactly one active standard conversion event. Secondary events can remain available for analysis, but they should not compete with the principal signal.
Pixel and Conversions API can work together. For one action they should transmit the same Pixel ID, event name and event ID so deduplication can operate. The Conversions API key remains on the server. Eligible matching data is normalized and hashed according to the documentation, and consent choices are respected.
Our detailed audit of measurement, privacy and attribution risks explains the difference between a technical conversion and a commercial outcome. For this checklist, the minimum test is:
- complete one real test action;
- confirm ID, name, time, currency and value;
- verify receipt through browser and server paths;
- confirm that deduplication leaves one conversion;
- locate the same action in CRM or commerce data;
- record how long it takes to appear in reporting.
Exit condition: the team can start from a reported conversion and find the internal result that supports it.
Phase 6: audience and context
Targeting should be specific enough for the offer but not fragmented until every group lacks volume. ChatGPT Ads documents geography, platforms, custom audiences and context hints. Context hints are not exact keywords and do not replace other filters.
For a custom audience used for inclusion or bid multipliers, current documentation requires at least 25,000 matched users. Uploaded rows are not the same as matched people. Ready audiences used only for exclusion can operate without that minimum under the present rules.
In a first test, avoid combining too many hypotheses in one group. If geography, message, offer and landing page all change simultaneously, you will not know which factor produced the difference. Choose one dominant hypothesis and keep the rest comparable.
Exit condition: there is a simple explanation of who can see the ad, who is excluded and why the estimated size is sufficient.
Phase 7: budget, bidding and limits
Campaign budget is not the billing threshold and is not the account spending limit. In postpay billing, the threshold can trigger a charge before the normal date, but it does not cap campaign spend. A failed payment can stop delivery. After a pause or update, spend and reporting may also continue to settle for a period.
For maximize_clicks and maximize_conversions, current documentation requires a daily budget and click billing in the standard configuration. maximize_conversions needs the valid primary event. Fixed bidding provides direct control and supports eligible multipliers, but it does not automatically produce better efficiency.
The pilot budget should be large enough to create an evaluable signal without turning a tracking fault into a large loss. Write down:
- daily budget and minimum duration;
- total financial exposure accepted;
- who can change the budget;
- alert threshold and stop conditions;
- the maximum acceptable cost for a valid outcome, not merely a form submission.
Exit condition: campaign budget, account limit, payment method and internal approval rule do not conflict.
Phase 8: creative and policy review
Campaign management documentation specifies a 3–50 character title, body copy up to 100 characters and an image of at least 640×640 for standard creative. These technical limits are not a strategy. The message should select the intended need, give a reason to visit and avoid claims that cannot be demonstrated.
Prepare a small number of variants that differ meaningfully: one centred on the problem, one on the outcome and one on mechanism or evidence. Changing one adjective is not a creative test. Imagery should represent the service, product or real context rather than an unrelated stock-like scene.
Review policies for restricted industries, claims, copyright, personal data and the destination. An ad preview confirms presentation, not final serving eligibility.
Exit condition: every variant has a distinct angle, a supported claim and a coherent destination.
Phase 9: build the campaign without hierarchy mistakes
The account, campaign, ad group and ad have separate states. An active child cannot deliver when its parent is paused, and an active campaign cannot deliver when the ad is rejected. Before publication, save a configuration record containing IDs, names, objective, budget, schedule, geography, platforms, event and URL.
Use a naming convention that remains understandable months later: country, offer, objective, audience, period and variant. Add consistent tracking parameters. Dynamic values such as {campaign_id}, {ad_id} and {oppref} can support diagnosis, but analytics and CRM naming should be decided first.

Exit condition: a second person can reconstruct the setup from the record and confirm that active objects form the same campaign.
Phase 10: final pre-launch test
Run the final control after saving the configuration rather than from memory:
- confirm that the entity, brand and payment method are approved;
- open every ad and check copy, image and URL;
- test the destination on iOS, Android and desktop;
- submit a test form or order and confirm deduplication;
- confirm the active primary event;
- review geography, language, platforms and exclusions;
- confirm budget, schedule and time zone;
- capture the settings and record launch time;
- name the person who will monitor the first hours.
The activation button is not the end of the process. It starts monitoring. A campaign can be active without receiving impressions, and an empty serving-issues list is not a promise that impressions will arrive.
The first 72 hours: what to check and what not to change
In the first hours, the review is technical: states, approval, impressions, spend, destination access and event receipt. If delivery is absent, diagnose from top to bottom: account, campaign, ad group, ad, schedule, budget, targeting and eligibility. Do not change five settings together merely to force impressions.
After traffic begins, inspect session and lead quality. Do not reach a definitive commercial conclusion after a handful of clicks. Conversions can arrive later and recent reporting can mature. Maintain a change log with date, reason and expected outcome.
| Moment | Priority check | Prudent action |
|---|---|---|
| First 2 hours | Status, approval, URL and impressions | Correct only confirmed blockers |
| First day | Spend, clicks, events and errors | Do not judge efficiency on insufficient volume |
| 48–72 hours | Traffic quality and first outcomes | Investigate anomalies before optimizing |
| After the minimum window | Valid CPA, net value and qualification rate | Compare with the business threshold and choose the next test |
When to optimize and when to stop
Optimization is meaningful when enough signal exists for a comparison. Change one dominant variable: message, audience, destination, offer or strategy. If tracking is broken, pause and repair it. If the ad attracts unsuitable enquiries, do not try to protect a cheap raw-lead CPA; change the message that filters intent.
Stop immediately if the landing page is unavailable, payment is uncontrolled, data is transmitted incorrectly, materials infringe rights or conversions are heavily duplicated. A campaign can be paused for analysis when budget is consumed without a relevant signal, but the decision should reflect realistic volume and the sales cycle.
Condensed launch record
| Area | Required evidence | Owner |
|---|---|---|
| Account | Owner, roles, country, currency and time zone confirmed | Client |
| Billing | Valid method, limits and financial alert | Finance |
| Offer | Promise, audience and outcome approved | Marketing + sales |
| Landing page | Mobile/desktop test and completed action | Web |
| Measurement | One event found in the platform and CRM | Analytics/technical |
| Creative | Variants, rights and policies checked | Marketing |
| Launch | Settings capture, change log and named monitor | Campaign manager |
What belongs in the campaign record
After launch, the configuration should not live only inside the account. Retain the approved brief, copy and images, evidence of rights, targeting matrix, UTM convention, conversion definition, test results, settings capture and change log. Keep the versions of the landing page as well, because a later page edit can explain a variation the advertising platform cannot see.
The record should be readable by the client and another specialist without an oral explanation. It protects continuity when a collaborator changes and makes audits faster. At the end of the pilot, add the decision, known data limitations and the hypothesis for the next stage. The second campaign can then start from accumulated knowledge rather than a copy of the first.
From checklist to an evaluable test
The checklist's value is not the number of ticks; it is the evidence left behind by every one. If the test succeeds, the company knows what it can expand. If it does not, the team can separate a weak offer from a delivery, measurement or landing-page fault.
For businesses that want implementation and monitoring, Web Hat's ChatGPT Ads campaign service can cover account review, campaign structure, creative, tracking, launch control and reporting connected to commercial results. Media budget remains separate and is activated after the controls pass.
Official sources checked
- ChatGPT Ads account setup and team roles
- Ads Manager availability by country
- Billing, thresholds and payments
- Campaign Management: creative, states and tracking
- Bidding and Budgets: compatibility and limits
- Campaign Targeting: geography, context and platforms
- Custom Audiences: thresholds and operations
- Conversion Tracking: events and deduplication
- Troubleshooting: diagnosing delivery
- OpenAI Advertising Policies
This checklist was updated on September 16, 2026. The interface and access conditions can evolve; confirm current documentation and account options before launch.