Coupang Email Scraper avatar

Coupang Email Scraper

Pricing

from $1.19 / 1,000 results

Go to Apify Store
Coupang Email Scraper

Coupang Email Scraper

Coupang Email Scraper SD - Coupang Email Scraper is a lead generation tool that extracts leads with public contact emails, account names and profile URLs from Coupang results by keyword, location and email domain - Coupang email extractor.

Pricing

from $1.19 / 1,000 results

Rating

0.0

(0)

Developer

Neuro Scraper

Neuro Scraper

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

5 days ago

Last modified

Categories

Features

Limited permissions

Share

Coupang Email Scraper

The Coupang Email Scraper collects publicly indexed contact emails connected to coupang.com, South Korea's dominant e-commerce platform. It builds Google queries with the site:coupang.com operator, fetches them through the Apify GOOGLE_SERP proxy, and extracts emails from the result blocks. No login, no browser, no Coupang API — only what Google has already published in its index.

Start with the honest part. Coupang exposes few indexable seller pages, so expect low volume. Coupang is heavily app-first and first-party, its seller tooling lives behind the Wing seller console, and much of the site is not the kind of open, crawlable seller directory that Google indexes deeply.

That shapes what the Coupang Email Scraper realistically finds: supplier, brand and business contact details that happen to be published on Coupang's own indexable pages. It does not find marketplace-seller inboxes at scale, because Coupang largely does not expose those publicly. If you need volume from genuine third-party sellers, the Allegro Email Scraper and Cdiscount Email Scraper are structurally far more productive.

What one run of the Coupang Email Scraper produces

Each dataset row is one unique email plus whatever account context Google printed around it. You get the raw title, an account label, a snippet, the exact query used and a truncation flag. The Coupang Email Scraper pushes rows to the Apify dataset as they are found, so you can export CSV or JSON mid-run.

Korean keywords and countryCode in the Coupang Email Scraper

This is the most important configuration section here, and the main lever you have over your results. coupang.com is indexed overwhelmingly in Korean. The shipped defaults — keywords of seller and brand, with email, contact, wholesale, customer service and inquiries as modifiers — are English starting points, not the optimal configuration.

To search this platform properly, switch to Korean terms. English queries against a Korean-language domain match a thin slice of the index and will usually return very little.

Korean keyword suggestions for the Coupang Email Scraper

Korean termMeaningUse it for
판매자sellerThe direct equivalent of the default seller keyword
브랜드brandBrand and label pages
업체company / vendorBusiness-facing pages
제조사manufacturerSupplier and sourcing research
도매wholesaleThe Korean equivalent of the wholesale modifier
문의inquiryContact-intent modifier
고객센터customer service centreSupport and contact pages
연락처contact detailsStrong contact-intent modifier

Combine a noun with an intent word — 판매자 문의, 도매 연락처 — rather than searching a bare noun. Keep one or two English terms in the mix as a control so you can compare which language actually returns rows for your niche.

Setting countryCode for the Coupang Email Scraper

Set countryCode to KR. This makes the Apify GOOGLE_SERP proxy search from a South Korean vantage point. Google personalises heavily by country, and a Korean-country search is what surfaces coupang.com pages at all; a default or US search will bury them.

countryCode: "KR" plus Korean keywords is the pairing that gives the Coupang Email Scraper its best chance. One caveat worth knowing: Google is not the dominant search engine in South Korea, so Google's index of Korean commercial pages is thinner than you might expect from other markets. The Coupang Email Scraper reads Google only.

Korean free-mail domains for customDomains

The default customDomains are @gmail.com and @yahoo.com. Keep Gmail. Yahoo is effectively absent from the Korean market and should be replaced.

These local providers are worth testing. They are suggestions based on how the Korean market publishes contact details, not guarantees of volume:

DomainWhy add it for Coupang
@naver.comBy far the most common personal and small-business mailbox in Korea
@daum.netThe other long-established Korean portal mail
@hanmail.netDaum's legacy address, still in wide circulation
@nate.comAnother Korean portal provider
@gmail.comKeep — widely used by Korean businesses that trade internationally

