Unreal Engine Marketplace Email Scraper

Unreal Engine Marketplace Email Scraper - extract seller support emails from Unreal and Fab results

The Unreal Engine Marketplace Email Scraper is an Apify Actor that collects publicly indexed contact emails tied to Unreal Engine marketplace listings. You supply keywords, optional location and the email domains you care about, and it returns a dataset of game-asset leads.

Read this first, because it shapes everything below. The Unreal/Fab marketplace indexes asset listings rather than seller profiles, so most rows carry a support email and product name without a seller handle. You get a real, contactable address and a product page; you usually do not get a resolved seller account.

The Unreal Engine Marketplace Email Scraper searches both unrealengine.com and fab.com, because the marketplace moved to Fab. Older listings, blog posts and documentation still live under the Unreal domain, while current storefront pages sit on Fab.

What the Unreal Engine Marketplace Email Scraper actually reads

The Unreal Engine Marketplace Email Scraper reads only what Google has already indexed on those two domains. It builds Google queries with the site: operator, fetches result pages through the Apify GOOGLE_SERP proxy, and pulls emails out of titles and snippets.

It does not log into Fab or Epic, call any Epic Games API, or open the marketplace website. There is no browser, no JavaScript rendering, no authentication and no cookies.

A support address written into a product's description is reachable here only because Google indexed that description - not because the Actor crawled the storefront.

Who the Unreal Engine Marketplace Email Scraper is built for

Game studios sourcing environment art and VFX, technical-art outsourcing shops, plugin vendors looking for integration partners, and publishers scouting creators all want the same thing: a repeatable way to turn an asset category into contactable sellers.

Set expectations accordingly. Because the marketplace indexes listings rather than seller profiles, the Unreal Engine Marketplace Email Scraper is best treated as a product-and-support-address finder, not a seller-directory builder.

---

Key features of the Unreal Engine Marketplace Email Scraper

Feature	What it does
Dual-domain site: dorking	Queries both unrealengine.com and fab.com through the Apify GOOGLE_SERP proxy
Query expansion	Runs base, quoted and intitle: variants plus one variant per query modifier; base queries run first
Domain-filtered extraction	Keeps only emails ending in your customDomains values
Global deduplication	One row per unique email across every query and every page of the run
Obfuscation handling	Understands name [at] domain [dot] com, name (at) domain, name @ domain.com, domain .com, zero-width characters and the full-width ＠
Junk filter	Rejects placeholders such as email@, yourname@, test@, xxx@ and single-character locals
Boundary-correct matching	@gmail.com never matches inside @gmail.company or @gmail.com.br
Soft-wrap repair	Drops a hit that is only the tail of another email in the same result block
Structural parsing	Locates the <h3> title then the smallest surrounding block, instead of relying on Google's CSS class names
Locale path handling	Skips the marketplace's language path segments (en, de, fr, pt...) when resolving a handle
Whole-page fallback	If Google's markup changes, the run degrades to "emails without account details" rather than "no emails"
Block detection	CAPTCHA, "unusual traffic" and consent pages are detected and retried, not counted as empty
Retries and backoff	Up to 3 attempts per page with exponential backoff and a fresh proxy session per request
Requeue of failures	Blocked or failed queries are re-queued once at the end of the run
Async concurrency	An asyncio worker pool with a shared stop signal on maxEmails
Resumable state	Progress is stored in the key-value store keyed by a hash of the input, with throttled saves plus saves on PERSIST_STATE, MIGRATING and ABORTING
Streaming output	Every lead is pushed to the dataset immediately, so partial results survive an abort
Run summary	Logs pages fetched, blocked pages, retries and emails per page

---

How the Unreal Engine Marketplace Email Scraper works

The pipeline behind the Unreal Engine Marketplace Email Scraper is deliberately simple, which is why it runs quickly and is hard to break.

