Ads in ChatGPT for service businesses: leads, appointments and trials
A clinic, an agency, a software company or a local trade has no product feed to upload, and that is fine. Ads in ChatGPT work for services through chat cards, lead conversion events and a feedback loop from your CRM or booking tool. This guide explains the setup and what Adsonomy does with it.
- Service campaigns optimise towards lead events: lead_created, appointment_scheduled, trial_started, subscription_created and registration_completed.
- Events reach OpenAI through the pixel and the Conversions API, deduplicated by event ID, with personal data hashed.
- Creative is the chat card: title 3 to 50 characters, body up to 100, image at least 640 by 640, destination reachable by OpenAI's crawler.
- Context hints, up to 2,000 per ad group, are written from your service pages, pricing and FAQ.
- Adsonomy connects HubSpot, Pipedrive, Salesforce, Calendly and Stripe so deal stages and values flow back as the optimisation signal.
- Conversion-optimised bidding and Conversions API keys are enabled per account by OpenAI.
Can a service business advertise in ChatGPT?
Yes. The OpenAI Ads platform is not limited to shops. A campaign can optimise towards lead events instead of orders, and the chat card format needs only a title, a short body, an image and a landing page. What changes for a service business is the conversion setup and the source of the targeting hints.
People ask ChatGPT for a physiotherapist who treats runners, an accountant for a freelancer in Rotterdam, or a tool to send invoices. Those conversations are where a service ad appears, matched by the context hints on your ad group. Read how ads in ChatGPT work for the platform mechanics; this guide covers what is specific to leads.
OpenAI publishes advertising policies that prohibit some categories and place others under additional review. Read them before planning a campaign in a regulated sector.
Which conversion events matter for leads?
Five of the platform's fourteen standard events describe a service funnel: lead_created when a form or chat produces a contact, appointment_scheduled when a booking is made, trial_started when someone activates a trial, subscription_created when a paid plan starts, and registration_completed when an account is opened. Only standard events can be set as an optimisation goal, so these are the events a campaign bids towards.
Each event needs an event ID so that the same lead sent from the browser and from the server is counted once, and a timestamp within the last seven days. A customer email or phone number in the event is normalised and hashed with SHA-256 before it is sent. The click attribution window is set by the advertiser; OpenAI's documentation uses 30 days in its example, which suits most service funnels where the booking happens days after the click.
Which event to optimise towards depends on volume. Conversion bidding needs a steady flow of the chosen event; a campaign that gets two appointments a week has too little signal, so it optimises towards lead_created and lets the CRM loop below tell the manager which leads were worth having.
How does the CRM feedback loop work?
Adsonomy connects your CRM or booking tool, reads deal stages and values, and sends the matching standard event to the Conversions API when a lead moves. A booking in Calendly becomes appointment_scheduled, a paid plan in Stripe becomes subscription_created, a deal marked qualified in HubSpot, Pipedrive or Salesforce becomes the event you mapped to that stage.
The platform itself only knows the events it receives; it reports conversions, cost per conversion and post-click conversion rate. Pipeline value stays in Adsonomy, joined to the campaign, ad group and hints that produced the lead, so the manager can see that one ad group produces cheap leads that never qualify while another produces fewer, better ones. That is the difference between optimising towards form fills and optimising towards revenue.
Attribution from ad to CRM record works through the tracking template. OpenAI lets you append a query string to landing page URLs at account, campaign, ad group or ad level, with placeholders for the campaign ID, the ad ID and a click reference. Adsonomy sets that template, captures the parameters on your website and stores them on the lead so the CRM stage change can be sent back against the right click. Events carry a timestamp within seven days, so a stage change that happens later is sent with the time of the change rather than the time of the click.
What do the ads look like for a service?
A chat card, and only a chat card. Product ads require a feed, which a service has no use for. A chat card has a title of 3 to 50 characters, a body of up to 100 characters, a JPEG, PNG or WebP image of at least 640 by 640 pixels, and a destination URL of up to 2,048 characters that OpenAI's crawler can reach.
The constraint is the body: 100 characters is one sentence. The best cards state the outcome and the proof, for example the service, the area and one concrete reassurance such as a same-week appointment or a fixed price. Every card passes review, and editing it sends it back into review, so Adsonomy's creative studio shows the card in a live preview before it goes live and lets you keep a few approved variants to rotate rather than editing the one that serves.
The destination must be a page OpenAI can crawl. Gated pages, pages behind a login and pages that require a cookie banner click before the content loads are common reasons for rejection.
Where do the context hints come from?
From your service pages, your pricing page and your FAQ. Adsonomy connects a website on WordPress, Webflow, Wix or Squarespace, or any site with a sitemap, and reads the pages that describe what you do, for whom, where and at what price. Those pages become the knowledge base from which the hints are written.
A context hint describes an intent rather than a search term. A dental practice might carry hints for a chipped front tooth before a wedding, a second opinion on a crown, or an emergency dentist open on Saturday. An accounting firm might carry hints for filing a first VAT return, or moving from a sole proprietorship to a limited company. An ad group can hold up to 2,000 of them, and the manager reviews which ones produce conversions and prunes the rest.
Because the platform reports no prompt data, the hints are the only lever you have on relevance. Writing them from real pages, real reviews and real questions from your inbox is what separates a service campaign that converts from one that just spends. In the Control edition you edit and version the hints yourself; in Autopilot the manager proposes new hints, and you set whether it may add them on its own or only suggest them, as described in the guardrails guide.
Frequently asked questions
Do I need a pixel if I have a CRM?
You need both. The pixel captures the browser reference on the landing page and the first events such as a form view. The CRM connection sends the lead, appointment, trial or subscription event from the server once it exists. The event ID and the browser reference tie the two together so the platform counts each lead once.
What if my leads take weeks to close?
Optimise towards an earlier standard event that happens often, usually lead_created or appointment_scheduled, and let the CRM feedback loop report which of those leads became customers. Events must be sent with a timestamp within seven days, so Adsonomy sends each stage change as it happens rather than waiting for the deal to close.
Can I run a service campaign without a CRM?
Yes. Adsonomy captures form submissions and bookings on the website directly and sends lead_created. You lose the qualification signal, so the manager optimises towards lead volume and cost per lead until a CRM or booking tool is connected.
Adsonomy runs ads inside ChatGPT for shops and service businesses. Control edition: you run it with rules. Autopilot: the AI manager runs it inside your guardrails. Launching 1 October 2026.
Join the waitlist