Docs

Ads

Search ads read from the Rank Tracker's stored results, competitors' ads from Google's Ads Transparency Center, ChatGPT ads recorded by people on your team, the check run and the Chrome extension, and what each figure means.

What Ads shows

Ads shows who pays to appear for the searches and prompts a client cares about. It has three pages: Search ads, which reads Google ads from the results pages the Rank Tracker has already stored; Ad library, which lists the Google Search ads that Google's Ads Transparency Center shows for the client's site and its competitors; and ChatGPT ads, which lists the ads people on your team saw in their own ChatGPT conversations. Open a client and choose Ads. Paid placements are a separate channel. They never count toward rankings or AI visibility and are never added to it. Where a page shows paid and earned side by side, they stay two figures, each with its own sample.

Search ads

Search ads needs the Rank Tracker. It reads the results pages the Rank Tracker has already stored for the client's tracked keywords: no extra search and no extra cost, however often you open it. For each ad it shows the advertiser, the headline, the description, the display URL and the sitelinks. For a Google Shopping ad block it shows each product with its merchant, price, regular price and rating. Ads stored before sitelinks and product details were added show without them. Choose a window of 7, 28 or 90 days (28 is the default) and, once the client's brand terms are set, filter by branded or non-branded keywords. An advertiser counts once per check, however many ads it shows on that results page. Only the text Google showed is stored. A paid-click redirect link is never kept. An ad that none of our checks caught cannot appear: a weekly check is one moment of an auction that changes all day.

Ad library

Ad library needs the Rank Tracker too. It shows which Google Search ads Google lists in its Ads Transparency Center for the client's own site and for each competitor domain the client tracks in Rankings (at most 10 sites per client), in each country its Rankings keywords name (at most 8, the one with the most keywords first; the page shows one country at a time): how many ads each runs, by format, which are new since the last lookup, which have stopped, how long the longest have run, and the advertiser's name as Google verifies it. Every ad links to its own page on Google. A country that DataForSEO's ads search does not offer is skipped and named on the page; it is neither looked up nor counted. No weekly lookup runs until someone switches it on. "Watch competitors' ads" is off for every client; switching it on for a client lets a weekly lookup run for it, and the page records who switched it on and when. "Check now" looks the sites up once, on your click (not again within 10 minutes of the last lookup that was read; the page says when it can run again). Both are billed: DataForSEO charges about $0.0006 per lookup of one site in one country, and on the Rank Tracker's budget we charge twice that, the same as every Rank Tracker search. The page says what it will cost before you switch it on, a lookup the budget cannot cover is not sent, and a lookup that fails is not charged to the budget. With your own DataForSEO connection, DataForSEO bills your own account. Each workspace can start up to 10,000 site lookups a month, Check now and the weekly lookup together (every Check now click counts too); each site counts once per country. In a month with five weekly runs that is at most 200 clients of ten sites in one country, or 25 in eight countries, watched weekly and never clicked. When the month's lookups are used, Check now says so and the weekly lookup waits for the next month; nothing is sent in the meantime. An ad counts as running when Google lists it as shown in the 7 days before the lookup. Every count has its day: the last lookup named at the top of the page, or, for a site last read on an earlier day, that day ("12 on 10 Nov"). A lookup lists at most 40 ads per site: when it reaches 40 the list is cut there, and the count says "or more" with "list cut at 40" ("21 or more" when 21 of the 40 listed ran), because ads past the cut may be running too. It never gives a total. New means running now and not in that site's previous lookup; stopped means running at the previous lookup and not now. Both appear from a site's second lookup, so the first one flags nothing as new. A lookup that failed or was never read shows as not checked, never as 0. No ad images are loaded or stored; we keep the advertiser's name, each ad's id, format, first and last shown dates and the link to Google's page. Advertiser names are third-party text and shown as text only. Paid placements are never added to AI visibility.

ChatGPT ads and the check run

