Targeting, creative & landing pages

ChatGPT ads landing page: blueprints, tracking and a review checklist

Build a ChatGPT ads landing page that converts and passes review: message match, oppref and UTM handling, OAI-AdsBot access, blueprints and a checklist.

Editorial illustration: a person opens a shallow storage cabinet in a narrow hallway.

A good ChatGPT ads landing page picks up exactly where the conversation and the ad left off. It repeats the promise in the ad’s title and body, answers the question the visitor was just discussing, and offers one clear next step. Technically, it must keep the oppref click reference and your UTM parameters intact, and let OpenAI’s review crawler, OAI-AdsBot, load it.

The landing page matters more here than in most channels. OpenAI uses it as one of the signals for choosing which ad to show, and in the EEA and Switzerland, where ads are matched on context alone, it carries even more weight. Below: what a click arrives with, how to structure the page for different business types, measurement, a checklist and the usual reasons pages fail.

What arrives with a ChatGPT ad click

Someone who clicks a ChatGPT ad has usually just described their situation in detail: their budget, constraints, location and what they’ve already ruled out. Your page doesn’t receive that conversation. It receives a URL. Plan for both: the visitor is further along than a typical search click, but your page knows nothing beyond the parameters.

Arrives with the click What it is What to do
oppref OpenAI’s click reference, appended to the landing URL Never strip it. The OpenAI Pixel stores it in a first-party cookie for conversion matching
Static UTM parameters Values you set on the ad, kept on every click Use one convention, such as OpenAI’s example utm_source=openai&utm_medium=paid
Macro values {campaign_id}, {ad_id} and {oppref} filled in through query_string_template Let them pass through redirects untouched
Referrer header Not documented Don’t rely on it for attribution. Use UTMs and oppref
The conversation itself Not passed Write the page for the situation your ad group targets

Don’t lose the parameters

Tracking often breaks on your own site rather than on OpenAI’s side. Typical causes:

  • Redirects that drop the query string, such as http to https, www to non-www, a missing trailing slash, or a language redirect.
  • Single-page apps that rewrite the URL on load and lose the query string before analytics or the Pixel read it. Read parameters on first load, or make sure the router keeps them.
  • Consent banners or “clean URL” scripts that remove unknown parameters.
  • Very long URLs. The full destination, parameters included, must stay within 2,048 characters.

Test with a real tagged URL. Paste it into a private window, follow every redirect and confirm that oppref and every utm_ value are still in the address bar on the final page. The UTM tracking guide covers naming and level precedence, and the free UTM builder builds the template with OpenAI’s macros and checks the length.

Let OAI-AdsBot in, and expect it in your analytics

Ads are reviewed, and the reviewer includes a crawler. OpenAI’s crawler guidance for advertisers asks you to allow OAI-AdsBot. A page that works in your browser can still block it through:

  • bot protection or a web application firewall that challenges unknown agents
  • robots.txt rules that disallow it
  • geo-blocking or a country selector that stops the page from loading
  • login walls, age gates or cookie walls in front of the content

OAI-AdsBot visits your landing pages with the tracking parameters attached. Those visits look like paid sessions in analytics but aren’t billed clicks. Filter them by user agent so they don’t distort your conversion rate in the first days.

Ad review and search indexing are separate questions. Allowing OAI-AdsBot doesn’t make a page rank, and a noindex campaign page can still be a valid ad destination.

Message match: from title and body to the first screen

An ad has a title of 3–50 characters and body copy of up to 100 characters. That leaves room for one promise and one detail. The first screen of the landing page should confirm both within a few seconds.

Ad element Example (fictional) First screen must show
Title Office cleaning for small teams in Malmö A headline with the same service and place
Body Weekly or fortnightly. Tell us your office size for a fixed quote. The schedule options and a short quote form
Image Cleaner in a small open-plan office A matching photo, not a stock skyline
Advertiser name and favicon Your brand The same logo and name in the header

If the ad says “fixed quote”, the page can’t open with “Contact us for more information”. If the ad names a city, the page must show that you serve it. Build your ad groups around situations (see what context hints are), then give each situation a page, or a section anchor, that answers it. The annotated ad examples show title, body and destination working together.

Blueprints by business type

These blueprints are starting points, not proven templates. Reorder them to fit what your visitors ask.

Local service (cleaning, trades, repairs)

  1. Hero: service + area in the headline, one sentence on how it works, the main action (request a quote or book a visit).
  2. Service area: list of towns or a postcode checker.
  3. What’s included and what isn’t: scope, exclusions, how pricing works.
  4. Process: 3–4 steps from request to completed job.
  5. Proof: real photos of your work, reviews you have permission to use, certifications you actually hold.
  6. FAQ: lead time, access, cancellation.
  7. Repeat the action with a short form.

Webshop product or category

  1. Hero: product photo, name, price, stock status, add-to-cart.
  2. Variants: sizes, colours, dimensions, with the variant from the ad preselected.
  3. Delivery and returns: cost, time, return window, close to the button.
  4. Details: materials, specifications, care.
  5. Use-case images after the real product shots, not instead of them.
  6. Reviews from real buyers.
  7. Related items and a sticky add-to-cart on mobile.

For catalogue campaigns, also see the product feed guide and the ecommerce features.

B2B service or software

  1. Hero: who it’s for, the job it does, the action (book a demo, start a trial, request a sample).
  2. The workflow: screenshots of the real product, labelled when illustrative.
  3. Fit: integrations, team size, requirements.
  4. Pricing or a clear explanation of how pricing works.
  5. Proof: named customers only with permission.
  6. Objections: migration, security, contract length.
  7. Short form or booking calendar.