1. The Unreal Engine Marketplace Email Scraper reads your input: keywords, location, email domains and limits.
2. It builds Google queries with the site: operator, for example site:fab.com asset seller "@gmail.com".
3. It fetches Google result pages asynchronously through the Apify GOOGLE_SERP proxy using aiohttp.
4. It parses each result block structurally, finding the <h3> title and the smallest block around it.
5. It extracts emails from the block text with a domain-filtered regex.
6. It deduplicates globally and pushes each lead straight to the Apify dataset.

Why two domains matter

Epic retired the standalone Unreal Engine Marketplace and moved selling to Fab, so the public footprint of this ecosystem is split across two hosts.

Querying only one host would miss half the index. The Unreal Engine Marketplace Email Scraper covers both, and the network field on every row reads Unreal Engine Marketplace regardless of which host the result came from.

Why query expansion exists

Google caps a single query at roughly 300 results, so one query has a hard ceiling no matter how many pages you allow.

Query expansion is how the Unreal Engine Marketplace Email Scraper gets past it: each keyword is combined with each email domain in several phrasings, and every variant carries its own result budget.

The default queryModifiers are email, contact, support, developer and publisher - the words that sit next to an address on a marketplace listing.

What the Unreal Engine Marketplace Email Scraper does not do

It does not log into Fab, use an Epic Games API, render JavaScript, read sales or review data, or reach anything that is not already public in Google's index.

It is an independent Apify Actor and is not affiliated with, supported by or endorsed by Epic Games.

---

Unreal Engine Marketplace Email Scraper input fields

Every field the Unreal Engine Marketplace Email Scraper accepts is optional except keywords. Defaults are exactly those shipped in the Actor's input schema.

Field	Type	Default	Meaning
keywords	array (required)	["asset seller", "game developer"]	Search terms describing the marketplace listings or sellers you want
location	string	""	Optional location phrase added to every query
customDomains	array	["@gmail.com", "@yahoo.com"]	Only emails on these domains are kept; the leading @ is optional
maxEmails	integer 1-10000	20	Stop after this many unique emails
countryCode	string	""	Two-letter country for the search proxy (US, GB, DE...)
expandQueries	boolean	true	Search each keyword x domain pair in several phrasings
queryModifiers	array	["email", "contact", "support", "developer", "publisher"]	Extra words combined with each keyword when expansion is on
maxPagesPerQuery	integer 1-50	30	Page cap per query
maxConcurrency	integer 1-20	5	Parallel queries

Example Unreal Engine Marketplace Email Scraper input

{
  "keywords": ["environment asset seller", "niagara vfx pack", "blueprint plugin developer"],
  "location": "",
  "customDomains": ["@gmail.com", "@outlook.com"],
  "maxEmails": 300,
  "countryCode": "US",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "support", "developer", "publisher"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}

Tuning the Unreal Engine Marketplace Email Scraper for better yield

Product language beats people language when you feed the Unreal Engine Marketplace Email Scraper. niagara vfx pack, landscape auto material, modular sci-fi environment and animation blueprint mirror how listings are titled, so they surface far more indexed pages than seller.

Add more email domains before adding more keywords. Each extra domain multiplies the number of distinct queries, and each query brings its own result budget.

Leave expandQueries on and expect to run wider here than on other platforms in this family, because this marketplace publishes fewer contact addresses in its indexed text.

---

Unreal Engine Marketplace Email Scraper output fields

Every dataset item the Unreal Engine Marketplace Email Scraper produces carries all 14 fields below. Fields are never dropped; they are empty or null when Google did not expose the value.

Field	Meaning
network	Platform name
keyword	The keyword that produced the lead
query	The exact Google query used
title	Raw result title
accountName	Account label Google prints (seller handle, studio name, or a product label)
fullName	Display name parsed from a profile-style title; empty for listing titles
username	URL-safe seller handle when one is exposed; otherwise null
profileUrl	Canonical https://www.fab.com/sellers/{username} URL when a handle is known; otherwise empty
url	Direct platform link when exposed, else the profile URL
description	Listing or bio snippet, cleaned of labels and engagement counters
email	Lower-cased email address
emailDomain	The matched domain, for example @gmail.com
possiblyTruncated	true when Google's snippet ellipsis touched the email - verify before sending
foundAt	ISO 8601 UTC timestamp

