Instagram Facebook Brand Presence Mapper

🔎 What can Instagram Facebook Brand Presence Mapper do?

Give it a company domain and it returns that company's Instagram, Threads and Facebook presence in one flat row: profile URLs, handles, follower counts and post counts.

Bought by consumer brand and retail sellers, agency new business teams, and influencer platforms sizing brand audiences across the Meta family in one row.

🚫 This is not a post, ad or comment scraper. It returns account level presence and counts. For a company's advertising, that is a different question and a different dataset entirely.

💡 Why use Instagram Facebook Brand Presence Mapper?

Threads costs you nothing extra here, and that is a measurement rather than a claim. Threads handles are Instagram handles: 5 of 5 measured across stripe, figma, supabase, shopify and hubspot. And 0 of 14 B2B homepages declare a Threads link at all. So a standalone Threads tool has nothing to read and has to pay a web search to rediscover a handle this actor already holds. Once Instagram resolves, Threads is one string substitution.

It tells you which numbers are rounded. Instagram renders "3M". Threads renders "306.9K". Those are the platforms rounding, not us. Both the expanded integer and the platform's own string are on the row, plus a flag, so you know before you sum a column.

It tells you when Facebook refused. Meta serves a login wall to anonymous clients on Pages. This actor reports blocked, which means unknown. It does not report zero.

🧭 One user agent decision carries all three

Meta serves its own link preview crawler an Open Graph card and serves an anonymous browser a JavaScript shell with the counts stripped out. Measured on the same URLs on the same day: Instagram returns 718,863 bytes with "3M Followers, 1,832 Following, 3,707 Posts" to the crawler, and 612,000 bytes of empty shell to a browser.

So all three platforms are read from the card Meta publishes for previews. No login, no API key, no browser automation.

📋 What data can Instagram Facebook Brand Presence Mapper extract?

Every row carries 34 flat fields. These are the ones a buyer actually filters and sorts on.

⚠️ How to read these values. threads_handle is null whenever Instagram did not resolve. That is deliberate: the 5 of 5 evidence is about Instagram handles, and a Threads guess with no Instagram behind it would carry none of it.

🛠️ How to map a company's Meta presence

1. Put a company domain in company_domain.
2. Use platforms to pick which of the three you want. Dropping facebook is the common choice and it makes the run cheaper and faster.
3. If you already know the Instagram handle, put it in handle. That skips Instagram discovery and gives Threads its handle for free.
4. For a list, pass an array of objects. Or put the domains in company_domains, one per line, on the Console form.

🧪 Using it in Clay

Add an Enrichment > Apify column, pick this actor, map company_domain. All three platforms arrive as flat columns on one row, so you get Instagram, Threads and Facebook from a single credit rather than three.

For consumer brand qualification, instagram_followers plus threads_posts is a useful pair: a large Instagram account with zero Threads posts is a brand that has not moved yet.

💵 How much does it cost?

Pay per event. Each run also carries Apify's apify-actor-start event, $0.00005 per GB of run memory, charged once when the run starts (one event at the default memory). Everything else is charged per row of output.

💳 What you are billed for. platform-resolved fires per platform you REQUESTED and resolved, so a run limited to ["instagram","threads"] cannot bill you for Facebook.

A blocked Facebook fetch charges the resolution event, because the URL was found and validated, and does not charge the extraction event, because no number was returned.

What the same coverage costs bought a la carte: Bought separately at Store list prices: apify/instagram-profile-scraper $0.0026, apify/threads-profile-api-scraper $0.0050, apify/facebook-pages-scraper $0.0120, so $0.0196 for the three. Every one of them requires the handle or the page URL as input. This actor resolves all three from a domain, and it derives the Threads handle from the Instagram one for nothing, which is a step none of those three performs.

Free plan: free Apify plan users get 600 results a month, reset on the 1st of each month. Any paid Apify plan removes the cap.

Cost cap: set max_charge_usd and the run stops before starting a company that could take it past that amount. The run also stops cleanly when the maximum cost per run you set in Apify is reached, and keeps every row already charged.

⌨️ Input

{
  "company_domain": "shopify.com",
  "company_name": "Shopify",
  "platforms": [
    "instagram",
    "threads",
    "facebook"
  ]
}