Each extra domain multiplies the query count, because the Coupang Email Scraper searches every keyword against every domain. Given the low expected yield, prefer a tight set — @naver.com, @daum.net, @gmail.com — over a wide sweep.

Coupang Email Scraper features

Everything listed below is implemented in the Coupang Email Scraper today.

FeatureWhat it means in practice
Query expansionBase, quoted, intitle: and one variant per modifier; base queries run first
Global deduplicationAn email found by several queries is stored exactly once
Email normalisationUnderstands name [at] domain [dot] com, name (at) domain, name @ domain, domain .com, zero-width characters and the full-width @
Junk filterRejects placeholders such as email@, yourname@, test@, xxx@ and single-character locals
Boundary-correct matching@gmail.com will not match inside @gmail.company or @gmail.com.br
Soft-wrap repairDrops a hit that is only the tail of another email in the same block
Structural parsingFinds the <h3> and the smallest surrounding block, so it does not depend on Google's CSS class names
Whole-page fallbackIf Google's markup changes, the run degrades to "emails without account details" rather than "no emails"
Block detectionCAPTCHA, "unusual traffic" and consent pages are detected and retried, not counted as empty
RetriesUp to 3 attempts per page with exponential backoff and a fresh proxy session per request
Failed-query requeueBlocked or failed queries are re-queued once at the end of the run
ConcurrencyAn asyncio worker pool with a shared stop signal on maxEmails
Resumable stateKey-value store state keyed by an input hash; saves on PERSIST_STATE, MIGRATING and ABORTING
Run summaryLogs pages fetched, blocked pages, retries and emails per page

How the Coupang Email Scraper works

The Coupang Email Scraper runs the same six steps on every query it builds.

  1. It reads your input: keywords, location, email domains and limits.
  2. It builds Google queries with the site: operator against coupang.com, for example site:coupang.com 판매자 "@naver.com" 문의.
  3. It fetches result pages through the Apify GOOGLE_SERP proxy using async aiohttp requests.
  4. It parses each result block structurally rather than by CSS class name.
  5. It extracts emails with a domain-filtered regex and normalises obfuscated forms.
  6. It deduplicates globally and pushes each lead to the dataset immediately.

There is no browser, no JavaScript rendering, no authentication and no cookies. The Coupang Email Scraper never signs into Coupang and never requests pages from Coupang's own servers. Everything it returns was already public in Google's search index.

Coupang Email Scraper input fields

These are the exact input fields the Coupang Email Scraper accepts, with the defaults it ships with.

FieldTypeDefaultMeaning
keywordsarray (required)["seller","brand"]Search terms describing the accounts you want
locationstring""Optional location phrase added to every query
customDomainsarray["@gmail.com","@yahoo.com"]Only emails on these domains are kept; @ optional
maxEmailsinteger 1-1000020Stop after this many unique emails
countryCodestring""Two-letter country for the search proxy — set KR here
expandQueriesbooleantrueSearch each keyword x domain in several phrasings
queryModifiersarray["email","contact","wholesale","customer service","inquiries"]Extra words combined with each keyword when expansion is on
maxPagesPerQueryinteger 1-5030Page cap per query
maxConcurrencyinteger 1-205Parallel queries

Example Coupang Email Scraper input

{
"keywords": ["판매자", "브랜드", "제조사"],
"location": "서울",
"customDomains": ["@naver.com", "@daum.net", "@gmail.com"],
"maxEmails": 100,
"countryCode": "KR",
"expandQueries": true,
"queryModifiers": ["email", "문의", "도매", "고객센터", "연락처"],
"maxPagesPerQuery": 30,
"maxConcurrency": 5
}

The location field simply appends a phrase to every query. Korean city names work as values — 서울, 부산, 인천 — or their romanisations, Seoul, Busan. On a low-yield platform this narrows an already narrow result set, so leave it empty unless you specifically need regional segmentation.

Coupang Email Scraper output fields

Every dataset item the Coupang Email Scraper writes carries all fourteen of these fields.