Example Unreal Engine Marketplace Email Scraper output

[
  {
    "network": "Unreal Engine Marketplace",
    "keyword": "niagara vfx pack",
    "query": "site:fab.com niagara vfx pack support \"@gmail.com\"",
    "title": "Stylised Niagara VFX Pack - Fab",
    "accountName": "Stylised Niagara VFX Pack",
    "fullName": "",
    "username": null,
    "profileUrl": "",
    "url": "https://www.fab.com/listings/stylised-niagara-vfx-pack",
    "description": "60 stylised Niagara systems for UE5. Support and custom requests: emberline.vfx@gmail.com",
    "email": "emberline.vfx@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T09:14:22.481Z"
  },
  {
    "network": "Unreal Engine Marketplace",
    "keyword": "blueprint plugin developer",
    "query": "site:unrealengine.com blueprint plugin developer contact \"@outlook.com\"",
    "title": "Save System Pro - documentation and support",
    "accountName": "Save System Pro",
    "fullName": "",
    "username": null,
    "profileUrl": "",
    "url": "https://www.unrealengine.com/marketplace/en-US/product/save-system-pro",
    "description": "Blueprint-only save framework. Documentation, roadmap and support requests to northgate.plugins@outlook ...",
    "email": "northgate.plugins@outlook.com",
    "emailDomain": "@outlook.com",
    "possiblyTruncated": true,
    "foundAt": "2026-08-31T09:14:29.113Z"
  },
  {
    "network": "Unreal Engine Marketplace",
    "keyword": "environment asset seller",
    "query": "site:fab.com intitle:\"environment\" seller email \"@gmail.com\"",
    "title": "Ridgeline Studio - Seller Profile - Fab",
    "accountName": "ridgeline-studio",
    "fullName": "Ridgeline Studio",
    "username": "ridgeline-studio",
    "profileUrl": "https://www.fab.com/sellers/ridgeline-studio",
    "url": "https://www.fab.com/sellers/ridgeline-studio",
    "description": "Modular environments and props for UE5. Business enquiries: ridgeline.studio.art@gmail.com",
    "email": "ridgeline.studio.art@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T09:15:03.902Z"
  }
]

The first two rows are the typical shape of Unreal Engine Marketplace Email Scraper output, not the exception: a product page carries a real support address with username: null and an empty profileUrl. The third row - a resolved seller profile - is the minority case.

---

Use cases for the Unreal Engine Marketplace Email Scraper

Use case	How the Unreal Engine Marketplace Email Scraper helps
Game asset lead generation	Build a contact list of asset and plugin creators by category
Outsourcing and art services	Reach creators whose listings suggest capacity for contract environment or character work
Tools and middleware sales	Contact plugin vendors already selling into the Unreal ecosystem
Bundle and store curation	Shortlist products for a themed bundle and write to the published support address
Publisher and studio scouting	Find small teams shipping polished UE content and open a conversation
Support-channel research	Map which listings publish a direct address instead of a marketplace form
Category and pricing research	Sample a category's listings, descriptions and contact practices in one dataset
Partner recruitment	Assemble candidates for an integration, marketplace or affiliate programme

Working with product-level leads

Because most Unreal Engine Marketplace Email Scraper rows come from listings, treat url and description as your qualification signal rather than profileUrl. The product page tells you what the seller makes and who the address belongs to.

Write to the product, not to a name you do not have. "About your Niagara pack" lands better than a generic greeting when the row has no seller handle.

Covering both engines and the wider asset ecosystem

Asset creators rarely sell on one storefront. Pair the Unreal Engine Marketplace Email Scraper with the Unity Asset Store Email Scraper for cross-engine coverage, and with the Figma Community Email Scraper when you also want UI and design assets.

---

Expected results from the Unreal Engine Marketplace Email Scraper

Be realistic about this one. In live test runs against Google, roughly 2 out of 10 parsed results carried an account identity - the weakest identity yield of the seven marketplace and developer Actors in this group.

