Zapier Competitor Ad Tracking: 7 Zaps for Ad Intelligence

Zapier competitor ad tracking is one of those projects marketers assume needs an engineer. It doesn't. Webhooks by Zapier can call any REST endpoint with a Bearer header, which means the same account that routes form leads into your CRM can pull competitor ads into Slack every morning before you open your laptop.

TL;DR: Webhooks by Zapier polls the AdLibrary API with one Bearer header and zero code. This guide builds seven zaps: a scheduled search that posts to Slack, new-ad detection with Storage by Zapier, a Notion swipe database, a weekly email digest, an Airtable archive, an AI enrichment trigger, and a client report appender. Every search costs one credit, so each zap is structured to pay for signal instead of noise.

The hard part is cost discipline, not difficulty. An ad intelligence API charges per search, and a sloppy zap will happily burn a credit every five minutes re-fetching ads you already saw on Monday. The seven recipes below run from simplest to most surgical, and they share one thesis. Structure your zaps so credits buy new information.

Two prerequisites before Step 0. You need a Zapier plan that includes premium apps and multi-step zaps, because Webhooks by Zapier is a premium app. You also need an AdLibrary Business subscription, since API access ships with that tier.

Step 0: Set Up Webhooks by Zapier With Bearer Auth

Start with the data source. Meta's free Ad Library API is the originator of this whole category, and it remains the right tool if you study political and social-issue ads on Facebook. Its commercial coverage is thin, though. Outside the EU and UK it returns political and issue ads only, and it requires app review plus an access token that expires every 60 days. Google publishes its own Ads Transparency Center, and LinkedIn documents its ad APIs on Microsoft Learn, but each is a separate integration with separate auth and separate quirks. Meta's free API is fine for one platform. The moment you want TikTok, YouTube, or LinkedIn ads in the same query, you need something else.

That something is the AdLibrary API, a paid REST API that returns commercial ads across Facebook, Instagram, TikTok, YouTube, Google, LinkedIn, Twitter, Pinterest, and more from one endpoint. Each ad arrives with copy, creative URLs, engagement counts, impressions, an estimated spend figure, and a 0-1000 heat score. If you have ever tried to assemble that picture from scraping tools, you know how fragile the alternative is. There are also other routes to API-grade ad data, but for this guide the deciding factor is that one key covers every platform.

Create the key in your AdLibrary dashboard. It starts with adl_, it is shown exactly once, and you can hold up to 10 keys per account, which is handy for separating clients. Test it from a terminal before touching Zapier:

curl "https://adlibrary.com/api/search" \
  -H "Authorization: Bearer adl_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{"keyword": "protein powder", "appType": "3", "sortField": "-impression", "daysBack": 30}'

The response is plain JSON: a total count, a results array of ads, and a _credits object showing what the call used and what remains. No OAuth dance, no token refresh job.

Now recreate that call in Zapier. Add a Webhooks by Zapier action and pick Custom Request, then configure four fields:

• Method: POST
• URL: https://adlibrary.com/api/search
• Data: the JSON body from the curl test
• Headers: Authorization → Bearer adl_your_api_key, plus Content-Type → application/json

Run the test inside the Zap editor. Zapier parses the response automatically, so every field of every returned ad becomes mappable in later steps. This single configured action is the engine behind every zapier competitor ad tracking recipe in this guide, and the full parameter reference covers every filter it accepts. Duplicate it once per zap rather than rebuilding it, and you will never re-type the headers.

Zap 1: Scheduled Competitor Search → Slack Alerts

The starter recipe. Every weekday morning, search one competitor's recent ads and post anything found to a Slack channel.

Trigger: Schedule by Zapier, daily at 6am.

Action 1, the search. Use your Custom Request with a brand-pinned body. Pin the brand with its Meta page ID rather than a bare keyword, otherwise you match every ad that merely mentions the name:

{
  "keyword": "glow recipe",
  "metaPageId": "123456789",
  "platform": ["facebook"],
  "daysBack": 7,
  "sortField": "-first_seen"
}

Where does the page ID come from? Brand resolution is free. A single call to GET https://adlibrary.com/api/advertisers/search?q=glow+recipe&country=US resolves the name to its Meta, Google, and LinkedIn identifiers without spending a credit. Run it once per competitor and keep the IDs in a note.

Action 2, the gate. Filter by Zapier: only continue if total is greater than 0. No fresh ads means no ping, and the run ends quietly.

Action 3, the alert. Slack's Send Channel Message action, mapping advertiser_name, the ad title, days_count for runtime, and landing_page_url. If your workspace restricts the Slack integration, Slack's own incoming webhooks work through a second Custom Request step instead.

