Google Play Email Scraper with Phone Number and Website

Google Play Email Scraper With Phone Number & Website 📱

Turn any keyword into a clean list of Android app developer leads — the developer's email, phone number and website, straight from the public Google Play app listings that match your search.

The plain Google Play email scraper stops at the email address. This one goes one step further: for every listing it finds, it opens that app's own listing page and reads the developer-contact section Google Play requires every publisher to fill in — the section that carries the published support phone, the published website, and (for apps distributed in the EU) the verified trader contact. That is why this actor returns real phone numbers and real websites where a search-text-only scraper returns almost none.

Built for B2B lead generation, agency prospecting, app-market research and partner outreach — a no-code Google Play scraper that exports to JSON, CSV, Excel or an API feed.

Extractable Data Table 📊

Data point	Field	Notes
Store / network	network	Always play.google.com
Search keyword	keyword	The keyword the row came from
App listing title	title	As shown on the result
Listing summary	description	Short description text, up to 500 chars
App listing URL	url	Direct link to the /store/apps/details page
Developer email	email	The address published on the listing
Developer phone number	phoneNumber	International format, e.g. +441564393118
Where the phone came from	phoneSource	listing_page or result_summary
Developer website	website	Absolute URL
What kind of website	websiteType	own_domain, link_aggregator or platform_profile
Contact provenance	contactSource	listing_page, result_summary, both or none

Every field is either a value the developer actually published or null. Nothing is guessed, reconstructed or filled with a placeholder.

Key Features of the Google Play Email, Phone & Website Scraper

• 📧 Email extraction, unchanged — the same email-scraping behaviour the plain Google Play email scraper has, with the same emailDomains filter (@gmail.com, @outlook.com, your own company domains, or all domains).
• ☎️ Developer phone numbers — read from the app's published contact section, already carrying their own international dial code. Coverage measured live at 42–72% of collected rows, depending on how business-oriented the keyword is.
• 🌐 Developer websites — read from the same section, measured live at 45–72% of collected rows. Store infrastructure, link shorteners, APK mirrors and free-mail domains are filtered out.
• 🏷️ Website quality labelling — a real company domain, a bio-link page and a rented social profile are three different things for a lead list, so they are labelled own_domain, link_aggregator and platform_profile instead of being silently merged.
• 🛡️ Strict phone verification (on by default) — only numbers published with their own international prefix are kept. In live testing that scored 11/11 correct with zero false positives; switch it off to also accept locally-written numbers.
• 🌍 194-country dial-code list — for the relaxed mode, tell the actor which country locally-written numbers belong to.
• 🔢 Per-keyword lookup cap — control how many listings get the deeper contact lookup, so you can trade run time against coverage.
• ⚡ Real-time output — every row lands in the dataset the moment it is collected; you can watch the table fill and stop the run whenever you have enough.
• 🧾 Honest provenance per row — phoneSource and contactSource tell you exactly where each row's contact data came from.
• 🔁 Backward compatible — every input and every output column of the plain Google Play email scraper still works and still appears, with the same values.

How to use the Google Play Email, Phone & Website Scraper 🚀

1. Open the actor and type one or more keywords (e.g. restaurant, gym, productivity, salon booking).
2. Optionally set an email domain filter and a location.
3. Choose how many results per keyword you want.
4. Leave Read each app's own contact section ON — that is what fills the phone and website columns.
5. Press Start, then watch the Output table fill in real time.
6. Export the dataset as JSON, CSV, Excel or XML, or pull it through the Apify API.

💡 Keyword tip that materially changes your results: business-flavoured keywords (restaurant, gym, salon booking, delivery) return far more phone numbers and websites than hobby-app keywords (productivity, wallpaper, puzzle), because business publishers are the ones who fill in a phone number and a company domain. Measured on the same run configuration: restaurant returned 8/10 phones and 6/10 websites, productivity returned 3/10 and 2/10.

Use Cases 🎯