Booking business (salons, restaurants, experiences, courses)

  1. Hero: what, where, price from, “Check availability”.
  2. Live availability or a booking widget above the fold on mobile.
  3. What to expect: duration, what’s included, who it suits.
  4. Location and access: map, parking, opening hours.
  5. Policies: cancellation, rescheduling, group bookings.
  6. Reviews and photos.

Speed, mobile and layout

Ads run on Android and iOS apps, mobile web and desktop web. Four of those five platforms are on a phone, so design for the small screen first.

  • Keep the main action visible without scrolling on a typical phone.
  • Set image dimensions so nothing jumps as the page loads. A form that moves just before a tap loses the tap.
  • Compress images and defer scripts the first screen doesn’t need.
  • Use readable type and tap targets that work for a thumb.
  • Click your own tagged URL from the ChatGPT app on both iOS and Android, and test forms and payment in whatever browser view opens.

Trust, claims and ad policy

Every claim in the ad and on the page should be something you can back up if asked. Put the evidence next to the claim:

  • “Fixed price” next to the price, or the method for calculating it.
  • “Delivered in 2 days” next to the delivery terms and the regions it applies to.
  • “Rated 4.8” only with a link to the real review source.
  • No invented logos, case studies, awards or countdown timers.

Check the category, too. OpenAI’s ad policies prohibit health, financial and legal services outside the US. They always prohibit adult and dating, alcohol and tobacco, gambling, political content, recreational drugs, and individual job or housing listings. A landing page that drifts into a banned category, such as a beauty salon page selling medical treatments, can sink an otherwise allowed ad.

Forms, booking and measurement events

Ask only for what you need to handle the request. A quote form might need an email, postcode and a short description. It shouldn’t require creating an account. Show a clear confirmation that says what happens next and when.

Then measure the outcome with OpenAI’s standard events. Install the OpenAI Pixel, and add the Conversions API when you can send events from your server or CRM. Give the browser and server event the same event ID so they’re deduplicated.

Page type Main event Supporting events
Quote or contact form lead_created page_viewed
Booking flow appointment_scheduled page_viewed
Webshop order_created contents_viewed, items_added, checkout_started
Signup or account registration_completed page_viewed
Subscription or trial subscription_created, trial_started page_viewed

Conversion-optimized campaigns support standard events only, so choose the main goal from this list rather than custom. The default attribution windows are 30 days after click and 1 day after view. If you’re still choosing a budget, the cost calculator shows how your conversion assumptions translate into cost per lead or order.

Landing page checklist

Run this against the exact destination URL of each ad before you submit it.

Check Pass when
Message match Headline repeats the ad’s offer, place and condition
One main action One primary button or form above the fold on mobile
Parameters kept oppref and all utm_ values survive every redirect and SPA load
URL length Full URL with parameters is 2,048 characters or less
Crawler access OAI-AdsBot isn’t blocked by robots.txt, firewall, geo or login walls
Category Offer is in an allowed category for the target country
Claims Every claim has evidence on the page
Speed and layout Fast on mobile data, no layout shift around the action
Form or checkout Test submission arrives and confirmation shows
Events Pixel fires the right standard event; CAPI deduplicated by event ID
Analytics hygiene Crawler visits filtered; UTM convention matches other campaigns
Ownership A named person handles the leads, bookings or orders

The broader pre-flight checklist covers campaign settings as well.

Common reasons a landing page fails review or performance

  • The crawler can’t load the page because of bot protection, a geo block or a login.
  • Category mismatch: the ad is allowed, but the page sells something prohibited.
  • Mismatch between ad and page: a different price, product or area than the ad promised.
  • Broken or redirecting URL: the destination 404s, loops, or lands on a homepage.
  • Unsupported claims: superlatives, guarantees or ratings without evidence.
  • Tracking lost: conversions don’t appear because oppref was stripped. The campaign looks like it failed when it actually worked.

Frequently asked questions

What makes a good landing page for ChatGPT ads?

It confirms the ad’s promise in the first screen, answers the specific situation the ad group targets and has one clear action. Technically, it keeps oppref and UTM parameters, loads for OAI-AdsBot and fires a standard conversion event.

Can I use my homepage as the ChatGPT ads landing page?

You can, but it’s rarely the best choice. ChatGPT users arrive with a specific need, and a homepage makes them hunt for it. A service page, product page or dedicated campaign page usually matches better and gives OpenAI a clearer signal about what you offer.

Does OAI-AdsBot need access to my landing page?

Yes. OpenAI asks advertisers to allow OAI-AdsBot so ads can be reviewed. Its visits include your tracking parameters and show up as sessions in analytics. They aren’t billed, so filter them out by user agent.

Why are my ChatGPT ads conversions not showing up?

The most common cause is the site losing oppref or the UTMs through a redirect, a single-page app or a consent script. Check that the Pixel is installed on the conversion page and fires a standard event. If you use the Conversions API, check that browser and server events share an event ID.

Do I need a separate landing page for each ad group?

Not always. One page can serve several ad groups if each situation has its own clear section. Create a new page when a situation needs different information, such as a different service, price or area. Copies that only swap a town name don’t count.

How AthillyAds helps

AthillyAds reads the landing pages you choose and builds the brand book, ad groups, context hints and copy from what the pages actually say. Pre-flight checks let you review each ad next to its destination before you publish. To test a page, run it through the free context hint generator and see which situations it supports. When you’re ready to build full campaigns, see pricing. The free plan covers one complete campaign.

Sources and scope

Working methods and examples are editorial suggestions. Check current platform requirements and available features before implementation.

Your next chapter

Put the ideas to work.

Give the free generator one of your pages and explore targeting ideas and ad drafts. No account needed.

No credit card needed · Ad spend is separate