The reason is structural, not a defect: the Unreal/Fab marketplace indexes asset listings rather than seller profiles, so most rows carry a support email and product name without a seller handle.

Those rows are still leads. They carry email, emailDomain, url, description and query - enough to write a specific, relevant message. If your workflow depends on resolved account handles, the CodePen Email Scraper or Hashnode Email Scraper will fit that need far better.

---

Limitations of the Unreal Engine Marketplace Email Scraper

Read this before planning a campaign around Unreal Engine Marketplace Email Scraper output.

• Listings, not sellers. The Unreal/Fab marketplace indexes asset listings rather than seller profiles, so most rows carry a support email and product name without a seller handle. This is the defining limitation of this Actor.
• Publicly indexed emails only. The Unreal Engine Marketplace Email Scraper finds an address only when it is already visible in Google's index. Contact routed exclusively through Fab's on-site support forms is out of reach.
• Google's ~300-result cap. A single query returns roughly 300 results maximum, which is exactly why expandQueries exists and why turning it off reduces volume further.
• possiblyTruncated. When this is true, Google's snippet ellipsis touched the email and it may be cut off. Verify those rows before sending anything.
• username and profileUrl are often empty. They are populated only when a seller handle appears in the result, which on this platform is the minority case.
• Apify GOOGLE_SERP proxy required. The Actor cannot run without Apify proxy credentials.
• Free plan cap. Free Apify plans are limited to 100 emails per run. Paid plans are uncapped.
• Variable results. Output depends on keywords, domains, location and Google's index, and the Unreal-to-Fab migration is still reshaping what is indexed. No yield is guaranteed.

---

Responsible use

Support addresses on marketplace listings are published for product correspondence - bug reports, licensing questions, custom work enquiries. Treat them that way.

If you contact people in the EU or UK, GDPR applies: have a lawful basis, identify yourself, say where you found the address, and honour opt-outs immediately. Respect Epic's community norms and any stated contact preference on a listing.

Because these are support inboxes, a bulk send is unusually damaging here - you are interrupting a channel customers rely on.

---

Unreal Engine Marketplace Email Scraper FAQ

Why do so many rows have username: null?

The Unreal/Fab marketplace indexes asset listings rather than seller profiles, so most rows carry a support email and product name without a seller handle. It is the expected shape of the data on this platform, not a parsing failure.

Which domains does the Unreal Engine Marketplace Email Scraper search?

Both unrealengine.com and fab.com, because the marketplace moved to Fab and the public footprint is split across the two hosts.

Does the Unreal Engine Marketplace Email Scraper use an Epic Games API?

No. It parses Google search results for pages Google has already indexed. There is no API call, no login and no page fetch against the marketplace itself.

Does it need a Fab or Epic account?

No. There is no authentication, no browser, no JavaScript rendering and no cookies. The only credential required is your Apify account's GOOGLE_SERP proxy access.

Where do the emails the Unreal Engine Marketplace Email Scraper returns come from?

From the text Google prints in result titles and snippets - the support section of listing descriptions, documentation notes, and the minority of seller profiles that expose an address.

How many emails can the Unreal Engine Marketplace Email Scraper return?

maxEmails accepts 1 to 10000 and defaults to 20. Free Apify plans are capped at 100 emails per run; paid plans are uncapped. Volume depends on your keywords and domains.

What does possiblyTruncated: true mean?

Google's snippet ellipsis touched the email, so the address may be incomplete. Verify those rows before you use them.

Can I restrict the Unreal Engine Marketplace Email Scraper to company domains?

Yes. Put the domains you want in customDomains, for example ["@studio.com", "@example.io"]. Only emails ending in those domains are kept, and the leading @ is optional.

Does it handle obfuscated addresses like name [at] gmail [dot] com?

Yes. The extractor normalises [at], (at), spaced @, spaced .com, zero-width characters and the full-width ＠, and it filters placeholders such as test@ and yourname@.

Can I target a specific country?

Set countryCode to a two-letter code such as US, GB or DE to steer the search proxy, and put a city or region in location to append it to every query.

What happens if an Unreal Engine Marketplace Email Scraper run is interrupted?

