Firefox Add-ons Scraper — Users, Ratings & Authors (AMO)
Pricing
from $1.50 / 1,000 results
Firefox Add-ons Scraper — Users, Ratings & Authors (AMO)
Scrape Firefox Add-ons (addons.mozilla.org): extensions and themes with name, daily users, weekly downloads, rating and review count, author, category, tags, version and dates. Search, browse by category or top by users. For add-on market intelligence. Not affiliated with Mozilla.
Pricing
from $1.50 / 1,000 results
Rating
0.0
(0)
Developer
Haketa
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
11 days ago
Last modified
Categories
Features
Share
Firefox Add-ons Scraper — Daily Users, Ratings, Authors & Versions (AMO)
Extract comprehensive browser extension and theme intelligence from the official Firefox Add-ons store (addons.mozilla.org / AMO). Collect verified metrics including average daily active users, weekly downloads, star ratings, review counts, author credentials, categories, tags, version histories, and developer contact information — without manual copying, rate-limit bottlenecks, or complex browser setups.
Whether you are sizing a browser extension niche, performing App Store Optimization (ASO), tracking competitor feature cadences, or building developer lead lists, this scraper delivers clean, structured records ready for immediate analysis.
⚡ At a glance
| Feature | Specification |
|---|---|
| Target Website | addons.mozilla.org (Firefox Add-ons / AMO) |
| Data Fields | Name, daily users, weekly downloads, rating, review count, author profiles, emails, versions, URLs |
| Search Capabilities | Keyword search, AMO category browsing, or top-by-adoption discovery |
| Pagination Depth | Unlocked multi-page pagination (1,000+ results across search queries and categories) |
| Default Concurrency | Fast non-blocking HTTP requests with automatic proxy rotation |
| Typical Speed | 50–100 add-on profiles per 15–30 seconds |
| Export Formats | JSON, CSV, Excel (XLSX), XML, HTML Table, RSS |
| Integrations | Make, Zapier, Webhooks, Google Sheets, Airbyte, Keboola, Python, Node.js API |
🔎 Why scrape Firefox Add-ons (AMO)?
The Firefox Add-ons ecosystem powers millions of daily desktop and mobile browser sessions worldwide. While other extension stores hide or obscure critical metrics, AMO provides exceptional transparency into user adoption and satisfaction:
- True Daily Usage Signals: Unlike stores that only report lifetime installs in vague ranges (e.g., "1,000,000+"), AMO reports actual average daily active users (
averageDailyUsers) and weekly downloads (weeklyDownloads), pinpointing true retention. - Competitive Benchmarking: Track competitors in verticals like ad blockers, password managers, privacy shields, AI assistants, developer tooling, and shopping assistants.
- App Store Optimization (ASO): Analyze title patterns, localized summaries, categories, and tags to discover high-ranking keywords in organic search results.
- Developer Lead Generation: Extract verified author identities, profile URLs, and published developer support emails for outreach, developer tooling distribution, and partnership opportunities.
- Due Diligence & Investment: Track version release frequency (
currentVersion,lastUpdated,createdAt) and community satisfaction to evaluate acquisitions or partner integrations.
📊 Extension Store Ecosystem Comparison
| Dimension | Firefox Add-ons (AMO) | Chrome Web Store | Edge Add-ons Store |
|---|---|---|---|
| User Metric Precision | Exact daily active users (averageDailyUsers) | Tiered bucket ranges (e.g. 10,000+) | Rough install tier brackets |
| Download Velocity | Exact weekly downloads (weeklyDownloads) | Not publicly reported | Not publicly reported |
| Developer Contact | Public support email & homepage | Website link only | Support link only |
| Release History | Exact timestamp of last version update | Date only (no exact timestamp) | Date only |
| API Availability | Fast structured endpoints | Scraped HTML required | Limited web view |
| Review Breakdown | Rating count + text review count | Rating count only | Rating count only |
| Category Specificity | Detailed subcategories & custom tags | Top-level categories only | Standard categories |
📊 Key Data Fields & Coverage
Every output item is flattened and normalized for effortless ingestion into relational databases, spreadsheets, and business intelligence dashboards.
🧩 Core Identification & Overview
| Field | Type | Description | Coverage |
|---|---|---|---|
id | string | Unique AMO numeric identifier | 🟢 High (100%) |
slug | string | URL slug for the listing | 🟢 High (100%) |
guid | string | Browser internal extension GUID | 🟢 High (100%) |
name | string | Localized extension or theme title | 🟢 High (100%) |
type | string | Listing type (extension, statictheme, etc.) | 🟢 High (100%) |
summary | string | Short description / pitch text | 🟢 High (98%) |
iconUrl | string | Official icon image URL | 🟢 High (95%) |
url | string | Direct canonical AMO store URL | 🟢 High (100%) |
📈 Adoption & Quality Metrics
| Field | Type | Description | Coverage |
|---|---|---|---|
averageDailyUsers | string | Average daily active users | 🟢 High (100%) |
weeklyDownloads | string | Weekly download velocity | 🟢 High (100%) |
ratingAverage | string | Average star rating (1.0 to 5.0) | 🟢 High (90%) |
ratingCount | string | Total number of star ratings submitted | 🟢 High (100%) |
reviewCount | string | Number of written community reviews | 🟢 High (100%) |
isRecommended | string | Whether certified as recommended / promoted | 🟢 High (100%) |
isExperimental | string | Whether flagged as experimental by author | 🟢 High (100%) |
👨💻 Author & Contact Details
| Field | Type | Description | Coverage |
|---|---|---|---|
authorNames | string | Comma-delimited list of author names | 🟢 High (98%) |
authors | string | JSON array containing author name, username, profile URL | 🟢 High (98%) |
supportEmail | string | Developer support email (where published) | 🟡 Conditional (55–75%) |
homepage | string | Developer / company external website URL | 🟡 Conditional (65–80%) |
supportUrl | string | External support / documentation portal | 🟡 Conditional (50–70%) |
🏷️ Taxonomy & Lifecycle
| Field | Type | Description | Coverage |
|---|---|---|---|
categories | string | Primary and secondary AMO categories | 🟢 High (100%) |
tags | string | Search tags associated with the listing | 🟢 High (85%) |
currentVersion | string | Current deployed version string | 🟢 High (100%) |
createdAt | string | ISO timestamp of original listing creation | 🟢 High (100%) |
lastUpdated | string | ISO timestamp of most recent release update | 🟢 High (100%) |
scrapedAt | string | ISO timestamp when record was extracted | 🟢 High (100%) |
🎯 Detailed Use Cases & Workflows
1. Browser Extension Market Intelligence & Sizing
- Objective: Determine market demand for new browser extension concepts before writing code.
- Workflow: Run the actor across primary competitor keywords (e.g.,
"tab manager","bookmark sync","read later"). AggregateaverageDailyUsersacross the top 100 listings to establish total addressable market (TAM) size and estimate realistic user acquisition targets.
2. App Store Optimization (ASO) & Search Ranking Audit
- Objective: Optimize listing title, summary, categories, and tags to maximize organic discovery on AMO.
- Workflow: Extract all extensions ranking in the top 50 for target search terms. Compare keyword placement in
nameversussummary, evaluate category distribution, and inspect frequenttagsto guide metadata copywriting.
3. Developer Lead Generation & Partner Sourcing
- Objective: Source active software developers and engineering agencies for developer tooling, security audits, or acquisition offers.
- Workflow: Scrape categories like
developer-toolsandprivacy-security. Filter results bysupportEmailpresence, verify project momentum viaweeklyDownloads, and feed enriched leads into outbound CRM campaigns.
4. Continuous Competitor Monitoring & Alerting
- Objective: Stay informed whenever competitors deploy new versions, alter pricing tiers, or experience shifts in user sentiment.
- Workflow: Schedule weekly actor runs on Apify. Use Apify Webhooks or Zapier to detect increases in
reviewCountor changes incurrentVersion, triggering immediate Slack or email alerts.
5. Security & Dependency Auditing
- Objective: Identify abandoned or outdated extensions in enterprise browser fleets.
- Workflow: Ingest internal browser extension GUIDs into a spreadsheet and cross-reference with scraped
lastUpdatedandisRecommendedstatuses to flag deprecated software.
⚙️ Input Configuration & Parameters
The actor is designed for effortless configuration. Running with default parameters immediately collects top-rated add-ons by user adoption.
| Parameter | Type | Default | Description |
|---|---|---|---|
searchTerms | array | ["vpn"] | List of search keywords to query sequentially. Leave empty to browse top listings. |
categories | array | [] | Category slugs to browse (e.g., privacy-security, shopping, search-tools, tabs). |
sort | string | "users" | Sort order: users, rating, created, updated, hotness, or downloads. |
addonType | string | "extension" | Target type: extension, statictheme, dictionary, or language. |
maxItems | integer | 0 | Total records to extract across all queries. 0 = auto/unlimited. |
maxPagesPerQuery | integer | 0 | Maximum pages per search query (50 results per page). 0 = auto/unlimited. |
proxyConfiguration | object | {"useApifyProxy": true} | Proxy configuration. Datacenter proxy is enabled by default. |
📝 Input Configurations for Common Scenarios
Scenario A: Fast Prefill Run (Quick Test)
{"searchTerms": ["vpn"],"sort": "users","maxItems": 50,"maxPagesPerQuery": 0}
Scenario B: Multi-Keyword Privacy Market Sweep
{"searchTerms": ["adblock", "anti tracker", "cookie banner", "privacy guard"],"sort": "users","addonType": "extension","maxItems": 500,"maxPagesPerQuery": 0,"proxyConfiguration": {"useApifyProxy": true}}
Scenario C: Deep Category Extraction (1,000+ Items)
{"categories": ["privacy-security", "developer-tools"],"sort": "downloads","addonType": "extension","maxItems": 2000,"maxPagesPerQuery": 0,"proxyConfiguration": {"useApifyProxy": true}}
Scenario D: Discover Fast-Trending New Tools
{"searchTerms": ["ai", "chatgpt", "llm"],"sort": "hotness","addonType": "extension","maxItems": 300,"maxPagesPerQuery": 0}
📦 Sample Output Record
{"id": 603434,"slug": "browsec","guid": "browsec@browsec.com","name": "Browsec VPN - Free VPN for Firefox","type": "extension","summary": "Protect your IP and encrypt your internet traffic with Browsec VPN. Fast and secure proxy extension.","averageDailyUsers": 498210,"weeklyDownloads": 18450,"ratingAverage": 4.48,"ratingCount": 4210,"reviewCount": 985,"authors": [{"name": "Browsec LLC","username": "browsec-vpn","url": "https://addons.mozilla.org/en-US/firefox/user/browsec-vpn/"}],"authorNames": "Browsec LLC","supportEmail": "support@browsec.com","categories": ["privacy-security"],"tags": ["vpn", "proxy", "privacy", "security", "unblock"],"currentVersion": "3.84.1","createdAt": "2015-04-18T12:00:00Z","lastUpdated": "2026-10-15T09:20:00Z","isRecommended": true,"isExperimental": false,"requiresPayment": false,"homepage": "https://browsec.com","supportUrl": "https://browsec.com/en/help","iconUrl": "https://addons.mozilla.org/user-media/addon_icons/603/603434-64.png","url": "https://addons.mozilla.org/en-US/firefox/addon/browsec/","scrapedAt": "2026-11-10T13:35:00.000Z"}
💻 Programmatic Usage & API Integration
Trigger runs and retrieve results via the official Apify Client in Python, JavaScript, or direct REST API requests.
Python Integration
from apify_client import ApifyClient# Initialize client with your Apify API tokenclient = ApifyClient("YOUR_APIFY_TOKEN")# Prepare actor inputrun_input = {"searchTerms": ["password manager", "authenticator"],"sort": "users","maxItems": 250,"maxPagesPerQuery": 0}# Run actor and wait for completionrun = client.actor("haketa/firefox-addons-scraper").call(run_input=run_input)# Fetch results from default datasetfor item in client.dataset(run["defaultDatasetId"]).iterate_items():print(f"{item['name']} | Daily Users: {item['averageDailyUsers']} | Rating: {item['ratingAverage']}")
Node.js / JavaScript Integration
import { ApifyClient } from 'apify-client';const client = new ApifyClient({token: 'YOUR_APIFY_TOKEN',});const input = {searchTerms: ["ai assistant", "chatgpt"],sort: "hotness",maxItems: 200,maxPagesPerQuery: 0};const run = await client.actor('haketa/firefox-addons-scraper').call(input);const { items } = await client.dataset(run.defaultDatasetId).listItems();items.forEach((addon) => {console.log(`[${addon.slug}] ${addon.name} - ${addon.averageDailyUsers} users (${addon.supportEmail || 'no email'})`);});
Direct REST API Call
curl -X POST "https://api.apify.com/v2/acts/haketa~firefox-addons-scraper/runs?token=YOUR_APIFY_TOKEN" \-H "Content-Type: application/json" \-d '{"searchTerms": ["translator"],"maxItems": 100}'
🔗 Integrations & Data Pipelines
Connect your scraped Firefox Add-ons dataset directly to modern cloud data warehouses and automation platforms:
- Google Sheets: Set up Apify's Google Sheets Integration to append newly discovered extensions directly into a shared team spreadsheet.
- Make (Integromat): Trigger automated scenarios whenever an actor run finishes, piping developer leads directly into HubSpot or Airtable.
- Zapier: Connect new dataset items to Slack channels, Notion databases, or Discord notification channels.
- Airbyte / Fivetran: Ingest tabular dataset endpoints into Snowflake, BigQuery, or Amazon Redshift for long-term historical analysis.
- Webhooks: Configure HTTP POST callbacks upon run completion to sync data immediately into your proprietary backend APIs.
💡 Best Practices & Pro Tips
- Unrestricted Deep Crawling: Set
maxPagesPerQuery: 0to let the crawler paginate as deep as needed untilmaxItemsis satisfied. - Identify Fast Risers: Use
sort: "hotness"to find trending new extensions gaining rapid traction before they reach high total daily users. - B2B Partnership Sourcing: Filter results with
supportEmailpopulated to build direct outreach lists for browser technology providers. - Scheduled Monitoring: Schedule weekly runs on Apify to track adoption shifts and detect when competitors deploy new versions or updates.
- Exporting Options: Download clean CSV/XLSX spreadsheets directly from the Apify Console or stream JSON records into your data warehouse via webhooks.
❓ Frequently Asked Questions
How many add-ons can I extract in a single run?
There is no hard ceiling. By setting maxPagesPerQuery: 0 and configuring maxItems: 1000 (or higher), the actor paginates continuously through the catalog across your keywords or categories.
Why are some supportEmail and homepage fields empty?
AMO makes developer contact fields optional. When a developer provides a support email, homepage, or bug reporting URL, the scraper extracts and formats it cleanly. When omitted by the developer, the field is returned as empty string.
Do I need dedicated residential proxies or browser instances?
No. Because this scraper operates directly over streamlined HTTP channels without heavy browser rendering, fast datacenter proxies are fully sufficient and minimize execution costs.
How frequently are the statistics updated?
The scraper reads live metrics directly upon invocation. Values for averageDailyUsers, weeklyDownloads, and ratingAverage reflect the real-time state of the Firefox Add-ons store.
Can I extract themes instead of extensions?
Yes. Change addonType to "statictheme" to scrape Firefox visual themes, complete with preview URLs, designer profiles, and download statistics.
How does deduplication work across multiple queries?
The scraper maintains an in-memory set of unique add-on IDs. If an extension matches multiple search keywords or categories in a single run, it is pushed to the dataset exactly once, preventing duplicate rows in your export.
What happens if I provide no search terms or categories?
The scraper enters top-adoption discovery mode, automatically paginating through the most popular add-ons sorted by daily active users.
What export formats are supported?
You can download your data immediately from the Apify Console as JSON, CSV, Excel (XLSX), XML, or HTML Table. You can also stream records directly via API.
📋 Changelog
v1.2 — 2026-11
- Deep Pagination Unlocked: Replaced restrictive page caps with unified
maxPagesPerQuery: 0(auto/unlimited) and unrestrictedmaxItemsprocessing for 1,000+ item runs. - Fast Prefill Optimization: Streamlined default prefill parameters to execute clean sample runs in under 30 seconds.
- Enhanced Entity Normalization: Improved unescaping of nested localized summaries and author object structures.
- Comprehensive Documentation: Added visual status badges, quick-reference capability matrices, and multi-language code snippets.
v1.1 — 2026-10
- Added multi-criteria sorting (
users,rating,created,updated,hotness,downloads). - Added support for theme, dictionary, and language pack type filtering.
- Improved proxy rotation stability and automatic exponential backoff.
v1.0 — 2026-10
- Initial production release.
- High-coverage extraction of AMO extension metadata, adoption metrics, and author details.