• B2B lead generation — build outreach lists of app publishers with a verified email, phone and domain.
• Agency prospecting — find businesses that already ship an app and can be pitched on marketing, ASO or a rebuild.
• App market research — map who publishes in a category and where they are based.
• Partnership and BD sourcing — reach the right developer directly instead of through a store contact form.
• Competitive intelligence — see which competitors publish a real company domain and which hide behind a bio-link page.
• CRM enrichment — attach a phone number and website to app-developer records you already hold.
• Recruitment sourcing — find small studios and independent Android developers by category.

Why choose this Google Play scraper 💎

• The contact section, not just the search text. Reading the listing's own developer-contact block is the difference between a phone column that is 15% populated and one that is 42–72% populated.
• Numbers you can dial. A published international number is used exactly as published — the actor never bolts a country code onto a bare local number in strict mode.
• null over noise. A missing phone is empty, never a placeholder, never a fabricated value.
• Filtered websites. play.google.com, gmail.com, shorteners, APK mirrors and ads.txt redirector domains never show up as somebody's "website".
• Nothing removed. This is a strict superset of the plain Google Play email scraper — same inputs, same outputs, plus three contact columns and two provenance columns.

Scalability 📈

maxEmails accepts up to 100,000 results per keyword and you can queue as many keywords as you like in one run. The contact lookup adds one additional page lookup per collected row, so a 10-result run does roughly 10 extra lookups on top of the discovery pages — expect it to take noticeably longer than a plain email scrape. Use Max listings to look up per keyword to cap that cost, or switch the lookup off entirely for the fastest possible email-only run.

Legal Guidelines ⚖️

This actor collects only publicly published business-contact information that app developers themselves put on their public Google Play listing — the same details any visitor sees on the page. It does not log in, does not bypass any access control, and does not touch private user data.

You are responsible for how you use the output. Comply with GDPR, CAN-SPAM, PECR and any other regulation that applies to you, honour opt-outs, and use the data for legitimate business purposes only.

Input Parameters 🧩

Field	Key	Type	Default	What it does
🔍 Keywords	keywords	array	["productivity"]	Required. One or more search keywords.
🌐 Platform	platform	select	Google-Play	The store to scrape.
📍 Location Filter	location	string	""	Narrows results to listings mentioning a place.
📧 Email Domains Filter	emailDomains	array	["@gmail.com"]	Keep only emails on these domains. Empty = all domains.
📊 Maximum Results per Keyword	maxEmails	integer	10	1 – 100,000.
📞 Add a phone number column	collectDeveloperPhone	boolean	true	Turns the phoneNumber / phoneSource columns on.
🌍 Country for locally-written numbers	developerPhoneCountry	select	United Kingdom (+44)	194 countries. Only used for numbers written without a +.
🛡️ Strict phone verification	strictPhoneVerification	boolean	true	ON keeps only numbers published with an international prefix.
🌐 Add a website column	collectDeveloperWebsite	boolean	true	Turns the website / websiteType columns on.
🏢 Read each app's own contact section	openListingPageForContacts	boolean	true	The high-coverage lane. One extra lookup per result.
🔢 Max listings to look up per keyword	maxListingPagesPerKeyword	integer	50	1 – 1000. Caps the lookup cost.
⚙️ Extraction Engine	engine	select	legacy	Selects the result-parsing pipeline.
🛡️ Proxy Configuration	proxyConfiguration	object	auto	Advanced network settings for the discovery side.

Input example

{
  "keywords": ["restaurant", "gym"],
  "platform": "Google-Play",
  "location": "",
  "emailDomains": ["@gmail.com"],
  "maxEmails": 10,
  "collectDeveloperPhone": true,
  "developerPhoneCountry": "United Kingdom (+44)",
  "strictPhoneVerification": true,
  "collectDeveloperWebsite": true,
  "openListingPageForContacts": true,
  "maxListingPagesPerKeyword": 50,
  "engine": "legacy"
}

Output Format 📤

{
  "network": "play.google.com",
  "keyword": "restaurant",
  "title": "Total X Software - Restaurant POS",
  "description": "Restaurant billing and order management app ...",
  "url": "https://play.google.com/store/apps/details?id=com.totalx.pos",
  "email": "totalxsoftware@gmail.com",
  "phoneNumber": "+917902524202",
  "phoneSource": "listing_page",
  "website": "https://totalx.in",
  "websiteType": "own_domain",
  "contactSource": "listing_page"
}