ChatGPT shows ads only to signed-in people on its Free or Go plan, and not every conversation gets one. CrunchJunkie cannot ask ChatGPT for you, so people on your team ask the client's tracked prompts in their own ChatGPT accounts and record what they see. OpenAI is not involved: CrunchJunkie never contacts it for this. Open a client, choose Ads, then ChatGPT ads and the Check run tab. It lists the prompts still to check this week. For each one, open ChatGPT in a new chat, send the prompt, read the answer and ask the suggested follow-up, because ChatGPT often places its ad after the second question. Then record the ads: who advertised, the headline and text, ChatGPT's line above the ad and under which answer. If no ad appeared, save that too: it counts as a check with no ad. Pick your plan, Free or Go, for each check. The country comes from your connection, not from the language of the chat, because ChatGPT chooses ads by where the reader is. Nothing runs on its own: you send every prompt. Please do not click the ads, because a click costs the advertiser money. Check the buying prompts every week, ideally with two people on different days. Viewers and client-only seats can read the results but cannot record checks. You can delete a check you recorded by mistake, and so can an owner or admin.

The Chrome extension

The optional extension "CrunchJunkie ChatGPT checks" (Chrome 116 or newer) saves typing. Install it from the Chrome Web Store, open the Check run and click Connect the extension. Get the extension. After that, Open ChatGPT opens a new ChatGPT tab for one check with the prompt already in the message box. You still press send, ask the follow-up and confirm. A panel lists the ads it found under each answer and which tracked brands the answers named. Nothing is recorded until you click "Looks right · save". The extension reads only the ChatGPT tab it opened for a check. There it puts the prompt into ChatGPT's message box (you send it) and reads the conversation inside your browser, to find the ad cards and the tracked brand names the answers mention. Only the ads (with ChatGPT's line above each) and the brand names are saved, when you click save. It never sends a message and never clicks anything in ChatGPT. Apart from the line above an ad, the text of the answers never leaves your browser and CrunchJunkie never stores it. It asks for access to chatgpt.com and app.crunchjunkie.io only, plus the browser's own extension storage (where it keeps its connection and the check in progress) and the clipboard. Connecting makes a token for you in this workspace. CrunchJunkie stores only a hash of it, with the browser's name, and it stops working after 180 days. Click Disconnect in the extension to revoke it sooner. A person who is removed from the workspace, becomes a viewer, or whose workspace has the Ads area off loses access at once. If ChatGPT changes its page and the extension stops finding ads, record the check by hand.

In reports and the MCP connector

Search ads and ChatGPT ads are also report sources: add their widgets to a client's report and they show the same counts, each with its window and its sample. A report never sends a search and never asks anyone to check anything; a widget with no check to count says so and never shows a 0. Assistants connected through the MCP connector read the same figures with `get_search_ads` and `get_chatgpt_ads`, from stored data and at no cost. The Ad library is on its page only.

Reading the figures

ChatGPT ads shows counts as k of n conversations: n is the conversations people recorded in the window, k the ones that matched. A percentage appears only from 20 conversations up. Below that you see the counts and a Small sample label. These figures are a sample of what people saw, in their country, on their plan, on the day. They are not every ad that ran and they are not impression share, which only an advertiser's own account has. In Search ads a share says how often an advertiser turned up in our checks. No ad means a person checked and saw none; a prompt nobody checked is not counted. Named in the answer is what the same conversation's answer said about the advertiser, never the result of an AI visibility scan. Paid figures are never added to AI visibility, and a ChatGPT ad is never counted as a mention.

What is stored

For Search ads, the public ad text from the stored results pages. For a ChatGPT check, the prompt, whether the follow-up was asked, your plan, the country, who recorded it, how (typed in or by the extension), the ads and the tracked brand names the answers named. The IP address is not stored with a check and the text of the answers is never stored. A check and its ads are kept until you delete them or the client or workspace is deleted. Ad library lookups (the sites, the advertiser's name, each ad's id, format, dates and link, never an image) are deleted 12 months after the lookup; the weekly switch with who set it is kept with the client and deleted with it. A user id in either is removed when that person's account is erased. The privacy policy describes this in its Ads section.