Google Ads Scraper avatar
Google Ads Scraper

Pricing

$30.00/month + usage

Go to Store
Google Ads Scraper

Google Ads Scraper

Developed by

Gustavo Silva (Coherent Paradox)

Gustavo Silva (Coherent Paradox)

Maintained by Community

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.3 (10)

Pricing

$30.00/month + usage

83

Total users

1.8K

Monthly users

255

Runs succeeded

>99%

Issues response

14 hours

Last modified

2 days ago

TM

Crawling gives many "TypeError: Invalid URL" errors

Closed

tan_mat opened this issue
a year ago

https://console.apify.com/organization/jecGokyjkaYwjpEr6/actors/runs/9Y13D2BSjPT95l5ew#log

There are a lot of:

2024-05-28T14:01:02.300Z WARN CheerioCrawler: Reclaiming failed request back to the list or queue. TypeError: Invalid URL 2024-05-28T14:01:02.301Z at new URL (node:internal/url:797:36) 2024-05-28T14:01:02.302Z at tryBypassGoogleAdServicesUrl (file:///usr/src/app/dist/src/utils/url.js:86:23) 2024-05-28T14:01:02.303Z at scrapeRenderHtml (file:///usr/src/app/dist/src/routes/creative.js:178:26) 2024-05-28T14:01:02.304Z at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 2024-05-28T14:01:02.305Z at async Promise.all (index 1) 2024-05-28T14:01:02.306Z at async file:///usr/src/app/dist/src/routes/creative.js:383:24 2024-05-28T14:01:02.307Z at async wrap (/usr/src/app/node_modules/@apify/timeout/cjs/index.cjs:54:21) {"id":"yBr4fkZkZsFJIUs","url":"https://adstransparency.google.com/advertiser/AR05544152143130263553/creative/CR08608777850478133249","retryCount":4}

In the logs; this increases a lot the cost of crawling - since it continues until the actor timeouts.

My question: This URL does not seem to be bad: https://adstransparency.google.com/advertiser/AR05544152143130263553/creative/CR08608777850478133249

silva95gustavo avatar

I'm sorry, this issue has been introduced in a very recent update. It has now been fixed.