FieldMeaning
networkPlatform name
keywordThe keyword that produced the lead
queryThe exact Google query used
titleRaw result title
accountNameAccount label Google prints
fullNameDisplay name parsed from a profile-style title; empty for post captions
usernameURL-safe handle when the platform exposes one; otherwise null
profileUrlCanonical account URL when a handle is known; otherwise empty
urlDirect platform link when exposed, else the profile URL
descriptionBio or snippet text, cleaned of labels and engagement counters
emailLower-cased email address
emailDomainThe matched domain
possiblyTruncatedtrue when Google's snippet ellipsis touched the email
foundAtISO 8601 UTC timestamp

Example Coupang Email Scraper output

[
{
"network": "Coupang",
"keyword": "판매자",
"query": "site:coupang.com 판매자 \"@naver.com\" 문의",
"title": "한빛리빙 - 쿠팡 상품 페이지",
"accountName": "한빛리빙",
"fullName": "한빛리빙",
"username": "1234567890",
"profileUrl": "https://www.coupang.com/vp/products/1234567890",
"url": "https://www.coupang.com/vp/products/1234567890",
"description": "생활용품 판매자. 문의: hanbit.living@naver.com",
"email": "hanbit.living@naver.com",
"emailDomain": "@naver.com",
"possiblyTruncated": false,
"foundAt": "2026-08-31T13:11:29Z"
},
{
"network": "Coupang",
"keyword": "도매",
"query": "site:coupang.com 도매 \"@daum.net\" 연락처",
"title": "도매 문의 안내 - 쿠팡",
"accountName": "도매 문의 안내",
"fullName": "",
"username": null,
"profileUrl": "",
"url": "",
"description": "대량 구매 문의: wholesale.example@daum.net",
"email": "wholesale.example@daum.net",
"emailDomain": "@daum.net",
"possiblyTruncated": true,
"foundAt": "2026-08-31T13:12:50Z"
}
]

Note the second row: username is null and profileUrl is empty, because Google printed an informational page title with no product or seller identifier to build a URL from. Note also the shape of the first row's profileUrl. On Coupang the canonical link the Coupang Email Scraper can construct is a product URL, https://www.coupang.com/vp/products/{id}, not a standalone seller storefront — because Coupang does not generally expose one.

What a measured Coupang Email Scraper run looked like

In an internal test run against coupang.com, only 3 of 10 rows carried a usable account identity in accountName or fullName. That is the weakest identity rate of the five regional marketplace Actors in this family, and it is a direct consequence of Coupang exposing few indexable seller pages.

Most rows will give you an email and a query, with thin account context around it. Plan your enrichment accordingly: expect to match on the email itself rather than on a seller name.

Use cases for the Coupang Email Scraper

Here is where the Coupang Email Scraper fits into real prospecting and research workflows.

Use caseHow to configure it
Korean supplier sourcingkeywords: ["제조사","도매"], countryCode: "KR", customDomains: ["@naver.com","@gmail.com"]
Brand contact discoverykeywords: ["브랜드","업체"] with the 연락처 and 문의 modifiers
Filling gaps in an existing KR listMatch on email rather than accountName, given the low identity rate
Cross-border trade researchCombine @gmail.com with Korean keywords to find export-oriented businesses
Market researchAnalyse query and keyword to see which Korean phrasings surface public contacts
Language A/B testingRun English defaults and Korean keywords separately and compare row counts
Cross-market enrichmentRun beside the Rakuten, Shopee and Lazada Actors for a wider APAC picture
Data-quality benchmarkingCompare yield here against a European marketplace to calibrate expectations

Practical Coupang Email Scraper recipes

Korean baseline. Korean keywords, Korean modifiers, countryCode: "KR", maxEmails: 50. This is the configuration most likely to return anything at all.

English control run. Shipped defaults, countryCode: "KR", same maxEmails. Comparing the two runs shows you empirically how much the language switch is worth for your niche.

Domain sweep. Run @naver.com, @daum.net and @gmail.com as three separate runs. On a low-yield platform, per-domain visibility is more useful than one merged number.

Widen before you deepen. More Korean keyword variants beat more pages per query here. Raise maxPagesPerQuery last, once you have confirmed a keyword returns Coupang pages at all.

