LinkedIn Ad Library Change Monitor
Pricing
from $5.00 / 1,000 verified search units
LinkedIn Ad Library Change Monitor
Collect public LinkedIn Ad Library ads and monitor verified changes across complete snapshots.
Pricing
from $5.00 / 1,000 verified search units
Rating
0.0
(0)
Developer
Monkey D. Scraping
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
0
Monthly active users
6 hours ago
Last modified
Categories
Features
Share
Track competitor ads in the public LinkedIn Ad Library and see what changed between runs. Search by advertiser, payer, keyword or Ad Library URL. Each verified comparison produces a change feed alongside the collected ads and a coverage report.

What changes between runs?
- First complete run. The Actor saves the baseline for your
monitorIdand search scope. - Next complete run. Reuse the same monitor ID and search scope. The Actor compares the current results with the last complete snapshot.
- Review the change feed. Open the named dataset listed under
changesDatasetin the run manifest. It records newly observed ads, ads missing from the verified results and advertisers seen for the first time by this monitor.
A missing ad may have moved outside the monitored date window. Check the original search and coverage before interpreting its absence. An incomplete or capped run keeps the last verified baseline for the next comparison.
中文用户 / 中文用戶: 简体中文说明 · 繁體中文說明(领英广告变化监控、LinkedIn广告库监控、竞品广告监控)
At a glance
Capabilities
| Capability | Details |
|---|---|
| Data source | Public LinkedIn Ad Library, logged out |
| Search targets | Advertiser, payer, keyword, or direct Ad Library URL |
| Input | One company or a list of monitored inputs |
| State | Previous snapshot in the Actor key-value store |
| Change feed | New ads, disappeared ads, and new advertisers |
| Reference data | Observed ads with per-run coverage; named datasets accumulate observations |
| Scheduling | Designed for daily or weekly runs |
| Authentication | None required |
| AI enrichment | None; deterministic normalization and set comparison |
What this Actor does
- Tracks one company or a list of competitors in one run.
- Searches by advertiser, payer, keyword, or a direct LinkedIn Ad Library URL.
- Detects new LinkedIn ads and ads that disappeared since the previous complete run.
- Flags a new advertiser appearing in the monitored results.
- Preserves a full current snapshot for audit and historical comparison.
- Calculates active-ad count, ads first seen in the period, average observed longevity, format mix, and payer-to-advertiser mapping.
- Keeps state isolated by
monitorId, so separate competitors, users, and schedules do not share baselines.
Search phrases this Actor answers
- track competitor LinkedIn ads
- monitor LinkedIn Ad Library
- get alerts on new LinkedIn ads
- detect when competitor ads disappear
- see which companies advertise on LinkedIn
- track LinkedIn advertiser and payer activity
- compare competitor ad campaigns over time
- export LinkedIn ad change events to a dataset
Why the change feed is useful
Most ad-library scrapers return a flat dump that must be compared manually. This Actor does the set comparison for you. The first run creates a baseline and intentionally emits no new alerts. Later complete runs emit only differences, so the changes dataset is suitable for schedules, downstream automations, and daily review.
Alerts are conservative: the baseline is replaced only by a verified complete collection, so disappeared events always come from verified search results.
Event semantics
| Situation | Output |
|---|---|
First run for a new monitorId and scope | Baseline only; no change alerts |
| Complete run with an ad not in the previous snapshot | new |
| Complete run with a previous ad no longer present | disappeared |
| Advertiser never seen in this monitor's history | new-advertiser |
Result set reaches maxResults | Snapshot delivered; no change alerts |
| Search without a verified result | Previous snapshot is kept |
This Actor vs similar LinkedIn Actors
| Capability | This Actor | SolidCode LinkedIn Ads Scraper | Jaybird LinkedIn Ad Library Scraper |
|---|---|---|---|
| Primary job | Monitor changes between scheduled runs | Extract LinkedIn ads in bulk | Extract LinkedIn ads and optional details |
| Output | Change events plus full snapshot | Flat ad rows | Flat ad rows with basic/enriched modes |
| Stateful baseline | Yes, isolated by monitorId | Not the core workflow | Not the core workflow |
| Alerts | New, disappeared, new advertiser | Consumer compares results separately | Consumer compares results separately |
| Search | Advertiser, payer, keyword, direct URL | Keyword, advertiser, direct URL | Company, payer, keyword, direct URL |
| Public/no login | Yes | Yes | Yes |
The positioning is intentionally different: those Actors are optimized for extracting ad data, while this Actor is optimized for recurring monitoring and a ready-to-use change feed. Check each Actor’s Pricing tab for its effective prices.
Other Actors from the same publisher
Use these complementary Actors for a broader monitoring workflow:
| Actor | Best for | Main output |
|---|---|---|
| Google Ads Scraper — Transparency Center | A competitor's Google Search, YouTube and Shopping ads | Ads with reach by country, texts and landing pages |
| TikTok Ads Library Scraper | A brand's TikTok ads and targeting | Ads with reach, advertiser and targeting |
| Telegram Keyword Search & Channel Scraper | Public Telegram research and keyword discovery | Matching posts and channel data |
| Google Shopping Price Tracker & Seller Monitor | Product prices, offers, and seller monitoring | Changed offers and product snapshot |
Output datasets
The default dataset contains delivered ad rows (recordType: snapshot) and a run-manifest. When verified-search billing is active, it also contains verified-search evidence records. Ads are saved before their batch charge.
Start with Ads and run records to read advertiser, ad ID, text, format, source URL and collection time. Use Run coverage to inspect completeness, failed or skipped inputs and the names of the two monitor-specific datasets. These views choose columns; they do not filter record types. API consumers can use recordType to distinguish ads from diagnostics.
| Destination | Contents | How to find it |
|---|---|---|
| Default dataset | Delivered ads, run manifest and active verified-search evidence | Output → Ads and run records, or the run's default dataset ID |
| Named changes dataset | new, disappeared and new-advertiser events, run summaries and company metrics | changesDataset name in the run manifest |
| Named snapshot dataset | Delivered ad observations collected by this monitor | snapshotDataset name in the run manifest |
The named datasets accumulate history across runs. Use observedAt to select one collection; they are not overwritten with a latest-only table. The coverage field of the run manifest tells you whether a snapshot is complete. sourceUrl identifies the public search/source page used. adId is a public identifier when available, with a stable derived fallback.
State is updated only after a verified complete collection and successful output writes; otherwise the previous baseline is kept and no change alerts are emitted. The first complete collection establishes a baseline and produces no change events.
Input example
{"monitorId": "acme-competitors-weekly","advertisers": ["OpenAI", "Anthropic"],"country": "IT","dateRange": "30d","searchType": "advertiser","maxResults": 100}
Use the same monitorId and filter scope on recurring runs. Changing the scope intentionally starts a new baseline instead of creating false changes. Set maxResults above the number of results of the search (or narrow the search) to receive change events.
With automatic Apify Proxy selection, residentialFallback (default true) lets a search retry through residential IPs. Set it to false to turn this off. Explicit proxy groups, custom proxies and disabled proxies are respected.
Pricing and spending limits
The Pricing tab is the source of truth for the prices effective for your run. Current events are:
| Event | Current price | What is billed |
|---|---|---|
apify-actor-start | $0.00005 per memory unit | Automatically billed by Apify at startup: one unit per whole GB allocated, minimum one |
ad-tracked | $0.0005 per ad | Each normalized ad delivered in the snapshot dataset |
change-detected | $0.003 per change | Each emitted new-ad, disappeared-ad, or new-advertiser event |
Verified-search pricing
The active plan includes advertiser-checked at $0.005 per verified search memory unit, effective since 24 October 2026 at 17:28 UTC. The active plan was checked on 29 October 2026. Consult the Pricing tab for the rates applicable to your run.
One unique search uses one unit per whole GB of allocated RAM, rounded up, with a minimum of one. At 1 GB, a search costs $0.005; at 2 GB, it costs $0.010, before ads and change events. Duplicate inputs that resolve to the same search URL are searched once. Internal retries do not generate a second check fee.
A verified search means a valid public Ad Library response with parseable ads or an explicit empty result. A valid search with zero ads is billed; a response without a verified result is not billed for this event. A collection that reaches maxResults or is not fully verified still delivers its ads and incurs this search fee; it does not update the baseline or emit change alerts. When active, a verified-search record is saved in the default dataset before this fee is charged.
At the active rates, example totals for one search at 1 GB, with no change events, are:
| Ads delivered | Total including startup, search and ads |
|---|---|
| 0 | $0.00505 |
| 1 | $0.00555 |
| 100 | $0.05505 |
Change events add $0.003 each. Use 1 GB for typical searches; allocating more RAM increases memory-based events. Set a spending limit that covers your selected memory, all searches, ads and possible changes. A search is skipped before navigation if the remaining budget cannot cover all its check units. Skipped inputs appear in skippedCompanies and preserve their previous baseline.
Dataset manifests, search-evidence records and aggregate metrics do not create additional item charges. The first complete collection creates a baseline and emits no change events.
How changes are verified
Change events are emitted when both the current snapshot and the saved baseline have verified coverage. The Actor compares the loaded card count with LinkedIn's visible result total (English and Italian result headings) before comparing snapshots.
The default dataset's run manifest exposes per-company coverage (reportedTotal, loadedCount, deliveredCount, complete, reason, stateUpdated) and failedCompanies, skippedCompanies, and the effective billing mode. Every delivered collection is available in the snapshot dataset; only verified complete collections update the baseline.
Country and date filters
For company, payer and keyword searches, country accepts a two-letter country code such as IT, or an empty value for all countries. dateRange accepts 30d (alias for last-30-days), last-30-days, current-month, current-year, last-year, a custom interval such as 2026-10-05..2026-10-06, or an empty value for all dates. Other filter values are rejected at start. Direct Ad Library URLs retain the filters already present in the URL; use the search form on LinkedIn to generate them.
Named output datasets accumulate observations across runs. Filter records by observedAt to inspect one run. disappeared means absent from the verified search results. For multi-company runs, allow enough run time for dataset writes (for example a 360-second timeout) and set a spending cap.
First run
The Console includes a small example: OpenAI ads in Italy during the last 30 days, capped at 5 ads. Replace the company and use a unique monitor ID for each independent monitor. Inputs that could not be collected are listed in failedCompanies in the run manifest, the run ends with a failed status, and their previously stored snapshots are kept. Other inputs still deliver their snapshots in the named dataset.
Chinese Simplified
中文说明:领英广告库变化监控工具(LinkedIn Ad Library Change Monitor 爬虫 / API)
LinkedIn Ad Library Change Monitor 按广告主、付款方、关键词或搜索链接,收集 领英广告库(LinkedIn Ad Library)中的公开广告,并与上一次完整运行的基线自动对比,记录新广告、从已验证搜索结果中消失的广告以及新出现的广告主。全程采用确定性规则,无需领英账号、登录、Cookie、AI或外部Actor。
专为竞品情报、广告活动跟踪、获客研究以及每日或每周的广告提醒打造,适合需要持续关注海外竞品LinkedIn投放的B2B出海团队和广告代理。
为什么选择这款领英广告变化监控工具?
- 直接输出变化,而不是一堆原始数据:一般的广告库爬虫只返回扁平的广告列表,需要自己逐一对比;本工具自动完成对比。首次运行建立基线,之后每次完整运行只输出差异:
new、disappeared和new-advertiser,写入专门的变化数据集,适合定时任务和下游自动化。 - 避免误报:只有经过验证的完整采集才会替换基线;结果达到
maxResults或未经验证时,保留上一次快照并不发出提醒。 - 已验证的覆盖率:将加载的广告卡片数与领英显示的结果总数进行核对,只有覆盖已验证时才产生变化事件。
- 一次运行监控多个竞品:每个监控按
monitorId隔离基线,不同竞品、用户和定时任务互不干扰。 - 完整快照与指标:保存每次的完整快照,便于审计和历史对比;计算在投广告数、本期首次出现的广告数、平均观察存续时间、广告格式分布以及付款方与广告主的对应关系。
- 住宅IP重试:使用自动Apify代理时,搜索可通过住宅IP重试(默认开启,可关闭)。
- 只为有效搜索付费:未获得已验证结果的搜索不收取搜索费,内部重试不重复收费,指向同一搜索链接的重复输入只搜索一次。
适用场景
- 竞品广告监控:每天或每周跟踪竞品在LinkedIn上的新广告。
- 发现广告下线:竞品广告从已验证的搜索结果中消失时获得记录。
- 新广告主发现:被监控的搜索结果中出现新的广告主时自动标记。
- 付款方追踪:按付款方搜索,跟踪广告主与付款方的对应关系。
- 投放策略对比:长期对比竞品的广告活动、格式分布和广告存续时间。
- 自动化提醒:将变化事件导出到数据集,接入下游自动化流程。
可以获取哪些数据?
- 默认数据集:交付的广告行(
recordType: snapshot),包括广告主、广告ID、文案、格式、来源链接和采集时间;运行清单run-manifest,列出每个公司的覆盖情况(reportedTotal、loadedCount、deliveredCount、complete)以及失败或跳过的输入;已验证搜索记录verified-search。 - 变化数据集:
new、disappeared、new-advertiser事件、运行摘要和公司指标。 - 快照数据集:该监控累积的广告观察记录,可按
observedAt选取某一次采集。
控制台提供 Ads and run records 和 Run coverage 两个视图,数据也可通过Apify API读取。
价格
按事件付费,以Apify控制台 Pricing 标签显示的价格为准:
| 计费事件 | 价格 | 计费内容 |
|---|---|---|
apify-actor-start | 每内存单位0.00005美元 | 启动时按分配内存每GB计1个单位,至少1个 |
advertiser-checked | 每个已验证搜索单位0.005美元 | 每次已验证的公开搜索(含有效的零结果),按每GB内存计1个单位,向上取整,至少1个 |
ad-tracked | 每条广告0.0005美元 | 快照中交付的每条广告 |
change-detected | 每次变化0.003美元 | 每个新广告、消失广告或新广告主事件 |
以1 GB内存执行一次搜索、无变化事件为例:0条广告0.00505美元,1条广告0.00555美元,100条广告0.05505美元;每个变化事件另加0.003美元。建议常规搜索使用1 GB内存,并设置最高费用,余额不足以完成某次搜索时,该搜索会在开始前被跳过并保留原有基线。
使用方法
- 在 Companies or Ad Library URLs 中输入一个或多个公司名或领英广告库搜索链接,每行一个。
- 在 Name for this monitor 中为监控命名;每个独立监控使用唯一名称,定期运行时保持相同名称和筛选条件。
- 设置 Maximum ads per advertiser(默认100)。
- 可选:填写 Country(两位国家代码,例如
IT;留空为所有国家)和 Date range(30d、last-30-days、current-month、current-year、last-year,或自定义区间如2026-10-05..2026-10-06)。 - 可选:在 Search type 中选择 Advertiser、Payer 或 Keyword。
- 点击 Start,再保存为Apify任务并设置每日或每周定时运行。首次运行建立基线,之后的运行输出变化。
{"monitorId": "acme-competitors-weekly","advertisers": ["OpenAI", "Anthropic"],"country": "IT","dateRange": "30d","searchType": "advertiser","maxResults": 100}
常见问题
需要领英账号或Cookie吗? 不需要。工具读取公开的领英广告库,不访问任何私有的领英数据。
为什么第一次运行没有变化提醒?
首次完整运行用于建立基线,有意不产生 new 提醒;之后的完整运行只输出与基线的差异。
如何同时监控多个竞品? 在 Companies or Ad Library URLs 中列出所有竞品即可在一次运行中完成;如需分别管理基线,为每个监控使用不同的 Name for this monitor。
修改国家或日期条件会怎样? 更改筛选范围会建立新的基线,而不会产生虚假的变化事件。
“消失的广告”是什么意思?
disappeared 表示该广告已不在本次已验证的搜索结果中。
可以通过API和自动化流程使用吗?
可以。通过Apify API读取数据集,并用 recordType 区分广告和诊断记录;变化数据集适合定时任务和下游自动化。
需要广告的展示量、定向等完整详情? 请使用下方的领英广告库采集工具。
中文说明会翻译采集到的数据吗? 不会。中文说明只是使用文档;采集到的数据保持来源的原始语言(广告文案和广告主名称按领英广告库的原文呈现)。
其他广告情报工具
- 领英广告库采集工具:按公司、关键词或付款方导出LinkedIn广告,含各国家展示量、定向、付款方和投放日期,每1,000条广告0.50美元起。
- Google广告采集工具(Google广告透明度中心):查看竞品在Google搜索、YouTube和Google购物上的广告,含按国家的覆盖、文案和落地页。
- TikTok广告库采集工具:按品牌导出TikTok广告,含覆盖量、广告主和定向。
- 微软/必应广告库采集工具:竞品在必应上的搜索广告、落地页和UTM参数。
- Telegram关键词搜索与频道采集工具:公开Telegram内容研究和关键词发现。
- Google购物价格与卖家监控:监控商品价格、报价和卖家变化。
- 招聘情报工具(Hiring Intelligence):研究你所关注公司的公开招聘信息和技术提及。
- Google新闻采集工具:收集品牌或竞品相关的新闻标题和来源链接。
Chinese Traditional
中文說明(繁體):LinkedIn廣告資料庫變化監測工具(LinkedIn Ad Library Change Monitor 爬蟲 / API)
LinkedIn Ad Library Change Monitor 依廣告主、付款方、關鍵字或搜尋連結,收集 LinkedIn廣告資料庫(LinkedIn Ad Library)的公開廣告,並與上一次完整執行的基準自動比對,記錄新廣告、從已驗證搜尋結果中消失的廣告以及新出現的廣告主。採用確定性規則,不需要LinkedIn帳號、登入、Cookie或AI。
為什麼選擇這款LinkedIn廣告監測工具?
- 直接輸出變化:第一次執行建立基準,之後每次完整執行只輸出
new、disappeared與new-advertiser。 - 避免誤報:只有經過驗證的完整擷取才會取代基準,否則保留上一次快照且不發出提醒。
- 一次監測多個競品:每個監測依
monitorId各自保存基準。 - 只為有效搜尋付費:未取得已驗證結果的搜尋不收搜尋費,內部重試不重複計費。
適用場景
- 競品廣告監測:每天或每週追蹤競品在LinkedIn上的新廣告。
- 新廣告主發現:監測的搜尋結果出現新廣告主時自動標記。
- B2B行銷與市場研究:長期比較競品的廣告活動、格式分布與存續時間。
使用方法
- 在 Companies or Ad Library URLs 輸入公司名稱或LinkedIn廣告資料庫搜尋連結,每行一個。
- 在 Name for this monitor 為監測命名,設定 Maximum ads per advertiser(預設100);選填 Country、Date range 與 Search type。
- 點擊 Start,再儲存為Apify任務並設定每日或每週排程。
{"monitorId": "acme-competitors-weekly","advertisers": ["OpenAI", "Anthropic"],"country": "IT","dateRange": "30d","searchType": "advertiser","maxResults": 100}
價格
依事件計費,以Apify主控台 Pricing 分頁為準:每個已驗證搜尋單位0.005美元,每則廣告0.0005美元,每個變化事件0.003美元,啟動費每記憶體單位0.00005美元。例如以1 GB記憶體搜尋一次、100則廣告、沒有變化事件,合計0.05505美元。
常見問題
需要LinkedIn帳號或Cookie嗎? 不需要,工具讀取公開的LinkedIn廣告資料庫。
為什麼第一次執行沒有變化提醒? 第一次完整執行用於建立基準,之後的完整執行才輸出差異。
「消失的廣告」是什麼意思?
disappeared 代表該廣告已不在本次已驗證的搜尋結果中。
中文說明會翻譯擷取到的資料嗎? 不會。說明是中文,資料保留來源的原始語言(廣告文案與廣告主名稱以LinkedIn廣告資料庫的原文呈現)。
More Actors from this publisher
| Actor | When to use it |
|---|---|
| LinkedIn Ad Library Scraper | Export LinkedIn ads by company, keyword or payer with impressions by country, targeting, payer and dates, from $0.50 per 1,000 ads |
| Hiring Intelligence | Research public job postings and technology mentions for companies whose advertising you follow |
| Google News Scraper Lite | Collect headlines and source links for brand or competitor research alongside ad observations |
Real observed output excerpt
Reduced snapshot from a run on 13 October 2026, using OpenAI, Italy and the last-30-days search. Creative text and other fields are omitted for readability.
{"recordType": "snapshot","adId": "1588837714","advertiser": "OpenAI for Business","format": "SPONSORED_STATUS_UPDATE","sourceUrl": "https://www.linkedin.com/ad-library/search?accountOwner=OpenAI&countries=IT&dateOption=last-30-days","observedAt": "2026-10-13T13:07:29.499Z"}
This run saved one ad snapshot and a separate run-manifest; two dataset rows therefore did not mean two ads. The manifest reported loadedCount 1 and reportedTotal 1 for this search. sourceUrl is the search page used.