Where Did You Hear About Us Checkout Field for WooCommerce
by wooassist · Uncategorized
Also makes 4 other plugins · 8.7K+ installs across the portfolio →
Adds a custom field in the checkout page to ask your customers where they've heard about your store.
Try it live opens a temporary test site in your browser, which can take about 20 seconds to load. Plugins that rely on outside services or a full server may not work completely there.
Health
C 62/100
Stale · Likely abandoned · Few reviews
Active installs
1K+
≈1.5K estimated
Momentum
+22%
downloads vs prior 30d
Biggest opportunity: “branding”, “custom” and “customizer” aren't earning a slot. You list them, but you're not in the first 24 results for those searches. WordPress.org counts only your first five tags, so free the slot for a search you can win.
62 health vs 58 average across 25,753 Uncategorized plugins
Install conversion
How it's measured →4.4%
of downloads still active
At least 1K of 22.8K lifetime downloads are still running, above its category: the median Uncategorized plugin keeps 0.6%, across 17,772 plugins.
Downloads count every update, not just first installs, so older and more frequently released plugins read lower. Compare against other Uncategorized plugins, not across the directory. wp.org reports active installs as the bottom of a band, so the real rate is this or higher.
Removal-risk signals
28/100Maintenance and integrity signals that tend to precede a WordPress.org removal. Not an official status, a heads-up to act.
- Not actively maintained. No update in about 2 years.
Details
Directory ranking optimization
How it's scored →How well this listing is tuned to rank in WordPress.org search, on the factors an owner controls. Not popularity, optimization.
Room to improve
Most to gain: Update recency
Updated 761 days ago, past the ~180 days where wp.org starts discounting
Tested up to WordPress 6.6.11; the current branch is 6.8
4.6★ over 8 reviews, smoothed to 4.17★ and held back under 25 reviews
5 of 5 tags set · short description in place
To rank higher: Last updated 761 days ago — ship an update; wp.org decays a listing's search weight after ~180 days.
Get the full rank-higher report →Search visibility
How it's tracked →Directory searches this plugin turns up in, and which way each one is moving. WordPress.org publishes no history of search positions, so this starts the day we first tracked a keyword and never backfills.
Not enough tracked days yet to call a direction. Momentum needs at least three keywords measured a week or more apart.
wp.org is where the directory puts the plugin for that search. On merit is where it would sit if results were ranked on rating, support and updates, without the install boost. The last column is how far the wp.org position moved, from our first reading in the last 90 days to the latest.
| Keyword | wp.org | On merit | wp.org move, 90 days |
|---|---|---|---|
| textbox | #15 | #14 | 0 |
| branding your tag | Not in the top 24 | ||
| custom your tag | Not in the top 24 | ||
| customizer your tag | Not in the top 24 | ||
| logo your tag | Not in the top 24 | ||
| storefront your tag | Not in the top 24 | ||
1 search this plugin appeared in over the last 90 days. 5 of its tags aren't in the top 24 for their own search.
What to do about it
- “branding”, “custom” and “customizer” aren't earning a slot. You list them, but you're not in the first 24 results for those searches. WordPress.org counts only your first five tags, so free the slot for a search you can win.
Daily downloads
Since 5 Oct 2022 · 1,489 days · wp.org + Plugin Pulse archive
30-day downloads
Rolling 30-day volume · peak 1.5K · peaks are release surges
Directory rank vs rivals
wp.org popularity rank over time · higher is better · when a rival's line climbs above yours, they've overtaken you
Rating trend
Star average over time · dips mark rough releases
Health trend
Composite health score, snapshotted daily
Update activity
How busy the existing users are, measured as downloads in the last 30 days for every 1,000 active sites. A spike means a new release everyone's pulling; a long, slow decline means an aging user base that updates less.
Release cadence
No release in a yearHow often this plugin actually ships. A steady rhythm is the maintenance signal a single "last updated" date can't show.
0
releases in the last 12 months
2.1y ago
latest release · v6.6.2 · 1 Oct 2024
1
tagged releases on record
Recent releases
What its installed base runs
via wordpress.orgShare of active installs on each version of this plugin · 94% run the current release. Green is the current release; a big slice on older versions is a user base that has stopped updating.
Estimated active installs
The public count shows “1K+”. Our estimate pins where the real number sits.
Crossed into this band 24 months ago; a band this size takes about a year or more to cross, which places it about 50% of the way through.
Install history since 9 Dec 2019
Recent reviews
All reviews on wp.org ↗- ★★★★★ vbosch1.5y ago
Hi there, Thanks for this plugin. We are using another plugin to automatically export and import orders into another system. In this plugin we have the capability to select certain ‘meta fields’, however we do not know what exact meta name / meta key your plugin uses. Could you please tell us? Thanks in advance
Read on wp.org ↗ - ★★★★★ windycitycabinet2.3y ago
A simple way to get feedback from you customer. Installed and running in 2 minutes.
Read on wp.org ↗ - ★★★★★ kira72.6y ago
No mess, no fuss, straight-forward plugin. Was up and running in around 10 minutes. It’s great that we can now ascertain how people found our site when going through the checkout process. Awesome stuff! 🙂
Read on wp.org ↗ - ★★★★★ sasko2k2.7y ago
Great simple plugin, does exactly what it says, nothin more, no extra fluff. More plugins should be like this.
Read on wp.org ↗ - ★★★★★ gavie3.0y ago
Great plugin, works fine. One suggestion: Currently the line “Other” is not translated in the dropdown-menu (only in the field label).. To fix: on wc-customer-source.php, line 589, please change the text-domain from woocommerce-admin to woocommerce, and it will work flawlessly.
Read on wp.org ↗ - ★★★★★ fdittmar5.3y ago
Works fine. A little more in terms of formatting/design would be great (spacing / alignment on my pages isn’t great).
Read on wp.org ↗ - ★★★★★ d9media7.0y ago
First of all, I would like to thank you for making this plug-in available to the public. I think it is an simple and elegant solution. There is a few questions that raised for me after giving this a try and reading the source code. In your report, you are directly accessing WooCommerce properties which is considered bad practice and will actually throw a lot of notices in the admin area (“doing it wrong”). Instead of $order->billing_first_name you should use $order->get_billing_first_name() and so forth. This will ensure the plug-in to continue working if WooCommerce decides to change these properties. Apparently this is also relevant for caching. You are using woocommerce_form_field( ) to build the select field. Then further down, you are building the field yourself. Is there a reasoning behind it? (I’m not saying it is not legit, just curious if this was done on purpose) You are defining your class as “final” which means that it can not be extended and methods can not be altered. While I’m sure this has a reasoning, it defeats the purpose of OOP. Lastly, In terms of transliteration, there’s a bunch of strings which are unnecessary to include into your textdomain, such as Report, Setting, Export, Customer Name, Order Status etc. Instead you may use WooCommerce’s or WordPress’ textdomain: __( 'Customer Name', 'woocommerce-admin' ), __( 'Orders', 'woocommerce-admin' ), __( 'Other', 'woocommerce-admin' ) __( 'Other', 'woocommerce' ) __( 'Select an option…', 'woocommerce' ) __( 'Customer', 'woocommerce' ) I don’t fault you for this, in fact I’m seeing this a lot of times in a lot of Plug-Ins but I think with a bit of research in our IDE we can often find strings which already have been included in core or contributed plug-ins. While we can’t always depend on other plugins in our translation, it is the case here because we are extending WooCommerce functionality.This way it will be easier to maintain and more languages will be supported in the first place. I hope you will find this review helpful. Thanks again for sharing your code. This topic was modified 6 years, 9 months ago by d9media. This topic was modified 6 years, 9 months ago by d9media. This topic was modified 6 years, 9 months ago by d9media.
Read on wp.org ↗ - ★★★★★ Stephen Ainsworth7.9y ago
And it has a position field in settings which lets you position the drop-down where you need it to be.
Read on wp.org ↗
Security history
via Wordfence IntelligenceThe 1 disclosed vulnerability is patched in the current version (1.3.3). Sites still on an older version should update.
- Patched Medium · 5.5 Where Did You Hear About Us Checkout Field for WooCommerce <= 1.3.1 - Authenticated (Shop Manager+) Stored Cross-Site Scripting ↗2024-04-29 CVE-2024-2752 Improper Neutralization of Input During Web Page Generation Affects <= 1.3.1 Patched in 1.3.2
Vulnerability records provided by Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. License and terms.
CVE records: Copyright 1999-2026 The MITRE Corporation. CVE terms of use.
Behavioral tests
via WP HiveAutomated install-time checks, tested on PHP 8.1.12 · WP 6.6.2
Languages
via translate.wordpress.orgTranslated into 3 languages, 2 at 90% or more
AI assistants
How it's measured →Whether ChatGPT and Claude name this plugin when asked the category question, and whether the readme gives them something to quote.
Not measured yet for this plugin’s topics. Its tracked searches are not among the measured topics. See the topics measured so far.
Readme readiness
2 of 8 pass · checked 29 Oct 2026Can an assistant quote this readme? Eight deterministic checks over the wp.org listing, no model involved.
- ✓ Says what it does "Adds a custom field in the checkout page to ask your customers where they've heard about your store."
- ! Has a FAQ Only 2 questions in the FAQ; 3 or more gives an assistant something to match.
- ! FAQ asks real questions 0 of 2 FAQ entries are headings, not questions ("undefined").
- ! Names who it is for Never says who the plugin is for or what they use it for.
- ✓ Names what it works with Mentions WooCommerce.
- ! Headings and lists 0 headings and 1 list; assistants quote headed sections and bullet lists, not paragraphs.
- ! Enough to quote 596 characters of description; under 1,000 there is little to quote.
- ! Tags match the text Only 1 of 5 tags appear in the text ("branding", "customizer", "logo", "storefront" missing).
Growth timeline
Install-tier crossings we have observed, and how long each tier took to outgrow
- 2024-11-16 2K+ → 1K+ down after 1 days in tier
- 2024-11-15 1K+ → 2K+ up after 4 days in tier
- 2024-11-11 2K+ → 1K+ down after 860 days in tier
- 2022-07-05 1K+ → 2K+ up
Competes with
The plugins that solve the same job, ranked by shared tags then reach, closest match first. The letter on the right is each plugin's health grade (A best, F worst).
- S Storefront Top Bar 2K+ installs · 4.5★ · 3 shared tags D
-
White Label CMS 200K+ installs · 4.6★ · 2 shared tags A -
Custom Login 10K+ installs · 3.7★ · 2 shared tags B -
Customize Admin 3K+ installs · 3.8★ · 2 shared tags B -
Customize Login Image 3K+ installs · 4.4★ · 2 shared tags C -
Brand My Login 100+ installs · 4.0★ · 2 shared tags D
Embed this report card
Drop a live Pulse card for Where Did You Hear About Us Checkout Field for WooCommerce into a readme, a review or a deck. It updates itself.
<iframe src="https://plugins.wpmayor.com/embed/wc-customer-source" width="480" height="300" style="border:0" loading="lazy" title="Where Did You Hear About Us Checkout Field for WooCommerce — Plugin Pulse"></iframe> Where Did You Hear About Us Checkout Field for WooCommerce: 1K+ active installs, 4.6★ (8 reviews). Plugin Pulse (WP Mayor), as of 2026-11-01. https://plugins.wpmayor.com/plugin/wc-customer-source
Spotted a number that looks wrong? Report a data issue and we'll check it against the source.