Responsible use, PIPA and GDPR

South Korea's Personal Information Protection Act (PIPA) is one of the stricter privacy regimes in Asia, and it applies to personal data you collect about Korean individuals. If you are established in the EU or targeting EU residents as part of the same campaign, the GDPR applies too.

An email that identifies a natural person is personal data even when it was published publicly. Public availability is not consent to send, and PIPA is notably firm on unsolicited commercial messaging.

Practical steps that keep a Coupang Email Scraper workflow defensible:

  • Strongly prefer role addresses (info@, sales@, 문의 inboxes) over addresses naming an individual.
  • Keep provenance for every lead — the query, url and foundAt fields exist for exactly this.
  • Give a clear sender identity, a stated purpose and a working opt-out in every message.
  • Honour opt-outs immediately and check suppression lists before each follow-up.
  • Delete data you are not actively using rather than warehousing scraped lists.
  • Take Korean legal advice on PIPA before running commercial outreach into that market at scale.

This is operational guidance, not legal advice.

The Coupang Email Scraper is part of an E-commerce and Marketplaces family that all share this engine. For a broader Asian sweep, pair it with the Rakuten Email Scraper for Japan, the Shopee Email Scraper for Southeast Asia and the Taobao Email Scraper for China. For markets where third-party seller pages are genuinely indexed, the Allegro Email Scraper and Cdiscount Email Scraper return considerably more.

ActorWhat it collects
Coupang Email and Phone Number ScraperEmails and phone numbers from Coupang
Coupang Phone Number ScraperPublic phone numbers from Coupang
AliExpress Email ScraperPublic contact emails from AliExpress
Allegro Email ScraperPublic contact emails from Allegro
Amazon Email ScraperPublic contact emails from Amazon
Best Buy Seller Email ScraperPublic contact emails from Best Buy
BigCommerce Store Email ScraperPublic contact emails from BigCommerce Store
Cdiscount Email ScraperPublic contact emails from Cdiscount
Depop Email ScraperPublic contact emails from Depop
DHgate Email ScraperPublic contact emails from DHgate
eBay Email ScraperPublic contact emails from eBay
Ecwid Store Email ScraperPublic contact emails from Ecwid Store
Etsy Email ScraperPublic contact emails from Etsy
Faire Email ScraperPublic contact emails from Faire
Flipkart Email ScraperPublic contact emails from Flipkart
Home Depot Seller Email ScraperPublic contact emails from Home Depot
JD.com Email ScraperPublic contact emails from JD.com
Lazada Email ScraperPublic contact emails from Lazada
Lowe's Seller Email ScraperPublic contact emails from Lowe's
MercadoLibre Email ScraperPublic contact emails from MercadoLibre
Mercari Email ScraperPublic contact emails from Mercari
Newegg Email ScraperPublic contact emails from Newegg
Otto Email ScraperPublic contact emails from Otto
Overstock Email ScraperPublic contact emails from Overstock
Poshmark Email ScraperPublic contact emails from Poshmark
Rakuten Email ScraperPublic contact emails from Rakuten
Shopee Email ScraperPublic contact emails from Shopee
Shopify Store Email ScraperPublic contact emails from Shopify Store
Taobao Email ScraperPublic contact emails from Taobao
Target Seller Email ScraperPublic contact emails from Target
Temu Email ScraperPublic contact emails from Temu
Tmall Email ScraperPublic contact emails from Tmall
Vinted Email ScraperPublic contact emails from Vinted
Walmart Email ScraperPublic contact emails from Walmart
Wayfair Email ScraperPublic contact emails from Wayfair
Wish Email ScraperPublic contact emails from Wish
Wix Stores Email ScraperPublic contact emails from Wix Stores
WooCommerce Email ScraperPublic contact emails from WooCommerce
Zalando Email ScraperPublic contact emails from Zalando
AliExpress Email and Phone Number ScraperEmails and phone numbers from AliExpress
Allegro Email and Phone Number ScraperEmails and phone numbers from Allegro
Amazon Email and Phone Number ScraperEmails and phone numbers from Amazon

