How to Track Sponsored Placements in ChatGPT Answers

Sponsored placements inside ChatGPT answers are easy to miss because they look like part of the answer. A product card with a price and a link can be an organic recommendation or a paid unit, and the difference is the whole point. If you do not log them separately you end up treating a paid slot as a citation win, which is the wrong signal and the wrong response. This is a working method for tracking them, built on Ads Radar inside Promptwatch.

The method assumes one thing up front: there is no official ChatGPT ads API. The data comes from monitoring the real ChatGPT interface, and Ads Radar is the feature that stores what that monitoring sees. No vendor has an OpenAI partnership for this, and any tool claiming one is misrepresenting how it works.

Step 1: Build the prompt set first

Tracking ads without a prompt set produces a pile of captures with nothing to compare them to. Write 15 to 25 prompts the way a buyer would type them, not the way your category pages are titled. Include branded prompts where someone types your name, category prompts, and a few comparison prompts that name you next to a rival. Tag each prompt by intent: BRANDED, COMMERCIAL, TRANSACTIONAL, INFORMATIONAL. The intent tag is what lets you later separate a rival buying your branded demand from one buying a broad category term.

Load the prompts into Promptwatch on a plan that includes Ads Radar. The commerce reports sit on Professional at $245/mo and above, and on the self serve agency plans. Essential at $95/mo does not include them. Explore is free with 10 ChatGPT prompts if you want to see the surface first.

Step 2: Confirm the surface exists by hand

Before you trust a dashboard, run five of the prompts in ChatGPT yourself. Note which answers show a sponsored unit at all, and where the unit sits in the answer. This does two things. It calibrates your expectation of how often the surface appears in your category, and it gives you a ground truth row to compare the dashboard against. If your category almost never returns a sponsored unit, ad tracking is a metric about a surface that barely exists for you, and the prompt set is what needs to change first.

Step 3: Read the prompt view

Open Ads Radar and list the prompts whose answers contained sponsored ads. Each row has an ad count and a latest capture time. Sort by ad count. The prompts with the most captured ads are where the auction is active, and those are the ones to work first. A prompt with zero captured ads is not one to spend time on yet.

Step 4: Read the advertiser view

List advertiser root domains ordered by ad count. This is the set of brands buying into your prompt set. Find the rival you did not expect, the one who is not in your SEO competitor set but keeps showing up in the paid slot. Filter the full ad list to that one domain and read every ad they have run on your prompts. Each row has the ad creative, the advertiser name, the landing page, the source response, and the position of the ad inside that answer. Save the exact copy, not a paraphrase.

Step 5: Sort by position and intent

Two sorts matter. Sort by position in the response to see who buys the top slot, because the top sponsored unit and the third one are not the same buy. Then filter by intent. A COMMERCIAL row on a BRAND_SPECIFIC prompt is a rival buying your own demand, and that is the row to escalate. An INFORMATIONAL row on an ORGANIC prompt is a rival buying awareness, which is a different response.

Step 6: Pull the trend

Pull the top advertiser domains with daily ad counts for the last 90 days to read share of ads over time. A rival whose daily count is climbing on your branded prompts is a different problem from one whose count is flat. A competitor who held steady for a quarter and then doubled in the last month is running something new, and you cannot tell that from a single capture.

Step 7: Decide what is and is not a ticket

Not every captured ad is a ticket. A rival buying a broad category prompt you do not target is context, not work. A rival buying your branded prompt is a ticket. A rival whose ad copy contradicts your docs is a ticket. Assign an owner to each ticket and save the exact ad string, because a paraphrase is a guess and a guessed ad will not survive a client check.

What this is not

This is not bid management. ChatGPT sponsored units are not Google Ads, the auction is different, and importing a Google campaign mental model breaks here. Ads Radar is a monitoring tool for the ChatGPT surface, not a management tool for a Google one. Site: promptwatch.com.

What to do this week

Write 20 buyer prompts, branded and unbranded, tagged by intent.
Run five by hand in ChatGPT and confirm the surface exists in your category.
Load the set into Promptwatch on a plan with Ads Radar.
Pull the advertiser domain list and the 90 day share of ads trend.
Turn the rival on your branded prompt into a ticket with an owner.