Pinterest Brand Presence Mapper

🔎 What can Pinterest Brand Presence Mapper do?

Give it a company domain and it returns that company's Pinterest business account with exact follower, pin and board counts, its claimed website, verified merchant status and how recently it pinned.

📦 What you get	⚙️ Features and integrations
📌 Pinterest business account resolved from a domain 🔢 Exact follower, pin and board counts 🕰️ Activity recency, so a dormant account is visible 🧾 22 flat fields, snake_case, one row per company	🛍️ Built to join an ecommerce profile on company_domain 🌐 Domain first discovery, no handle required 🚦 Status per row, not_found and blocked are different answers ⬇️ Export to JSON, CSV, Excel, HTML or XML

Bought by ecommerce and DTC sellers, retail agencies, and home, food and fashion vertical teams where Pinterest is a real acquisition channel.

🚫 This is not a pin or board content scraper. It returns the account and its counts, once per company. It does not download pins, images or board contents.

💡 Why use Pinterest Brand Presence Mapper?

The counts are exact. Pinterest serves real integers, so unlike Instagram, TikTok, YouTube, Threads and Facebook, these numbers can be summed across a target list without summing the platform's rounding.

Board count is the better activity signal. Followers are a vanity metric on every platform. Boards are curation work, and a consumer brand with thirty boards is investing in Pinterest in a way that one with three thousand followers and two boards is not.

It refuses to report a stranger's account as yours. This matters more on Pinterest than anywhere else in this family, because handles here are rarely the domain stem. Guessing pinterest.com/stripe for stripe.com returns a real, active account with 35 followers, 117 pins and 30 boards, belonging to a private individual named Debra Rotz. This actor reports identity_mismatch and no counts. A tool without that check would publish her numbers under Stripe's domain.

It joins cleanly with company level ecommerce data. Identity columns use the fleet's standard spelling and every count is an integer, so a join on company_domain needs no cleaning step.

🧭 Why identity checking matters so much here

Pinterest usernames are rarely the domain stem, and B2B homepages declare Pinterest even less often than they declare TikTok. So the guess route gets used a lot, and the guess route is where wrong accounts come from.

Every account found by guessing or by search is checked against the company before its numbers ship, using two signals the guess did not choose: the account's own display name, and the website it claims. When neither corroborates, the row reports identity_mismatch, keeps the URL so a human can check the call, and returns no counts.

📋 What data can Pinterest Brand Presence Mapper extract?

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

Field	Type	Meaning
degraded	boolean	True when this row could not be produced normally, for example the company site was unreachable and no discovery could run. A degraded row is never charged.
degradation_reason	string | null	Why the row is degraded, in plain words. Null on a normal row.
company_domain	string | null	The company domain this row is about, normalized. Null when only a handle or a name was supplied. This is the join key across the whole Mamba Labs fleet.
company_name	string | null	The company name as supplied or derived. Improves search accuracy and is what the identity gate matches against.
pinterest_url	string | null	Canonical Pinterest profile URL, or null when no trustworthy account was found.
pinterest_handle	string | null	The resolved Pinterest username.
pinterest_followers	integer | null	Exact follower count. Pinterest serves the real integer, so this number can be summed across a list, unlike Instagram, TikTok, YouTube, Threads and Facebook.
pinterest_followers_exact	boolean | null	Always true when a count was returned. Pinterest does not round.
pinterest_following	integer | null	How many accounts this account follows.
pinterest_pin_count	integer | null	Total pins on the account. Zero is a real answer and means a claimed but unused account.
pinterest_board_count	integer | null	Total boards on the account. For a consumer brand this is a better activity signal than follower count: boards are curation effort and followers are not.
pinterest_display_name	string | null	The account display name. This is what the identity gate checks against, and on this platform it does real work.
pinterest_about	string | null	The account about text.
pinterest_website	string | null	The website the account links to. When its host is the company domain, the account is provably this company's and needed no guessing.
pinterest_verified_merchant	boolean | null	True when Pinterest marks the account as a verified merchant, which is a real commerce signal rather than a vanity badge.
pinterest_last_pin_at	string | null	When the account last saved a pin, where the page declares it. An account with boards and no recent pins is dormant.
pinterest_discovery	string | null	How the account was found: input_handle, homepage_sameas, homepage_link, search or pattern_guess. Treat pattern_guess with particular suspicion on Pinterest: see Known limits.
pinterest_status	string	ok, not_found, not_extractable, blocked, identity_mismatch, auth_failed or skipped. identity_mismatch is more common here than anywhere else in this actor family and it is the actor working correctly.
row_status	string | null	ok when the lookup ran and found what it looked for, no_match when it ran and there is nothing to find, incomplete when the platform withheld or refused part of it (the reason is in error_reason), error when the row could not be produced. Read from pinterest_status and degraded.
error_reason	string | null	Why the row is incomplete or an error, in plain words. Null on an ok or no_match row.
billable_events_json	string	The pay per event charges this row caused, as a JSON array of {"event","count"}. [] when the row charged nothing. The once per run apify-actor-start event is not on any row.
run_date	string	ISO 8601 timestamp of this run. Social counts move, so a row without a date is a number with no shelf life.

