Skip to content

Send conversions to ChatGPT Ads

KonversAI can send a conversion to ChatGPT Ads every time a visitor who came from a ChatGPT ad verifies their contact details, submits a form, or books an appointment in the chat. ChatGPT Ads then counts the conversion for the ad that brought the visitor, and can optimise bids toward it.

You set this up on the Conversion tracking screen in the KonversAI console, under Settings. You connect ChatGPT Ads once under Where signals are sent, then choose in the table What to send where which KonversAI event ChatGPT Ads records as which conversion.

You need a role with permission to view and change workspace settings, and conversion tracking must be switched on for your workspace. Contact KonversAI support to switch it on.

Conversion tracking is switched off for every workspace until you ask for it. The Conversion tracking item does not appear under Settings until KonversAI enables it. ChatGPT Ads can also be enabled separately for each workspace. On the Conversion tracking screen, ChatGPT Ads shows as not enabled for this workspace or coming soon until you can connect it. Contact support to have it switched on.

You need two values from ChatGPT Ads Manager:

  • The Pixel ID. In Ads Manager, open Conversions, then your pixel.
  • A Conversions API key. In Ads Manager, open Conversions, then API keys, and create one.

ChatGPT Ads needs the address of a page for every conversion. KonversAI sends the page the visitor arrived on when it knows it. For the other conversions, give KonversAI your website’s address in Website address, or those conversions are not sent.

The chat widget on your website must collect ad click IDs. In the KonversAI console, open Settings, then Widget, then the chat tab, expand Conversion tracking and tick Capture ad click IDs. KonversAI reads click IDs and cookies only from visitors who granted marketing consent.

  1. In the KonversAI console, open Settings, then Conversion tracking.
  2. Under Where signals are sent, select Connect ChatGPT Ads.
  3. In Name, type a label for this connection, such as the name of your website.
  4. In Pixel ID, paste the pixel ID from Ads Manager.
  5. In Website address, type the full address of your website, such as https://www.example.com/. This field is optional, but without it KonversAI cannot send a conversion when it does not know the visitor’s page.
  6. In Conversions API key, paste the API key from Ads Manager.
  7. In Currency, type the three-letter currency code for conversion values, such as NOK.
  8. Select Save. The connection appears as a card with the status Not tested, and it is switched off.
  9. Select Test. KonversAI checks a sample conversion with ChatGPT Ads without recording it, and shows the result on the card.
  10. In What to send where, find the column for your ChatGPT Ads connection. KonversAI has already filled in the lead rows: Contact verified and Lead submitted as Lead created, and Appointment booked as Appointment scheduled, each with the placeholder value 1.
  11. Change or clear any cell. Pick a standard type from the list, pick Custom event and type a name, or pick Not sent. A custom name uses up to 64 lowercase letters, digits, hyphens or underscores, and cannot be the name of a built-in ChatGPT Ads type such as lead_created. KonversAI lowercases the name as you type.
  12. Type what each conversion is worth to you in the value field under the type. KonversAI reports the value in the currency of the connection.
  13. On the connection card, select Switch on. KonversAI sends nothing to ChatGPT Ads until you do this.

Which KonversAI events can I send to ChatGPT Ads?

Section titled “Which KonversAI events can I send to ChatGPT Ads?”

The table What to send where on the Conversion tracking screen has one row for each event. Each event is sent at most once per conversation.

  • Conversation started: a visitor starts a chat.
  • Contact verified: a visitor verifies an email address or phone number with a code.
  • Lead submitted: a form in the chat is completed.
  • Appointment booked: a booking is confirmed. A tentative hold does not count.
  • Handed over to a person: the conversation is handed to a human agent.

Each row shows how often the event was recorded in the last 30 days. KonversAI counts an event only while something receives it, so a row that nothing receives shows 0.

Bid on the lead events: Contact verified, Lead submitted and Appointment booked. Treat Conversation started and Handed over to a person as low intent. Bidding on them trains ChatGPT Ads to find visitors who chat, not visitors who become customers. If you send one of them, the cell says: “Bidding on this event trains the platform toward low-intent clicks.” For the same reason, ChatGPT Ads never offers Lead created for Conversation started.

Why is the conversion value 1, and should I change it?

Section titled “Why is the conversion value 1, and should I change it?”

KonversAI fills each new lead row with the value 1, and marks it: “Placeholder: set what this is worth to you.” ChatGPT Ads bids on value, so it treats every conversion as worth 1 until you change it. Type what a lead or a booking is worth to your business in the value field of the cell in What to send where. To keep 1 as the real value, type 1 again.

Will ChatGPT Ads count the same lead twice?

Section titled “Will ChatGPT Ads count the same lead twice?”

It can. When two or more lead rows go to one ChatGPT Ads connection, the column warns: “More than one lead event goes here.” A visitor who verifies an email address and then submits a form sends two conversions. Make only one of them a primary conversion in ChatGPT Ads. If the ChatGPT Ads pixel on your own website also records the same lead, ChatGPT Ads counts it again: record each lead in one place only. Every ad platform you connect also claims the same lead for its own ad, so the totals across platforms add up to more leads than you had.

Why are fewer conversions showing in ChatGPT Ads than in KonversAI?

Section titled “Why are fewer conversions showing in ChatGPT Ads than in KonversAI?”

KonversAI sends a conversion to ChatGPT Ads only when the visitor granted marketing consent on your website, and only with something ChatGPT Ads can match the visitor on. That is the click ID from a ChatGPT ad, the ChatGPT Ads pixel cookie on your website, or a verified email address or phone number, hashed before it leaves KonversAI. ChatGPT Ads also refuses conversions older than 7 days. On the connection card, select Show recent deliveries. Each conversion that was not sent says why, such as No marketing consent. No page address known for this conversation means KonversAI did not know the visitor’s page and the connection has no Website address: select Edit on the card and add one.

KonversAI sends the conversion type, the time, the value and currency, the address of the page, and the identifiers above. Email addresses and phone numbers are hashed. Nothing is sent for a visitor who did not grant marketing consent. Marketing consent alone does not allow ad personalisation: KonversAI counts ad personalisation as allowed only when your website says so explicitly, and otherwise tells ChatGPT Ads that the visitor opted out of it.

What does “Needs reconnecting” mean on my ChatGPT Ads connection?

Section titled “What does “Needs reconnecting” mean on my ChatGPT Ads connection?”

ChatGPT Ads rejected the stored Conversions API key. KonversAI sends nothing until you replace the key, and conversions in the meantime are not sent later. Under Show recent deliveries, those conversions say Connection needs to be reconnected. Create a new API key in Ads Manager, select Replace token on the connection card, paste the key into Conversions API key, and select Save.

To stop one event, pick Not sent in its cell in What to send where. To stop everything, select Switch off on the ChatGPT Ads connection card.

Last reviewed . Tell us when a step no longer matches the product.