# Changelog of Google Ads Transparency API & Scraper: Ad Library, Monitor, MCP (`akhil_rajesh/google-ads-transparency-scraper`) Actor

- **URL**: https://apify.com/akhil_rajesh/google-ads-transparency-scraper/changelog.md
- **Full Actor documentation**: https://apify.com/akhil_rajesh/google-ads-transparency-scraper.md

## Changelog

### 2026-11-10

- The README links a new Actor: Indeed Jobs MCP Server & API.

### 2026-11-06

- The README links a new Actor: Pinterest Trends Scraper & API.

### 2026-11-04

- The README links a new Actor: Google Trends Scraper & API.

### 2026-11-03

- The Apify SDK is updated from 4.0.2 to 4.2.0 (apify-client 3.4.0 and crawlee 1.11.0 stay). Runs return the same data. A run still stops exactly at your maximum cost per run and says so: SDK 4.2.0 would let one more result through past a spent limit, and this Actor keeps the earlier behaviour, so nothing past your limit is stored or charged.
- With SDK 4.2.0, a status update that doesn't reach Apify is logged instead of stopping the run.

### 2026-11-02

#### 0.1.12 - History kept whole however a run ends; alerts on every end; stricter webhook addresses

- **Only changes, when a run is aborted or moved.** If a tracked run was aborted, or moved to another server by the
  platform, at the very moment it was saving a search's history, the two saves could overlap, and the later one wrote
  the history back without part of the earlier one. In a run that had already been restarted once, the ads delivered
  before the restart could drop out of the history, and the next scheduled run reported them (and charged for them)
  a second time, as new or stopped ads. The saves now take turns: the abort's save waits for the search's own and adds
  to it, so nothing a run delivered is reported again.
- **Only changes, however a run ends.** Every ad a tracked run stored now goes into the history, also when the run
  ended on an error or a dataset failure, or was restarted by the platform and then aborted before it got back to a
  search, or couldn't read a search again after the restart (the Transparency Center down). Before, those ads stayed
  out of the history, and the next scheduled run reported them (and charged for them) a second time. The same goes
  for the removed-ads feed: the removals a run stored before such an end are no longer returned again.
- **Only changes, when an abort comes as ad details load.** A run aborted while the last ad details its Ad details
  budget allowed were loading went on to store the ads read with them after the abort had saved the history,
  and left them out of it: the next run reported (and charged) them again. The run now saves the history
  again as it ends.
- **Alerts on every end.** A run that stored changes and then failed (an error, the dataset refusing to store more)
  or was aborted now posts them to the webhook, and its status says so: the next run won't report those changes
  again, so it wouldn't post them either. An aborted run starts no new message after 15 seconds (a gracefully aborted
  run has 30 in all), tries each message once, and doesn't wait after a refusal; what it couldn't post stays in the
  dataset, and the status says how many.
- **Alerts when a history doesn't answer.** When a search's history couldn't be read, the run no longer posts the
  "alerts are set up" message (it isn't a first run) and doesn't say there were no changes; it says that Only changes
  couldn't be applied there, as before.
- **Alert webhook URLs.** A webhook URL that writes a private address in a short or numeric form, such as
  `https://127.1/`, `https://0x7f.1/` or `https://2130706433/` (all of them 127.0.0.1 to an HTTP client), is now
  refused like `https://127.0.0.1/`. Public addresses written that way, such as `https://134744072/` (8.8.8.8), are
  still accepted.
- Library versions are fixed: apify-client 3.4.0 and crawlee 1.11.0 next to the Apify SDK 4.0.2, so a rebuild can't bring in versions the tests haven't run on.
- The README links two new Actors: YouTube Channel Scraper and Contact Details Scraper.
