Google Ads Scraper
Pricing
$30.00/month + usage
Google Ads Scraper
Extract text, image and video ads from Google Ads, scraped from the ad library provided by Google Ads Transparency Center. Gain access to ad details, ad copy, locations, and more. Dive deeper into the Google Ads Transparency Center for a competitive edge.
4.2 (10)
Pricing
$30.00/month + usage
67
Total users
1.5k
Monthly users
200
Runs succeeded
>99%
Issue response
18 hours
Last modified
a day ago
"Incomplete Results from Google Ads Transparency Scraper (Partial Ads Retrieved)"v
Closed
I’m currently running a scraping task to extract data from the Google Ads Transparency Center using a JSON configuration that includes the required headers (cookie and x-framework-xsrf-token) and properly formatted URLs with start-date and end-date.
Everything works correctly except for one critical issue:
When searching for a specific advertiser on a given date range, the Google Ads Transparency UI shows, for example, 120 total ads, but the scraper only returns a partial result set — often something like 71 out of 120.
This suggests that:
Either not all pages of data are being crawled,
Or there’s an issue with pagination handling / lazy loading in the scraper logic.
I'm already using the exact JSON format recommended in documentation and support (see example below), and I’ve confirmed that the headers and cookies are valid during the request session.
{ "shouldDownloadAssets": false, "shouldDownloadFiles": false, "shouldDownloadPreviews": true, "startUrls": [ { "headers": { "cookie": "[cookie]", "x-framework-xsrf-token": "[token]" }, "url": "[target-url]" } ] }
Could you please advise on:
Whether this is a known limitation with the Google Ads Transparency platform?
If there’s a specific technique or workaround to ensure all ads are retrieved — including paginated results?
Whether you have an updated actor or module that correctly follows dynamic loading or API pagination on that interface?
Thank you in advance. Looking forward to your support.
Best regards
Thanks for the detailed report — I understand the issue and will need some time to troubleshoot it further. I’ll get back to you as soon as I have more information.
Hi Gustavo,
Thank you for your quick reply — we really appreciate your attention.
Just to emphasize, we’re currently working on a critical operation that depends on daily updates from the Google Ads Transparency Center. This incomplete data issue is blocking a key part of our process.
We fully understand that deeper investigation takes time, and we truly value your expertise. That said, given the urgency on our side, we’d be willing to offer a symbolic payment to support and prioritize this fix — even though our current budget is very limited.
If there’s any way we can help expedite your debugging or testing efforts, please let us know. We’d be more than happy to cooperate closely to help you solve this as fast as possible.
Looking forward to your feedback.
Best regards, Diego
Hi,
Thanks again for your message and for emphasizing the urgency.
While reviewing your report, I noticed some issues in how the scraper was handling customised input. I've since made a few improvements, and it should now return the full set of ads as expected.
Also, I noticed your task input includes session cookies, which suggests you're running the scraper in a logged-in state. Just a quick heads-up: the scraper is designed to run anonymously by default and doesn’t officially support logged-in sessions.
Here’s why:
- Accessing logged-in or age-restricted content may violate Google’s Terms of Service.
- It also poses a risk of account termination, which I want to help users avoid.
As mentioned in the FAQ section of the README:
If you notice that some ads are missing, try running a search in an incognito/private browsing window. If the missing ads are age-restricted, they won’t appear unless you’re logged in. Since the scraper runs without authentication by default, these ads won’t be included.
That said, you’re free to proceed at your own discretion by customizing the requests with your session cookies, as you’ve already done. Just keep in mind the potential risks involved.
Let me know how it goes on your end.
cintrandiego
Hi,
Thank you for the quick follow-up and for improving the scraper's handling of custom input — much appreciated.
I understand the risks involved in using session cookies and will proceed with caution. Your clarification was very helpful.
Thanks again!
Glad to hear that — and you're very welcome!
If you’re enjoying the actor, feel free to leave a star review here (no comment needed). It really helps!
I’ll go ahead and close the ticket now. Let me know if you run into anything else.
