Title: Order Source Analytics for WooCommerce Author: ocmisrael Published: 2026(e)ko apirilaren 29(a) Last modified: 2026(e)ko apirilaren 29(a) --- Bilatu pluginak ![](https://ps.w.org/order-source-analytics-for-woocommerce/assets/banner-772x250. png?rev=3518080) ![](https://ps.w.org/order-source-analytics-for-woocommerce/assets/icon-256x256. png?rev=3518065) # Order Source Analytics for WooCommerce [ocmisrael](https://profiles.wordpress.org/ocmisrael/)-(r)en eskutik [Deskargatu](https://downloads.wordpress.org/plugin/order-source-analytics-for-woocommerce.1.0.1.zip) * [Xehetasunak](https://eu.wordpress.org/plugins/order-source-analytics-for-woocommerce/#description) * [Berrikuspenak](https://eu.wordpress.org/plugins/order-source-analytics-for-woocommerce/#reviews) * [Instalazioa](https://eu.wordpress.org/plugins/order-source-analytics-for-woocommerce/#installation) * [Garapena](https://eu.wordpress.org/plugins/order-source-analytics-for-woocommerce/#developers) [Laguntza](https://wordpress.org/support/plugin/order-source-analytics-for-woocommerce/) ## Deskripzioa **Order Source Analytics for WooCommerce** helps you understand where your WooCommerce sales really come from. Instead of guessing which traffic channels work best, this plugin gives you a clear and visual breakdown of orders and revenue by traffic source — including Google Ads, Organic Search, Facebook, Direct traffic, referrals and UTM-based campaigns. The plugin is lightweight, fast, and optimized for large stores using aggregated queries. It is fully compatible with WooCommerce HPOS (High-Performance Order Storage). **100% free. No upsells. Built with love ❤️** ### Key Features * Analyze orders and revenue by traffic source * Supports Google Ads, Organic Search, Facebook, Direct, Referral, UTM campaigns and more * Beautiful charts: Pie, Bar and Line (daily revenue) * KPIs dashboard: Orders, Revenue, AOV and Top Source * Filter by date range and order status * Top traffic sources table with revenue share * Export full report to CSV * Optimized queries for large WooCommerce stores * Fully compatible with WooCommerce HPOS * No configuration required — works out of the box * **Translation-ready** — fully internationalized with a complete `.pot` template * **Hebrew translation included** with full **RTL (right-to-left) support** for Hebrew WordPress sites ### Supported Traffic Sources The plugin automatically detects and normalizes common WooCommerce attribution sources, including: * Google Ads * Google Organic * Facebook * Direct traffic * Referral traffic * UTM-based campaigns * Unknown / fallback traffic ### Who Is This Plugin For? * WooCommerce store owners * Marketing and performance teams * Agencies managing multiple WooCommerce stores * Anyone who wants clear attribution insights inside WordPress ## Pantaila-argazkiak [⌊Analytics dashboard with KPIs and filters⌉⌊Analytics dashboard with KPIs and filters⌉[ Analytics dashboard with KPIs and filters [⌊Revenue distribution by traffic source (pie chart)⌉⌊Revenue distribution by traffic source (pie chart)⌉[ Revenue distribution by traffic source (pie chart) [⌊Orders by source (bar chart)⌉⌊Orders by source (bar chart)⌉[ Orders by source (bar chart) ## Instalazioa 1. Upload the plugin files to the `/wp-content/plugins/order-source-analytics-for- woocommerce` directory, or install the plugin directly from the WordPress plugins screen. 2. Activate the plugin through the “Plugins” screen in WordPress. 3. Open **WooCommerce Order Source Analytics**. 4. Run your first report — no setup required. ## MEG ### Does this plugin require any configuration? No. The plugin works out of the box using WooCommerce order attribution data. ### Is this plugin compatible with HPOS? Yes. The plugin is fully compatible with WooCommerce High-Performance Order Storage( HPOS). ### Can I export the data? Yes. You can export the report to a CSV file for further analysis in Excel or Google Sheets. ### Does this plugin track users or add cookies? No. The plugin only analyzes existing WooCommerce order data and does not track visitors. ### Is the plugin really free? Yes. 100% free, with no ads, no upsells and no limitations. ### Is the plugin available in Hebrew? Does it support RTL? Yes. A full Hebrew (he_IL) translation is bundled with the plugin and loaded automatically when the WordPress site language is set to Hebrew. The admin interface also includes a dedicated RTL stylesheet that switches the layout to right-to-left, so the dashboard reads naturally in Hebrew. ### Can I translate the plugin to another language? Yes. The plugin is fully translation-ready and ships with a `.pot` template inside the `languages/` folder. You can translate it using tools like Poedit or contribute through the WordPress.org translation platform. ## Berrikuspenak ![](https://secure.gravatar.com/avatar/4ca4a3695ef3db692fb4adff8877f25be8b9560c8ebe29480253f92f1321da7c? s=60&d=retro&r=g) ### 󠀁[Problems in plugin](https://wordpress.org/support/topic/problems-in-plugin/)󠁿 [servicestsim](https://profiles.wordpress.org/servicestsim/) 2026(e)ko uztailaren 10(a) Version 1.0.1 has serious reporting bugs 1. It probably excludes completed orders The code converts statuses using: ‘wc-‘ . ltrim($s, ‘wc-‘) The second argument to ltrim() is a set of characters, not a literal prefix. Consequently: processing - > wc-processing completed -> wc-ompleted cancelled -> wc-ancelled The default statuses are processing and completed, so completed orders will likely be silently excluded from both the source report and daily-revenue trend. The correct form is approximately: $s = sanitize_key((string) $s); return str_starts_with($s, ‘wc-‘) ? $s : ‘wc-‘ . $s; This bug appears in multiple paths and must be fixed everywhere, including the legacy-order queries. 2. Its PHP 7.4 compatibility declaration is wrong The plugin says it supports PHP 7.4, but repeatedly calls: str_contains() str_starts_with() str_ends_with() Those functions require PHP 8.0 or later. On PHP 7.4, report execution will fatal-error. The developer should either declare PHP 8.0+ or replace those calls with PHP 7.4-compatible implementations. 3. Large date ranges can consume excessive resources The date parameters are sanitized but not strictly validated or limited. The plugin: Builds one PHP array entry for every day in the selected period. Retrieves one database row per order and aggregates the results in PHP. Describes the queries as “aggregated,” even though the main source query is not aggregated in SQL. A shop manager selecting an extremely large range could cause a heavy database query, high PHP memory use, or a timeout. 4. Its HPOS support is brittle It does query wc_orders and wc_orders_meta, so it understands HPOS storage. But it: Directly couples itself to WooCommerce table structures. Does not declare HPOS compatibility through WooCommerce’s FeaturesUtil mechanism. Executes a second legacy-table query even when HPOS is active, attempting to find orders not present in HPOS. That is less robust than using supported WooCommerce order/query APIs. 5. The advertised meta-key settings do not exist The plugin initializes a list of possible attribution meta keys and tells the administrator to configure the correct meta key in “Settings.” However: There is no settings screen or save handler. The private option-update function is never called. The reporting function ignores the supplied $metaKeys. It always uses three hard-coded WooCommerce attribution keys. Therefore, the advertised support for custom attribution metadata is effectively unimplemented.6. It can misclassify attribution The normalization code tends to label a source value of google as Google Ads, without examining UTM medium. It also collapses most referring domains into a generic Referral category. That can give misleading marketing results even after fixing the completed-order bug.7. “Revenue” means order total, not net sales It sums total_amount. It does not subtract refunds or reproduce WooCommerce Analytics’ net-sales calculation. Its revenue result may include shipping and tax and may differ materially from WooCommerce’s standard reports. I would not rely on version 1.0.1 in production until at least the following are fixed: Replace all faulty ltrim($s, ‘wc-‘) status handling. Require PHP 8.0+, or implement PHP 7.4-compatible string helpers. Validate dates and impose a sensible maximum report range. Compare its counts and totals against known completed and processing orders. Clarify whether “revenue” means gross order total or net sales. Add a proper HPOS compatibility declaration. [ Irakurri 0 berrikuspenak ](https://wordpress.org/support/plugin/order-source-analytics-for-woocommerce/reviews/) ## Laguntzaileak eta Garatzaileak “Order Source Analytics for WooCommerce” software librea da. Ondoko pertsonek egin dizkiote ekarpenak plugin honi. Laguntzaileak * [ ocmisrael ](https://profiles.wordpress.org/ocmisrael/) [Itzul zaitez Order Source Analytics for WooCommerce zure hizkuntzara.](https://translate.wordpress.org/projects/wp-plugins/order-source-analytics-for-woocommerce) ### Garapena interesatzen zaizu? [Araka kodea](https://plugins.trac.wordpress.org/browser/order-source-analytics-for-woocommerce/), begiratu [SVN biltegia](https://plugins.svn.wordpress.org/order-source-analytics-for-woocommerce/) edo harpidetu [garapen erregistrora](https://plugins.trac.wordpress.org/log/order-source-analytics-for-woocommerce/) [RSS](https://plugins.trac.wordpress.org/log/order-source-analytics-for-woocommerce/?limit=100&mode=stop_on_copy&format=rss) bidez. ## Aldaketen loga #### 1.0.1 (2026-04-29) * Narrow down the tag list to the 5 most relevant tags #### 1.0.0 * Initial release * Order source analytics dashboard * Charts, KPIs and CSV export * HPOS compatibility * Full internationalization (i18n) support with `.pot` template * Hebrew (he_IL) translation included with full RTL stylesheet ## Meta * Version **1.0.1** * Azken eguneraketa **duela 2 hilabete** * Instalazio aktiboak **10 baino gutxiago** * WordPress bertsioa ** 6.0 edo handiagoa ** * **6.9.4** (e)raino probatuta. * PHP bertsioa ** 7.4 edo handiagoa ** * Language * [English (US)](https://wordpress.org/plugins/order-source-analytics-for-woocommerce/) * Etiketak * [analytics](https://eu.wordpress.org/plugins/tags/analytics/)[attribution](https://eu.wordpress.org/plugins/tags/attribution/) [order source](https://eu.wordpress.org/plugins/tags/order-source/)[traffic source](https://eu.wordpress.org/plugins/tags/traffic-source/) [woocommerce](https://eu.wordpress.org/plugins/tags/woocommerce/) * [Ikuspegi aurreratua](https://eu.wordpress.org/plugins/order-source-analytics-for-woocommerce/advanced/) ## Balorazioak 5 out of 5 stars. * [ 1 5-star review ](https://wordpress.org/support/plugin/order-source-analytics-for-woocommerce/reviews/?filter=5) * [ 0 4-star reviews ](https://wordpress.org/support/plugin/order-source-analytics-for-woocommerce/reviews/?filter=4) * [ 0 3-star reviews ](https://wordpress.org/support/plugin/order-source-analytics-for-woocommerce/reviews/?filter=3) * [ 0 2-star reviews ](https://wordpress.org/support/plugin/order-source-analytics-for-woocommerce/reviews/?filter=2) * [ 0 1-star reviews ](https://wordpress.org/support/plugin/order-source-analytics-for-woocommerce/reviews/?filter=1) [Your review](https://wordpress.org/support/plugin/order-source-analytics-for-woocommerce/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/order-source-analytics-for-woocommerce/reviews/) ## Laguntzaileak * [ ocmisrael ](https://profiles.wordpress.org/ocmisrael/) ## Laguntza Zerbait duzu esateko? Laguntza behar? [Ikusi laguntza foroa](https://wordpress.org/support/plugin/order-source-analytics-for-woocommerce/)