A row where the developer published no phone and no website looks like this — empty, never faked:

{
  "network": "play.google.com",
  "keyword": "productivity",
  "title": "Daily Task Planner",
  "description": "Simple to-do and habit tracker ...",
  "url": "https://play.google.com/store/apps/details?id=com.example.planner",
  "email": "froslaud@gmail.com",
  "phoneNumber": null,
  "phoneSource": null,
  "website": null,
  "websiteType": null,
  "contactSource": "none"
}

Output Table

Field	Type	Always present?	Description
network	string	yes	play.google.com
keyword	string	yes	Keyword that produced the row
title	string	yes	App listing title
description	string	yes	Listing summary text (max 500 chars)
url	string	yes	App listing URL
email	string	yes	Developer email published on the listing
phoneNumber	string | null	nullable	International-format phone number
phoneSource	string | null	nullable	listing_page or result_summary
website	string | null	nullable	Developer website URL
websiteType	string | null	nullable	own_domain / link_aggregator / platform_profile
contactSource	string	yes	listing_page / result_summary / both / none

The dataset ships with two table views: Emails, Phones & Websites (all 11 columns) and Contact Details Only (the seven columns a lead list actually needs).

FAQ ❓

What is the Google Play Email Scraper With Phone Number & Website?

It is a Google Play scraper that searches public app listings by keyword and returns the app developer's email address, phone number and website as structured rows you can export or pull through an API.

How does it find phone numbers for Android app developers?

Google Play requires every publisher to fill in a developer-contact section on the app's own listing, and apps distributed in the EU additionally publish a verified trader contact. The actor reads that published section for each result.

How complete is the phone number data?

Measured live: 42–72% of collected rows carry a phone number, and the spread is driven by the keyword. Business categories (restaurant, gym, salon, delivery) sit at the top of that range; hobby-app categories (productivity, wallpapers, puzzles) sit at the bottom. Rows without a published number are returned with phoneNumber: null.

How complete is the website data?

45–72% of collected rows, with the same keyword-driven spread. Store infrastructure, free-mail domains, link shorteners, APK mirrors and ads.txt redirector domains are filtered out rather than reported as websites.

Why is websiteType useful?

Because https://acme-software.com, https://linktr.ee/acme and https://facebook.com/acme are very different leads. own_domain means the developer has a real site of their own; link_aggregator and platform_profile tell you they do not.

What is strict phone verification?

With it ON (the default) the actor keeps only numbers that were published with their own international prefix, which is the safest possible reading of a phone number. With it OFF it will also accept a locally-written number and apply the dial code of the country you selected — higher hit rate, slightly higher risk.

Does this actor still do everything the plain Google Play email scraper does?

Yes. Every input key and every output column of the plain email scraper is present, with the same names and the same values. The contact columns are added on top.

Does the contact lookup slow the run down?

Yes, and that is stated up front: it performs one additional page lookup per collected row. A 10-result run does about 10 extra lookups. Cap it with Max listings to look up per keyword, or turn the lookup off for a fast email-only run.

Can I scrape multiple keywords and categories in one run?

Yes. keywords accepts a list, and each keyword is processed with its own result budget.

Can I filter to business email domains only?

Yes. Put your target domains in emailDomains (e.g. ["@yourclient.com", "@outlook.com"]), or leave it empty to collect every domain.

What export formats are supported?

JSON, CSV, Excel, XML and HTML from the Apify Console, plus the Apify API and integrations (Google Sheets, Slack, webhooks, Make, Zapier).

Do I need any technical skills?

No. It is a no-code form: type keywords, press Start, export the table.

Is the data collected legally?

It is public business-contact information the developer chose to publish on a public store listing. How you subsequently use it is governed by the privacy and marketing laws that apply to you.

Does it work for the Apple App Store too?

No. This actor targets Google Play app listings only.

What happens if a developer published nothing?

The row is still returned with the email that matched your filter, and the phone/website columns are null with contactSource: "none". No placeholder, no invented value.