⚠️ How to read these values. pinterest_website is the strongest field on the row for verification. When its host equals your company_domain, the account is provably the company's own.

🛠️ How to find a company's Pinterest account

1. Put a company domain in company_domain.
2. Add company_name. On this platform it does more work than anywhere else, because it is what the identity gate checks a guessed account against.
3. If you already know the handle, put it in handle. That skips discovery and the identity risk with it.
4. For a list, put the domains in company_domains, one per line, or pass an array of objects with the same fields.

🧪 Using it in Clay

Add an Enrichment > Apify column, map company_domain.

This actor pays off on consumer and ecommerce brands and returns not_found on most pure B2B software companies, which is correct rather than a failure. Gate the column on your ICP so you are not spending credits establishing that a devtools company has no Pinterest.

💵 How much does it cost?

Pay per event. Every run is also charged Apify's platform start event, apify-actor-start, at $0.00005 per GB of run memory, one event and $0.00005 at this actor's default of 1,024 MB. Everything else is charged per row of output. Prices shown are the free plan price; paid Apify plans pay 10 to 30 percent less per event, depending on the plan.

Free Apify plan: up to 900 results per calendar month, reset on the 1st. Any paid Apify plan removes the cap.

Spend limits. Set max_charge_usd and the run stops before its charges pass that amount. The maximum cost per run you set in Apify is honored the same way. Either way every row already charged is kept, and each row lists its own charges in billable_events_json.

Event	Fires when	Price
company-checked	Once per company for which the discovery cascade completed and a non degraded row was produced, whether or not a Pinterest profile was found. Does not fire on a degraded row, because on a degraded row no discovery was performed.	$0.0035
profile-resolved	Once per company whose candidate Pinterest URL passed the identity gate. Fires on the validation work, not on a populated count. A candidate dropped as an impersonator does not charge: the work was done and the honest answer is that there is no such profile.	$0.0030
follower-count-extracted	Once per company where a numeric follower count was read off the public page. Does not fire on not_extractable, blocked, identity_mismatch or url only runs.	$0.0025

💳 What you are billed for. An identity_mismatch row charges company-checked and profile-resolved, because a candidate was found, fetched and validated, and the answer is that it was not this company. It does not charge the extraction event.

What the same coverage costs bought a la carte: There is no Pinterest company presence actor on the Apify Store that accepts a company domain. Pinterest scrapers on the Store take a username or a board URL and return pins, which is content rather than company presence. There is no like for like price, so this follows the family's own three event shape.

⌨️ Input

Field	Type	Required	Meaning
company_domain	string	no	Bare company domain, for example shopify.com. Supply this or a handle. With a domain the actor runs full discovery; with a handle it skips straight to the fetch.
company_name	string	no	Optional. Improves search accuracy and is what the identity gate checks a discovered profile against, so supplying it reduces wrong matches.
handle	string	no	Optional. The Pinterest username from pinterest.com/
includeFollowerCounts	string	no	When "true" (default) the profile page is fetched and the counts are extracted. Set "false" to resolve the profile URL only, which is cheaper and needs no proxy. Sent as a string for Clay compatibility.
skipCache	string	no	When "false" (default) a successful lookup is cached for seven days and reused. Set "true" to force a fresh fetch. Sent as a string for Clay compatibility.
company_domains	array	no	Optional. A list of bare company domains, one per line, for example stripe.com. Each domain becomes its own row, so a list of 500 is one run and one start charge instead of 500. Per company fields above (name, handle, ids) apply only to the single Company Domain row, never to the list.
max_charge_usd	number	no	Optional. The run stops before its event charges pass this amount, for example 2.50. Every row already charged is kept. Leave empty for no cap beyond the maximum cost per run you set in Apify, which is also honored.

{
  "company_domain": "shopify.com",
  "company_name": "Shopify"
}