Coupang Email Scraper limitations

Read these before planning anything around the output.

  • Coupang exposes few indexable seller pages, so expect low volume. This is the defining limitation of the Coupang Email Scraper and the reason every recommendation above is conservative.
  • Weak account identity. In an internal test run only 3 of 10 rows carried a usable accountName or fullName. Expect emails with thin context.
  • Publicly indexed emails only. The Coupang Email Scraper finds addresses already visible in Google's index. Anything behind the Wing seller console or an in-app contact flow is unreachable.
  • Google's ~300-result cap. A single query returns roughly 300 results at most, which is why expandQueries defaults to true.
  • possiblyTruncated. When true, Google's snippet ellipsis touched the email and it may be cut off. Verify before sending.
  • username and profileUrl are frequently empty. Where they are populated, the link is a product URL rather than a seller storefront, because Coupang does not generally expose one. That is a Google and platform limitation, not a bug.
  • Apify GOOGLE_SERP proxy required. The Coupang Email Scraper cannot run without Apify proxy credentials.
  • Free-plan cap. Free Apify plans stop at 100 emails per run. Paid plans are uncapped.
  • No guaranteed volume. Results vary with keywords, domains, location and Google's index on the day.
  • Not affiliated with Coupang. This is an independent tool, not supported, endorsed by or connected to Coupang.

Coupang Email Scraper FAQ

Common questions about the Coupang Email Scraper, its inputs and its output.

How many results should I expect from the Coupang Email Scraper?

Few. Coupang exposes few indexable seller pages, so expect low volume, and in an internal test only 3 of 10 rows carried a usable account identity. Treat it as a supplementary source rather than a primary lead engine.

Why is the yield lower than on European marketplaces?

Coupang is app-first and heavily first-party, its seller tools sit behind a login, and Google is not the dominant search engine in South Korea. Fewer public seller pages are indexed, so there is less for the Coupang Email Scraper to read.

Does the Coupang Email Scraper log into Coupang?

No. It never logs in, never calls a Coupang API and never opens coupang.com in a browser. It reads Google results through the Apify GOOGLE_SERP proxy.

Should I use Korean or English keywords?

Korean. Try 판매자, 브랜드, 제조사 and 도매 with 문의 and 연락처 as modifiers. The shipped English defaults are a starting point, not the best configuration for a Korean-language domain.

What should I set countryCode to?

KR. Google personalises results by country, and a Korean vantage point is what surfaces coupang.com pages at all.

Which email domains work best for Coupang?

Start with @naver.com, @daum.net and @gmail.com. @hanmail.net and @nate.com are worth testing. These are suggestions based on Korean market habits, not guarantees.

Whose emails am I actually finding?

Mostly supplier, brand and business contacts that happen to appear on Coupang's indexable pages — not marketplace-seller inboxes at scale. Set expectations accordingly.

Because Coupang does not generally expose a public seller storefront URL. When a handle is available, the canonical link the Coupang Email Scraper can build is https://www.coupang.com/vp/products/{id}.

Does the Coupang Email Scraper verify deliverability?

No. It extracts and normalises what Google indexed. Check rows flagged possiblyTruncated before using them.

Can I resume an interrupted run?

Yes. State lives in the key-value store keyed by a hash of your input, with saves on Apify's PERSIST_STATE, MIGRATING and ABORTING events.

What happens when Google blocks a request?

Block, CAPTCHA and consent pages are detected rather than treated as empty. Pages get up to three attempts with exponential backoff, and failed queries are re-queued once at the end of the run.

The Coupang Email Scraper only reads publicly indexed Google results. Whether you may then contact those addresses is a separate PIPA — and possibly GDPR — question. See the responsible use section and take your own legal advice.

Leave a review

If the Coupang Email Scraper saved you time, please leave a star rating and a short review on the Actor page.

Reviews are how other buyers judge whether a tool works, and they tell us which features to build next.

If something did not work, email neurodata.apify@gmail.com instead - bugs get fixed faster than they get complained about.

Support

Questions, a bug, or you need a custom build of the Coupang Email Scraper? Contact neurodata.apify@gmail.com.