Snapchat for Business Success Story Gallery

Extract public campaign success stories and creative metadata from Snapchat for Business gallery pages. Despite the legacy Actor name, this is not a private Snapchat Ads Library API client: it reads only public forbusiness.snapchat.com HTML and embedded gallery state.

What it returns

Each dataset row is one complete public success-story tile and can include:

• Content ID, title, summary, publication value, tags, and success-story URL
• Public gallery, locale, country, device, and platform metadata
• Creative image URL, content type, dimensions, size, quality, and high-DPI flag
• Optional public story-page title, description, headings, and paragraphs
• Gallery and detail source URLs, HTTP status, proxy use, extraction method, and timestamp

Bulky raw Contentful objects are not retained. Missing fields are omitted, and incomplete tiles are not represented as successful data.

Input

{
  "startUrls": [
    { "url": "https://forbusiness.snapchat.com/success-stories" }
  ],
  "maxItems": 5,
  "fetchDetails": true,
  "requestDelayMs": 250,
  "timeoutMs": 45000,
  "maxResponseBytes": 4000000,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}

The Actor accepts one to 10 exact public /inspiration or /success-stories gallery URLs and emits at most 50 records. Unknown fields and off-scope URLs fail before requests begin. Disable fetchDetails to make only the gallery requests.

Access failures and empty galleries

Network failures, access challenges, changed embedded state, and incomplete tiles are reported in the OUTPUT key’s bounded failures array and counters. They are never mixed into dataset rows. Empty runs are explicitly labeled blocked, failed, or no_data; they are not reported as success.

Requests use a transparent Actor user agent, no retries, bounded response sizes and timeouts, and direct public HTTP by default. Standard Apify Proxy can be enabled when justified. The Actor does not log in, solve CAPTCHAs, patch fingerprints, or bypass access controls.

Cost and responsible use

The base request count is the number of gallery URLs. When detail enrichment is enabled, up to one additional request is made for each selected story. Actual Apify compute, proxy, and storage costs depend on the selected plan and run settings.

Use public data only for lawful advertising research. Follow Snap terms, robots guidance, intellectual-property rules, and content-owner rights. Returned creative URLs do not grant reuse rights, and campaign claims should be independently verified.

Local validation

Run npm test, apify validate-schema, and then a bounded live sample with apify run --purge --input-file qa-inputs/snapchat-ads-gallery-scraper/local-validation.json. Inspect both the default dataset and the OUTPUT key.