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.
57 health vs 56 average across 16,376 Uncategorized plugins
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
Biggest win: Update recency
To rank higher: Last updated 697 days ago — ship an update; wp.org decays a listing's search weight after ~180 days.
Get the full rank-higher report →Daily downloads
Since 2022-10-05 · 1,425 days · wp.org + Plugin Pulse archive
30-day downloads
Rolling 30-day volume · peaks are release surges
358
now · peak 1.5K
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
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
1.9y ago
latest release · v6.6.2
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.
Refined from the date this plugin crossed into its current band.
Install history · since 2019-12-09 · 1,422 observations
Estimated value
What this plugin might earn a year, and what it might sell for. Modeled from public signals; we don't see anyone's books.
Est. annual revenue
Est. acquisition value
No paid tier is visible, so we don't put a figure on revenue or sale value: that would be guessing. The install base is a real asset to an acquirer, just not one public data lets us price. A small install base leaves thin data to model from.
Details
Recent reviews
All reviews on wp.org ↗- ★★★★★ vbosch1.4y 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.1y ago
A simple way to get feedback from you customer. Installed and running in 2 minutes.
Read on wp.org ↗ - ★★★★★ kira72.4y 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.6y ago
Great simple plugin, does exactly what it says, nothin more, no extra fluff. More plugins should be like this.
Read on wp.org ↗ - ★★★★★ gavie2.8y 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.1y 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 ↗ - ★★★★★ d9media6.9y 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.7y 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 ↗
Known vulnerabilities
via Wordfence Intelligence1 disclosed vulnerability on record for this plugin, fixed in the current version. Sites on older versions stay exposed until they update.
- 2024-04-29 CVE-2024-2752 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') 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
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
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 C
-
White Label CMS 200K+ installs · 4.6★ · 2 shared tags A -
Custom Login 10K+ installs · 3.7★ · 2 shared tags B
-
Customize Admin 4K+ installs · 3.8★ · 2 shared tags B -
Customize Login Image 3K+ installs · 4.4★ · 2 shared tags D -
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-08-29. https://plugins.wpmayor.com/plugin/wc-customer-source