📤 Output

Exports to JSON, CSV, Excel, HTML or XML. One flat, snake_case row per company. No nested objects, so it drops straight into Clay, a spreadsheet or a warehouse table without a flattening step.

{
  "degraded": false,
  "degradation_reason": null,
  "company_domain": "notion.com",
  "company_name": "Notion",
  "platforms_checked": 1,
  "platforms_found": 1,
  "instagram_url": "https://www.instagram.com/notionhq/",
  "instagram_handle": "notionhq",
  "instagram_followers": 485000,
  "instagram_followers_display": "485K",
  "instagram_followers_exact": false,
  "instagram_following": 151,
  "instagram_posts": 350,
  "instagram_discovery": "homepage_link",
  "instagram_status": "ok",
  "threads_url": null,
  "threads_handle": null,
  "threads_followers": null,
  "threads_followers_display": null,
  "threads_followers_exact": null,
  "threads_posts": null,
  "threads_status": "skipped",
  "facebook_url": null,
  "facebook_handle": null,
  "facebook_followers": null,
  "facebook_followers_display": null,
  "facebook_followers_exact": null,
  "facebook_likes": null,
  "facebook_discovery": null,
  "facebook_status": "skipped",
  "run_date": "2026-08-22T12:47:41.744Z",
  "row_status": "ok",
  "error_reason": null,
  "billable_events_json": "[{\"event\":\"company-checked\",\"count\":1}]"
}

false versus null, and why the difference matters

false means we looked and the answer is no. null means we could not look, or the platform withheld it. They are never interchangeable in this output. If you filter for companies with no presence on this platform, filter on false, because null rows are unknown rather than absent and including them will overstate your list.

💡 Tips

• Drop Facebook unless you need it. It is the least reliable of the three and it costs a fetch to discover that.
• Read the _display columns. "3M" tells you more about the precision of the number than 3000000 does.
• A big Instagram with no Threads is a signal, not a gap. It usually means the brand has not adopted the newer network.
• Supply the Instagram handle when you have it. It pays for itself twice, once on Instagram and once on Threads.

⚠️ Known limits

• Instagram, Threads and Facebook all round their counts. There is no exact figure on the card for a large account. The _exact flags mark every row where that applies.
• Facebook is best effort and frequently blocked. Meta serves a 427 KB login interstitial to anonymous clients and blocks aggressively. This is a known, measured, carried across ceiling: a previous Mamba Labs actor recorded 590 upstream failures on this exact path and makes one bounded attempt because retry does not recover. Expect blocked, and read the URL, which is reliable.
• No posts, comments, reels, stories or engagement. Account level presence and counts only.
• A private Instagram account still returns a card with counts, but no content. That is Instagram's behavior, not ours.
• Follower counts are a public vanity metric, a proxy for reach rather than a measurement of it.

❓ FAQ

Why is Facebook so often blocked when Instagram works? Meta treats Pages differently from Instagram profiles for anonymous clients. Pages get a login interstitial. This is Meta's choice and no logged out tool gets around it reliably.

How can Threads be free? Because its handle is the Instagram handle, measured 5 of 5. Once Instagram resolves there is no discovery left to do, only one fetch.

Why are Instagram counts rounded? Instagram renders "3M" on the card. The exact number is not on the wire. instagram_followers_display shows you exactly what the platform said.

Can I get just Instagram? Yes. Set platforms to ["instagram"]. You are then billed for one platform, not three.

Does this need a login or an API key? No.

🧩 Want other GTM data?

Mamba Labs builds a fleet of GTM enrichment actors that share one flat, Clay-ready output convention, so their rows join on company_domain with no cleaning step:

Every actor in the suite takes a domain or a company and returns one flat row, so they stack in the same Clay table without reshaping anything.

🆘 Support

Issues, field requests and bug reports: open an issue on the actor's Issues tab. Mamba Labs reads every one.

ℹ️ Sourcing and legal. Fields are read from the public Open Graph cards Meta serves to any unauthenticated visitor. Counts are public vanity metrics and Instagram rounds them above roughly ten thousand, which instagram_followers_exact marks. You are responsible for how you use the output.

Built by Mamba Labs.