📤 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": "patagonia.com",
  "company_name": "Patagonia",
  "pinterest_url": "https://www.pinterest.com/patagonia/",
  "pinterest_handle": "patagonia",
  "pinterest_followers": 111474,
  "pinterest_followers_exact": true,
  "pinterest_following": 10,
  "pinterest_pin_count": 10,
  "pinterest_board_count": 19,
  "pinterest_display_name": "Patagonia",
  "pinterest_about": "Build the best product, cause no unnecessary harm, use business to inspire and implement solutions to the environmental crisis.",
  "pinterest_website": "http://www.patagonia.com/",
  "pinterest_verified_merchant": true,
  "pinterest_last_pin_at": "Thu, 20 Aug 2026 21:56:58 +0000",
  "pinterest_discovery": "homepage_sameas",
  "pinterest_status": "ok",
  "row_status": "ok",
  "error_reason": null,
  "billable_events_json": "[]",
  "run_date": "2026-08-22T12:48:29.558Z"
}

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

• Check pinterest_website first. It is the cheapest confirmation that the row is right.
• Compare pinterest_board_count, not followers, when you are ranking brands by Pinterest investment.
• Filter out pattern_guess rows if a wrong match would be costly, even though they are gated.
• not_found on a B2B software company is the correct answer, not a coverage gap.

⚠️ Known limits

• Discovery is genuinely hard here. Pinterest handles are rarely the domain stem and few B2B homepages declare a Pinterest link. Expect not_found and identity_mismatch more often than on LinkedIn or YouTube.
• The page is heavy, 1.4 MB, second only to YouTube in this family. Cheap in money over datacenter routing, not fast.
• No pins, no boards content, no pin engagement. Account level presence and counts only.
• A personal account can look exactly like a brand account. That is why the identity gate exists and why identity_mismatch is a status you will see.
• Follower counts are a public vanity metric, a proxy for reach rather than a measurement of it.
• An account can resolve and still return no counts. When Pinterest serves the profile without its embedded counts, the row keeps the URL and reports pinterest_status not_extractable with every count null. Measured on lego.com on 2026-09-21 and 2026-10-05.

❓ FAQ

Why do I get identity_mismatch so often on Pinterest? Because Pinterest handles rarely match domain stems, so the actor has to guess more often, and a guess frequently lands on a real account belonging to somebody else. Reporting the mismatch is the actor working correctly.

Are the counts exact? Yes. Pinterest serves real integers.

Why does a B2B company return not_found? Because it probably has no Pinterest account. That is a real answer.

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

Can I pass a handle instead of a domain? Yes, in handle, and on this platform it is the safest input.

🧩 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:

🔔 Account Hiring Watch	🕵️ Agent Accessibility Auditor
🤖 AI Tooling Detector	📡 GTM Signals Aggregator
🚀 Prospect Engine	📝 Publishing Frequency Tracker
🦋 Bluesky Brand Presence Mapper	🔀 Career Change Signal Engine
⏩ Sequencer Lead Push	🔄 Company Change Event Feed
📇 Company Contact Details Extractor	🧭 Company Discovery List Builder
🏢 Company Firmographic Enricher	🪪 Company Identity Resolver
🌐 Company Social Presence Mapper	🏷️ Contact Classifier
📈 Influencer Change Monitor	🔎 Influencer Finder
🧾 Influencer Lead List Builder	👤 Influencer Profile Scraper
📬 Domain Deliverability Checker	🔗 Domain to LinkedIn URL Resolver
🛒 Ecommerce Platform Profiler	✉️ Work Email Waterfall
🎪 Event Presence Index	⚖️ Expert Witness Directory
💵 Company Funding Record	💰 Funding and Press Signal Scanner
🐙 GitHub Organization Signal Scanner	🧑‍💼 GTM Hiring Signal Scraper
📋 Job Posting Monitor	🧱 Tech Stack Signal Detector
🎯 ICP Fit Scorer	🔑 Job Board Keyword Signal Scanner
🧳 Job Change Tracker	🏛️ Legal Entity Resolver
📰 Link in Bio Scraper and Newsletter Detector	💼 LinkedIn Company Page Mapper
💬 LinkedIn Post Tracker	📢 Meta Ad Library Monitor
📸 Instagram Facebook Brand Presence Mapper	🆕 New Hire Finder
📮 Outbound Stack Detector	📄 Page Finder and Extractor
🧑 People Finder & Email Verifier	🏆 Government Contract Award Monitor
📅 Reporting Window Finder	👽 Reddit Brand Presence Mapper
⭐ Trustpilot Reputation Enricher	🤝 Influencer Talent Agency Lookup
👥 Team Page People Extractor	🎵 TikTok Brand Presence Mapper
📊 Website Traffic Rank Estimator	🏅 Workplace Program Detector
✖️ X Brand Presence Mapper	▶️ YouTube Channel Stats Extractor

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.

🛠️ Need something custom built for you or your team? Tell us what you are trying to find and we will build it. Talk to Mamba Labs.

🆘 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 Pinterest profile page served to any unauthenticated visitor. Counts are public vanity metrics. You are responsible for how you use the output.

Built by Mamba Labs.