Progress is saved in the key-value store keyed by a hash of your input, with saves on PERSIST_STATE, MIGRATING and ABORTING. Leads are pushed to the dataset as they are found, so nothing already collected is lost.

Is the Unreal Engine Marketplace Email Scraper affiliated with Epic Games?

No. It is an independent Apify Actor, and it is not supported, endorsed or affiliated with Epic Games, Fab or Unreal Engine.

---

Related Actors

The Unreal Engine Marketplace Email Scraper belongs to a Developer & Technology family of Apify Actors that all work the same way on different platforms. Run several to cover an ecosystem instead of a single site.

Actor	What it collects
App Store Email Scraper	Public contact emails from App Store
Atlassian Marketplace Email Scraper	Public contact emails from Atlassian Marketplace
Bitbucket Email Scraper	Public contact emails from Bitbucket
Chrome Web Store Email Scraper	Public contact emails from Chrome Web Store
CodePen Email Scraper	Public contact emails from CodePen
Confluence Email Scraper	Public contact emails from Confluence
Dev.to Email Scraper	Public contact emails from DEV Community
Docker Hub Email Scraper	Public contact emails from Docker Hub
Figma Community Email Scraper	Public contact emails from Figma Community
Firefox Add-ons Email Scraper	Public contact emails from Firefox Add-ons
GitHub Email Scraper	Public contact emails from GitHub
GitLab Email Scraper	Public contact emails from GitLab
Google Play Email Scraper	Public contact emails from Google Play
Hashnode Email Scraper	Public contact emails from Hashnode
HubSpot Marketplace Email Scraper	Public contact emails from HubSpot Marketplace
Hugging Face Email Scraper	Public contact emails from Hugging Face
Jira Email Scraper	Public contact emails from Jira
Maven Central Email Scraper	Public contact emails from Maven Central
Microsoft AppSource Email Scraper	Public contact emails from Microsoft AppSource
Salesforce AppExchange Email Scraper	Public contact emails from Salesforce AppExchange
Shopify App Store Email Scraper	Public contact emails from Shopify App Store
Slack App Directory Email Scraper	Public contact emails from Slack App Directory
SourceForge Email Scraper	Public contact emails from SourceForge
Stack Overflow Email Scraper	Public contact emails from Stack Overflow
Unity Asset Store Email Scraper	Public contact emails from Unity Asset Store
WordPress Plugin Directory Email Scraper	Public contact emails from WordPress Plugin Directory
WordPress Theme Directory Email Scraper	Public contact emails from WordPress Theme Directory
Zapier App Directory Email Scraper	Public contact emails from Zapier App Directory
App Store Email and Phone Number Scraper	Emails and phone numbers from App Store
Atlassian Marketplace Email and Phone Number Scraper	Emails and phone numbers from Atlassian Marketplace
Bitbucket Email and Phone Number Scraper	Emails and phone numbers from Bitbucket
Chrome Web Store Email and Phone Number Scraper	Emails and phone numbers from Chrome Web Store
CodePen Email and Phone Number Scraper	Emails and phone numbers from CodePen
Confluence Email and Phone Number Scraper	Emails and phone numbers from Confluence
DEV Community Email and Phone Number Scraper	Emails and phone numbers from DEV Community
Docker Hub Email and Phone Number Scraper	Emails and phone numbers from Docker Hub
Figma Community Email and Phone Number Scraper	Emails and phone numbers from Figma Community
Firefox Add-ons Email and Phone Number Scraper	Emails and phone numbers from Firefox Add-ons
GitHub Email and Phone Number Scraper	Emails and phone numbers from GitHub
GitLab Email and Phone Number Scraper	Emails and phone numbers from GitLab
Google Play Email and Phone Number Scraper	Emails and phone numbers from Google Play
Hashnode Email and Phone Number Scraper	Emails and phone numbers from Hashnode

Leave a review

If the Unreal Engine Marketplace 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 a custom build of the Unreal Engine Marketplace Email Scraper for your own domain list? Email neurodata.apify@gmail.com and we will get back to you.