Monitor a competitor's new Bing ads
Schedule this task to get only the Bing ads a competitor started since the last run. The first run returns ads up to your maximum, in the order Microsoft serves them, and remembers the rest for free; later runs return only ads not seen before. In our runs on 12 November 2026 the first run saved 3 ads and the next run saved 0, as nothing was new.
Input
Output fields
Sign up on Apify or log in
The Microsoft Ads Library Scraper: Bing Ads, EU DSA Repository Actor is ready to run with the inputs already set for "Monitor a competitor's new Bing ads". Sign up or log in and you'll land in Apify Console with a copy of this exact task.
Start the "Monitor a competitor's new Bing ads" task
The Microsoft Ads Library Scraper: Bing Ads, EU DSA Repository Actor will start running based on the input automatically. You can also change all the input fields, like advertisers, only ads not returned in earlier runs, and more, to match your specific use case.
Receive the "Monitor a competitor's new Bing ads" output
Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as advertiser, headline, description, and more.
Integrate into your workflow
The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also run the "Monitor a competitor's new Bing ads" task via API.

The watch named in the task remembers every ad it has seen for that advertiser. Each run reads the list until it has returned your maximum of new ads, otherwise to its end, and charges only for unseen ads. Run one watch at a time.
Microsoft lists ads in no fixed order, so each run reads the whole list at about one page every 8 seconds: our first run on an advertiser with many ads took about 8 minutes.
Yes. Call fetchwright/microsoft-ads-library-scraper through the Apify API or the Apify MCP server with this task's input. Rows come back as JSON, and the run summary says what was read and charged.