Cost: one credit per run, about 22 credits a month on weekdays. As zapier competitor ad tracking goes, this is the minimal viable version, and it is also the cheapest automated competitor ad monitoring you can build. It retires the manual ad spy habit of checking libraries by hand. For the strategic layer on top of these alerts, the competitor ad monitoring playbook covers what to do with each new creative you catch.

Zap 2: New-Ad Detection With Storage by Zapier

Zap 1 has a flaw you will notice by Thursday. A daysBack: 7 window re-surfaces the same ads every morning until they age out, so most alerts repeat yesterday's news.

Storage by Zapier fixes this with a key-value memory that persists between runs. The pattern:

1. Search as in Zap 1, but add "pageSize": 10 to the body so later loop steps stay cheap.
2. Looping by Zapier, Create Loop From Line Items, iterating over the returned ads.
3. Storage, Get Value with the ad's ad_key as the key. ad_key is the stable identifier an ad keeps across calls, which makes it the only safe dedup handle. Creative URLs and titles change. The key does not.
4. Filter: continue only if the stored value does not exist.
5. Slack alert for the genuinely new ad.
6. Storage, Set Value writing ad_key → today's date, so the next run skips it.

The API also offers a server-side shortcut. Setting "newAdsFlag": true in the search body restricts results to newly seen ads, which thins the stream before Zapier ever loops. Use both: the flag reduces volume, the storage check guarantees exactly-once alerting even when windows overlap.

Note what this pattern saves. The search still costs one credit per run, so storage dedup buys cleaner attention rather than a lower bill. If you got burned by alert fatigue from other tools, this is the recipe that fixes it, and it is the foundation for monitoring competitors without touching Meta's interface at all.

Zap 3: A Notion Swipe Database That Fills Itself

A swipe file only works if it is fed regularly, and nobody feeds one by hand for more than two weeks. This zap turns Notion into a self-filling creative inspiration library.

Trigger: Schedule by Zapier, weekly on Monday.

Action 1: Custom Request with a niche search tuned for proven creatives rather than fresh ones:

{
  "keyword": "sleep gummies",
  "appType": "3",
  "adsType": ["2"],
  "daysBack": 90,
  "sortField": "-days",
  "pageSize": 5
}

sortField: "-days" puts the longest-running ads first, and runtime is the strongest available proxy for performance. Advertisers kill losing creatives within days, so anything still live after a month has earned its budget. adsType: ["2"] restricts results to video, where most ad spend concentrates.

Action 2: Looping by Zapier over the five results.

Action 3: Notion's Create Database Item action, mapping advertiser_name and title into the page name, landing_page_url into a URL property, platform into a select, days_count into a number, and preview_img_url into a files-and-media property as an external URL. The Notion API handles external image URLs natively, so thumbnails render inside the database view.

One styling tip: add a manual "Why it works" text property and leave it empty. The blank column nags you to annotate each ad with the hook or angle you would steal, which is the difference between a swipe database and a screenshot graveyard. Treat the impression figure as a band rather than a precise count when you annotate, since platforms report impressions in ranges.

Cost: one credit per week per niche. Five niches tracked all year cost about 260 credits.

Zap 4: The Weekly Email Digest

Slack alerts suit urgent signals. For everything else, batching wins, and Digest by Zapier is the batching primitive most marketers never discover.

The setup uses two cooperating zaps:

Zap 4a, append. Reuse the Zap 2 skeleton (search, loop, dedup filter), but replace the Slack step with Digest's Append Entry action. Each entry is one formatted line per new ad: advertiser, title, runtime, landing page. Set the digest to release weekly.

Zap 4b, send. When the digest releases, it triggers the follow-on steps. Map the accumulated body into Gmail's Send Email action, addressed to yourself or the whole creative team.

Why bother when Slack already pings you? Because channels scroll and inboxes get reviewed. A digest forces weekly pattern recognition, the moment you notice that a rival shipped six new video hooks in five days, which a drip of single alerts never quite surfaces.

The result reads like a changelog: every competitor ad that appeared this week, in one email, with zero duplicate entries. Pair the digest with the ad spend estimator when you review it, because a burst of new creatives plus rising estimated spend usually marks a scaling push worth studying.

Worth being clear about scope here. This recipe ingests competitor data into your inbox. If you want Zapier to manage your own campaigns, budgets, and pause rules, that is a different discipline with its own recipes, covered in our Zapier Meta ads automation guide. The two stacks complement each other and share nothing but the trigger app.

Zap 5: The Airtable Archive for Trend Analysis

Ad libraries are goldfish. They show what runs now, and a paused ad effectively disappears from view. An archive you own is the only way to answer questions like "how often does this brand refresh creative?" or "how many ads did they run last Black Friday?", which is the raw material of real competitor analysis.

Trigger: Schedule by Zapier, daily.

Action 1: the brand-pinned search from Zap 1 with daysBack: 1.

Action 2: Looping by Zapier over results.

Action 3: Airtable's Find Record action, searching your base on the ad_key field.

Action 4: Filter, continue only when no record was found.

Action 5: Airtable's Create Record action. Useful columns: ad_key as the primary field, advertiser_name, platform, first_seen, last_seen, days_count, like_count, share_count, impression, landing_page_url, and the preview_img_url as an attachment. The Airtable Web API accepts external URLs for attachments, so creatives archive themselves.

Add one Formatter by Zapier step before the create: first_seen and last_seen arrive as Unix timestamps, and Formatter's Date/Time transform turns them into readable dates.

Three months in, this base starts paying rent. Group records by month and you can see each competitor's creative refresh cadence, which tells you how fast their concepts hit ad fatigue. Sort by days_count and the durable concepts float to the top. Filter by platform and you learn where a rival actually concentrates budget, which rarely matches where they make noise. None of that analysis costs additional credits, because querying your own Airtable is free forever. The archive is also where zapier competitor ad tracking stops being an alerting trick and becomes a dataset your team can interrogate.

Zap 6: The Enrichment Trigger for Winners Only

Here is where credit discipline turns into a competitive edge. The AdLibrary API's enrichment endpoint runs a full AI teardown of a single ad: a scene-by-scene transcript, the strategic read on funnel and audience, the persuasion analysis, and a 1:1 creative brief for rebuilding the concept with your own product. Each analysis costs one credit for image ads and videos up to three minutes, with longer videos costing more. Running it on all 60 results of a search would be the noise-paying mistake this article exists to prevent.

So gate it behind proof:

Trigger: Airtable's New Record in View. Create a "Winners" view on your Zap 5 archive filtered to days_count greater than 45. Records enter the view only after an ad has survived six weeks, which is the evidence threshold.

Action: Custom Request, POST to https://adlibrary.com/api/enrichment, with the ad's stored fields mapped into the body:

{
  "ad": {
    "ad_key": "meta_123456789",
    "platform": "facebook",
    "video_url": "https://..."
  }
}

Output: the response carries enrichment.analysis, enrichment.summary, and enrichment.transcription. Map them into a Notion page appended to your swipe database entry, or into a Google Doc per competitor.

Two billing behaviors matter. Ads you have already paid to enrich return free on repeat calls, so re-running the zap never double-charges for the same creative. And failed analyses refund automatically. The deeper version of this loop, where an agent reads the brief and drafts new creative from it, is what the Claude Code workflow guide builds on top of the same AI ad enrichment endpoint.

Zap 7: The Client Report Row Append

Agencies bill hours for competitor research that a zap performs in eight seconds. This recipe builds the weekly evidence trail.

Trigger: Schedule by Zapier, Friday afternoon.

Action 1: one search per tracked competitor with daysBack: 7, brand-pinned as in Zap 1.

Action 2: Google Sheets' Create Spreadsheet Row in a per-client sheet. Columns that survive contact with account managers: week date, competitor, new ads this week (the total field), longest current runtime, top platform, and a link to the standout creative. Monday's status call writes itself from the sheet, and the client pitch workflow shows how the same data seeds new-business decks.

Keep one zap per client. Duplicating a zap takes thirty seconds, and per-client zaps mean you can pause a churned account without surgery on a shared workflow.

For multi-platform coverage per brand, upgrade the search step to the saved-advertiser flow. Save each competitor once via POST /api/advertisers with its Meta, Google, and LinkedIn IDs, then call POST /api/advertisers/{id}/curate. One curate call fans out across all three platforms, merges the results, and dedups them by ad_key. It costs one credit per 30-minute session regardless of platform count, which beats three separate searches, and it pairs naturally with saved ads for the creatives you flag along the way. Budget math for a typical roster: five clients with three competitors each on weekly pulls is roughly 60 credits a month. Add the Facebook ads cost calculator to your report template if clients want benchmark context next to the competitive data.

Dedup Patterns for Zapier Competitor Ad Tracking

Every recipe above leans on one of five dedup patterns. Choosing deliberately is what keeps zapier competitor ad tracking cheap at scale, so here they are side by side.

Time-window dedup. Search with daysBack: 1 on a daily schedule. Each run sees only the newest slice. Cheapest pattern, no extra steps, but a paused zap leaves a blind spot for the days it missed.

Server-side flags. "newAdsFlag": true returns only newly seen ads, and "duplicateRemoval": true collapses near-identical creatives in the response. Both shrink result volume before Zapier loops, which saves tasks on your Zapier bill.

Storage-key memory. The Zap 2 pattern. Exact, per-zap, survives schedule gaps. Costs two extra task steps per looped ad.

Find-before-create. The Zap 5 pattern. Durable and queryable, since your dedup ledger doubles as your archive. Slowest of the four, fine at daily cadence.

Session reuse. Curate sessions stay open for 30 minutes, and continuation calls inside the window are free. Relevant when one zap checks several platforms for the same brand back to back.

Notice which patterns save credits and which save attention. Time-window and session reuse reduce what you pay the API. Storage keys and find-before-create reduce what you read. The server-side flags do a little of both. A mature setup stacks one from each column.

When Zapier Is the Wrong Tool for Competitor Ad Tracking

Zapier's ceiling is real, and pretending otherwise produces ugly bills. Three walls you will eventually hit:

Task economics. Looping is expensive. Sixty ads through a four-step loop is 240 tasks in one run, and daily runs put you at 7,000+ tasks a month for a single zap. Zapier pricing scales with tasks, so high-volume ingestion belongs elsewhere.

Pagination. The API paginates cleanly with page and pageSize up to 100 results per page, but each page is a fresh one-credit search and Zapier has no elegant way to loop "fetch until done." If your research needs deep result sets, a script does in twelve lines what Zapier does in three chained zaps.

Rate limits and retries. The API allows 10 requests per minute and 10,000 per day per key, with a Retry-After header on 429 responses. Zapier cannot honor that header, so the step simply fails. Daily-cadence zaps never get close to the limits, but anything polling dozens of brands hourly needs real backoff logic.

When you outgrow it, the migration path is gentle because the API stays identical. n8n gives you self-hosted loops where tasks cost nothing, Make.com sits between the two on price and power, and a self-built MCP server hands the whole research loop to an AI agent. The fully agentic version of that, where the model plans its own searches, lives in our agentic marketing workflows guide. For a solo marketer watching five competitors at daily cadence, though, Zapier remains the honest answer.

Frequently Asked Questions

Do these zaps need a paid Zapier plan?

Yes. Webhooks by Zapier is a premium app, and every recipe here is multi-step, both of which sit above Zapier's free tier. Any paid Zapier plan works. On the data side you need the AdLibrary Business plan, which includes API access and 1000+ monthly credits.

How many credits does zapier competitor ad tracking use?

One credit per search call. A weekday-only daily brand check runs about 22 credits a month, and a daily check about 30. Enrichment adds one credit per analyzed ad, more for videos over three minutes. A typical solo setup tracking five competitors stays under 200 credits a month.

Can Zapier track competitor ads on TikTok, YouTube, and LinkedIn?

Yes. The same /api/search call accepts a platform parameter covering Facebook, Instagram, TikTok, YouTube, Google, LinkedIn, Twitter, Pinterest, and more, so one zap can watch all of them. Meta's free Ad Library API stops at Meta's own platforms, which is the main reason to pay for broader coverage.

How do I stop the same ad triggering alerts every day?

Key your dedup on ad_key, the stable identifier each ad keeps across API calls. Store seen keys with Storage by Zapier and filter unseen ones through, or narrow the search with daysBack: 1 and newAdsFlag: true so each run only returns fresh ads.

Is the AdLibrary API free like Meta's Ad Library API?

No. Meta's API is free and remains the right choice for political-ad transparency research on Meta. The AdLibrary API is a paid upgrade on the Business plan at €329/mo: commercial ads across 11 platforms, engagement and impression signals, estimated spend, heat scores, and AI creative briefs behind a single adl_ key.

Your First Zapier Competitor Ad Tracking Stack

Build in this order. Zap 1 today, because a working Slack alert this week beats a perfect system next month. Add the Storage dedup from Zap 2 the first time a repeat alert annoys you. Add the Airtable archive in week two, and let it accumulate quietly. Hold off on enrichment until the archive proves which ads deserve a deeper look, then wire Zap 6 and let the briefs come to you.

The whole stack is a few evenings of clicking, no code, and a credit bill that stays boring because every recipe pays for new information only. That is what separates deliberate zapier competitor ad tracking from the polling scripts that quietly drain an API budget.

API access ships with the Business plan at €329/mo, which includes 1000+ monthly credits, up to 10 API keys, and free integration help from the team if a zap fights you. Compare tiers on the pricing page, or start with the API access feature overview and run your first curl before the coffee gets cold.