Polnisch 
English Kowal Analytics is a sales attribution module for Magento 2. Its purpose is to show which store elements actually affect the cart, order, and revenue.
This is not a regular pixel that collects page views. The module analyzes the full sales context:
Thanks to this, the store can answer questions that standard analytics usually do not answer:
WhatsApp
+48608012047related products sections actually sell?upsell and cross-sell blocks generate revenue?The module was created for stores that want to optimize merchandising, content, and page layout based on real impact on sales, not just traffic or CTR.
From the reports, you can evaluate:
A click alone says nothing about business value. Kowal Analytics connects frontend events with the cart, order, and revenue.
areaThe basic unit of analysis is an area, meaning a defined part of the page that you want to measure.
Examples:
related_products on PDP,upsell_products on PDP,crosssell_products in the cart,category_listing on the category product list,search_results on search results pages,wishlist_products,compare_products,blog_post_listing,blog_sidebar_categories,objectEach area contains specific object items, meaning the elements the user sees and clicks.
Examples:
related_products section,This means the report does not stop at the level of:
but goes down to the level of:
The module also stores the source context, meaning where the path started.
Example:
Affirm Water Bottle product page,related_products,Zing Jump Rope,Zing Jump Rope.In that case, you can show:
source page = Affirm Water Bottle,area = related_products,clicked object = Zing Jump Rope,purchased sku = Zing Jump Rope.This is exactly the level of analysis that is usually missing in typical tools.
Area is a section or block of the page that you want to measure as a source of sales impact.
Examples:
Object is a specific element inside an area.
Examples:
Source Page is the page from which the user started the path related to a given area.
Examples:
related_products,This is the specific SKU that was purchased and to which we attribute the impact of a given area or object.
The module supports both native integrations and areas defined by selectors.
related_productsupsell_productscrosssell_productscategory_listingsearch_resultswishlist_productscompare_productsblog_post_listingblog_recent_posts_widgetblog_sidebar_recent_postsblog_sidebar_categoriesblog_sidebar_tagsblog_post_viewhomepage_promo_boxblack_friday_bannersummer_campaign_sliderai_recommendationscategory_top_ctaUsed for a quick results overview.
It shows, among other things:
Answers the question:
Example:
related_products generates 12 orders and 4 800 PLN in revenue,WB05-S-Orange,Affirm Water Bottle product.This report is key for product areas.
It answers the question:
Example:
source product = Affirm Water Bottle,clicked object = Zing Jump Rope,purchased sku = Zing Jump Rope,orders = 7,revenue = 840 PLN.Shows the blog's impact on sales.
It answers the questions:
Example:
How to choose a training water bottle generated 9 orders,Affirm Water Bottle.Lets you drill down into one specific object.
Example:
related_products,blog_post_listing,The report shows:
This is a reverse-perspective report.
Instead of looking at the object, you look at one source page and check:
Example:
Affirm Water Bottle product page as the source page,related_products,The store can compare whether:
related_products sells better than upsell_products,The content team can check:
If a section has high impressions and low or zero impact on revenue, you can assess whether it should:
After changing the layout, widget, blog, or recommendation mechanism, you can compare:
It provides the most value to:
Kowal Analytics turns storefront elements into measurable sales sources.
It lets you move from the general question:
to the specific question:
Main entry points to the module:
Kowal -> Analytics -> DashboardStores -> Configuration -> AnalyticsCurrently, the module provides three main groups of settings.
Path:
Stores -> Configuration -> Analytics -> GeneralField:
Enable AnalyticsMeaning:
Recommendation:
store view after verifying that trackers and consumers are working correctly.Path:
Stores -> Configuration -> Analytics -> DebugFields:
Enable Backend Debug LogEnable Frontend Console LogMeaning:
var/log/kowal_analytics_debug.logUse cases:
Recommendation:
Path:
Stores -> Configuration -> Analytics -> ToolsField:
Enable Frontend Selector AssistantMeaning:
Use cases:
The module works within Magento scope, so the configuration can differ for:
default,website,store view.It is safest to treat the module as a per-store-view tool because:
Area is a defined part of the page that you want to measure as a source of sales impact.
Examples:
related_productsupsell_productscrosssell_productscategory_listingsearch_resultswishlist_productscompare_productsblog_post_listingblog_sidebar_categorieshomepage_promo_boxObject is a specific element inside an area.
Examples:
Source Page is the page from which the user started an interaction that later led to a sale.
Examples:
related_products,This is the main overview screen. It shows:
This screen answers the question:
what works bestThis report answers the questions:
Example:
related_products has 18 orders,Zing Jump Rope sells best there,Affirm Water Bottle product page.This is a report for product areas such as:
related_productsupsell_productscrosssell_productscategory_listingsearch_resultsIt shows the relationship:
source product -> clicked object -> purchased SKUExample:
Affirm Water Bottle,WB05-S-Orange in related_products,WB05-S-Orange.This is a report for blog areas:
blog_post_listingblog_recent_posts_widgetblog_sidebar_recent_postsblog_sidebar_categoriesblog_sidebar_tagsblog_post_viewIt answers the questions:
This is a report for one specific object.
Example:
related_products,blog_post_listing,blog_sidebar_categories.It shows:
This is a report for one specific source page.
Example:
Affirm Water Bottle product page,How to choose a training water bottle,Running Shoes category listing.It shows:
Available models:
Last ClickFirst ClickAssistedView ThroughHow to read them:
Best for the question:
Best for the question:
Best for the question:
Best for the question:
You can prepare a custom area through the Frontend Selector Assistant.
Typical workflow:
Enable Frontend Selector Assistant.container selector.item selector.link selector.data-kowal-track-*.Assume you have a promotional box with three tiles on the homepage.
You can define:
area_code = homepage_promo_boxobject_type = promotioncontainer_selector = .homepage-promoitem_selector = .homepage-promo__itemlink_selector = .homepage-promo__linkThen the report will show:
The most sensible sequence:
Before installation, make sure that:
bin/magento,var/log.Add the Composer repository:
composer config repositories.kowal composer https://repo.kowal.storeAdd credentials for the private repository:
composer config http-basic.repo.kowal.store Install the module:
composer require kowal/module-analyticsRun the standard Magento commands:
bin/magento module:enable Kowal_Analyticsbin/magento setup:upgradebin/magento cache:flushIf the store runs in production mode, also execute:
bin/magento setup:di:compilebin/magento setup:static-content:deploy -fbin/magento cache:flushThe module uses queues and asynchronous processing. Without them, the dashboard and reports will not be complete.
Start the required consumers:
bin/magento queue:consumers:start kowal_analytics.raw_eventsbin/magento queue:consumers:start kowal_analytics.conversionbin/magento queue:consumers:start kowal_analytics.attributionMagento cron must also work correctly because the module uses retry and backfill for attribution.
Basic check:
bin/magento cron:runAfter correct installation, the module:
quote,sales_order,After installation, check:
Kowal -> Analytics -> DashboardStores -> Configuration -> AnalyticsIf the module is active correctly, you should see:
Perform a simple end-to-end test:
related_products or a blog post.If debug is enabled, check:
var/log/kowal_analytics_debug.logIf you want to confirm that tracking works on page render, check for the presence of these attributes:
data-kowal-track-areadata-kowal-track-area-iddata-kowal-track-objectdata-kowal-track-iddata-kowal-track-skuExample:
related_products section container should have data-kowal-track-area='related_products'data-kowal-track-object='product' and its own data-kowal-track-idCheck:
Check:
kowal_analytics.attribution consumer is running,Check:
data-kowal-track-*,The safest order is:
