Newsletter Ad Rate Card Extractor (sponsor pages) avatar

Newsletter Ad Rate Card Extractor (sponsor pages)

Pricing

$10.00 / 1,000 one newsletter's published sponsorship rate cards

Go to Apify Store
Newsletter Ad Rate Card Extractor (sponsor pages)

Newsletter Ad Rate Card Extractor (sponsor pages)

Give it newsletter domains; it finds the public sponsor/advertise page and extracts published ad prices, CPMs and claimed subscriber counts.

Pricing

$10.00 / 1,000 one newsletter's published sponsorship rate cards

Rating

0.0

(0)

Developer

Maybe Quark

Maybe Quark

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

4 minutes ago

Last modified

Share

Newsletter Advertising Rates: Sponsor Page Rate Card Extractor

Newsletter Ad Rate Card Extractor finds the public sponsor, advertise or media-kit page on each newsletter domain you give it and pulls out the published ad prices, CPM mentions and the subscriber count the publisher claims. Newsletter advertising rates are scattered across hundreds of /sponsor and /advertise pages; this actor reads them for you and returns one row per newsletter, so you can compare sponsorship prices side by side as CSV, JSON or Excel. It reads only each newsletter's own public page on its own domain and respects robots.txt.

Input

{
"domains": ["tldr.tech", "morningbrew.com", "thehustle.co"],
"maxDomains": 50
}
  • domains: newsletter website domains, for example tldr.tech. For each one the actor tries the paths /sponsor, /sponsors, /advertise, /advertising, /sponsorship, /media-kit, /mediakit, /partner and /ads. Protocol, www. and trailing paths are stripped. The default is five well-known newsletter domains.
  • maxDomains: safety cap on domains processed per run (default 50).

Output

One row per domain. Real example row (price text shortened here):

{
"domain": "tldr.tech",
"url": "https://advertise.tldr.tech/",
"status": "prices_found",
"claimedSubscribers": "1.6M subscribers",
"pricesFound": "... $382K in pipeline, their best direct buy yet | ... $1M in pipeline attributed to TLDR ads ...",
"cpmMentions": null,
"crawlDate": "2026-10-14"
}

status is one of prices_found, page_found_no_public_prices or no_public_sponsor_page_found. pricesFound holds dollar amounts with about 40 characters of surrounding text (up to 12 snippets), so it can include case-study figures as well as rate-card prices; read the snippets before using them. cpmMentions holds up to 5 sentences that mention CPM.

Use cases

Search phrases this actor is built for:

  • "Newsletter advertising rates": paste a list of newsletter domains and compare what each publishes.
  • "Newsletter sponsorship prices, CPM and subscriber count": read pricesFound, cpmMentions and claimedSubscribers in one table.
  • "Find a newsletter's sponsor page and rate card": the url column gives the exact public page that was read.

Typical users are indie SaaS founders, small-brand marketers and agencies shopping for newsletter sponsorships. It also works as a tool for AI agents through the Apify MCP server.

Pricing

Pay per result: each newsletter row returned is one billable result, listed at $0.01 per row ($10 per 1,000). Set a maximum charge on the run for a hard ceiling. A pre-built, cleaned rate index is sold separately at https://rasengan.win/products/.

Limits

  • Only the newsletter's own public sponsor page on its own domain is read; no marketplaces, no logins, no emails or personal data are collected, and robots.txt is respected.
  • Prices are as published and may change. Pages that render only with JavaScript, or that hide prices behind a contact form, return a status instead of numbers.
  • Subscriber counts are the publisher's own claims, not verified. Price extraction is text matching, not a structured rate-card parser.
  • A sponsor page on a separate subdomain (for example advertise.example.com) is found only when the main domain redirects to it.

FAQ

Does it scrape ad marketplaces? No, only the publisher's own page.

Are the subscriber numbers verified? No, they are claims from the page.

Why did a newsletter return no_public_sponsor_page_found? None of the tried paths returned a readable page, or robots.txt disallowed them.