These cookies are essential for the website to function properly. They enable core functionality such as security, shopping cart, and account access. You cannot disable these cookies.
These cookies enable enhanced functionality and personalization, such as remembering your language preference or region. If you do not allow these cookies, some features may not work properly.
These cookies help us understand how visitors interact with the website by collecting and reporting information anonymously. This helps us improve our website.
These cookies are used to deliver advertisements that are relevant to you based on your interests. They also help measure the effectiveness of advertising campaigns.
Yandex Metrica sends your PrestaShop shopping journey to Yandex and retries delivery of eligible approved purchases. A numeric counter ID and one switch start measurement; an optional Yandex token enables the purchase backup.
Yandex Metrica is a free analytics service covering traffic, products, orders and advertising results, with recordings, click maps and form analysis. The separate paid Pro plan is not required.
You switch nine shopping actions on independently, name the purchase goal and define up to fifteen custom goals. Marketing consent governs measurement and purchase delivery, staff visits stay excluded, and each shop keeps separate settings. The purchase queue shows waiting, accepted and failed reports and retries unsuccessful deliveries.
A temporary delivery fault leaves a visible purchase to retry instead of silently removing that order from your reporting.
Yandex Metrica connects a PrestaShop store to the Yandex service and protects every consent-eligible approved purchase with shop-managed retries, so a failed first delivery does not erase revenue from campaign reports.
Yandex Metrica supplies the hosted analysis. Its reports show where visitors come from, which pages and products they use, what reaches the cart, which orders are completed and how much revenue each source produces. Webvisor replays recorded visits, click and scroll maps combine page interactions, and form analysis exposes where fields slow people down.
The standard Yandex Metrica service is free. Yandex Metrica Pro is a separate paid plan for larger limits, real-time data transfer, centralized tag access and unsampled reports; the module needs neither that plan nor another reporting service.
The module gives those Yandex reports their PrestaShop meaning. It connects the selected counter to products, searches, carts, wishlists, checkout, customers and approved orders, then keeps important purchase delivery under the shop's control.
Nine independent switches cover page view, product view, category view, successful cart addition, successful wishlist addition, checkout start, search, account creation and purchase. Cart and wishlist actions are reported only after the store confirms the change, with the correct product and quantity. The page-view switch controls page reporting itself rather than merely changing a label.
You choose the purchase goal name and define up to fifteen additional goals for the moments particular to the store. A rule responds to a selected element, part of a page address, a chosen page type or a named action already produced by the storefront. A quote request, newsletter signup, telephone link, finance tab or completed configurator therefore appears under a readable business name.
The module validates every target before saving it and isolates a faulty rule from the others. Standard measurement remains quick to enable, while a mature store gains the vocabulary needed to answer its own conversion questions.
Every consent-eligible approved order enters the purchase queue, including a guest whom Yandex had not previously identified. The record carries the order reference, gross revenue, currency and as many as fifty product lines. A stable visitor identity keeps the order connected to the same reporting path.
The first delivery run starts immediately. If Yandex or the network refuses that attempt, the record remains in the queue and the automatic sender returns to it, with no more than six attempts. The shop shows what is waiting, in progress, accepted or failed, together with the response that explains a rejection.
This is the module's strongest difference: an interrupted confirmation page or temporary delivery fault becomes visible work for the queue instead of a silent hole between PrestaShop revenue and the Yandex report.
MPR Cookies Revolution and MPR Cookie Banner pass the current marketing decision to the module. Consent granted on the open page starts Yandex measurement immediately; withdrawal stops later shop actions and purchase delivery without waiting for another page. The same choice governs both the storefront and the retry queue.
Staff exclusion covers ordinary administration, previews and impersonation work, so price checks and test orders do not enter customer reports. When another supported MPR module uses the same Yandex counter, ownership selects one sender and the configuration screen names the conflict.
In a multistore installation, each shop has its own counter, goal names, consent behavior, purchase credentials and delivery view. One brand's traffic and queue history therefore stay separate from another brand managed in the same PrestaShop installation.
Everyday measurement starts with installation, a numeric counter ID and the activation switch. The optional purchase backup adds one token created in Yandex. Invalid identifiers are rejected, and tracking stays inactive until the required value is complete.
The same screen later controls nine standard actions, the purchase goal name, merchant-defined goals, consent behavior, staff exclusion, the amount processed in one delivery run and the active shop. There is no second setup when the store moves from basic reports to a detailed measurement plan.
The readiness view tests the effective storefront state, the Yandex connection, every custom target, consent, duplicate ownership, purchase credentials, queue health and automatic delivery. It distinguishes configured from active, consent-blocked, staff-excluded, invalid or rejected, so the merchant sees the reason before missing figures guide a budget decision.
Be the first to share your experience with this product.
Yandex Metrica connects your PrestaShop store to a Yandex Metrica counter so you can see page activity, product interest, cart actions, searches, sign-ups, and completed orders in one analytics account.
Modules our team genuinely pairs with this one, and exactly why each belongs in the same setup.
A store using Yandex Metrica measures ecommerce activity, custom goals and purchases in markets where Yandex reporting genuinely matters, building data from page, product and checkout actions. Metrica is a capable analytics destination, but it is one endpoint; stores of any size also run additional marketing tags that benefit from organised, event-aware delivery rather than being scattered as separate snippets throughout the theme.
Google Tag Manager is a separate module that adds your GTM container and feeds it GA4-formatted ecommerce events from real product views, cart changes, checkout starts, purchases, searches, logins and sign-ups. It gives your wider tag stack a single, consistent delivery layer, keeping the marketing tags around Metrica tidy as they multiply.
Used alongside Yandex Metrica, GTM keeps the two roles distinct: Metrica remains your primary analytics view for its markets while the container orchestrates the other tags around it. The payoff is a cleaner, more maintainable setup where your regional analytics reporting is not entangled with campaign snippets, adding or changing tags is lower risk, and each tool does the job it was built for instead of one being stretched to cover both.
Running Yandex Metrica, your store already measures ecommerce activity, custom goals and purchases, so you can see which products, searches and checkout steps contribute to revenue in the markets you care about. Those numbers reliably show where behaviour changes, but they cannot reveal the on-page cause, and without that detail it is difficult to move from noticing a weak step to fixing it with any confidence.
Hotjar is a separate tool that ties heatmaps and session recordings to real shopping context, exposing friction on product pages, checkout steps, forms and calls to action. It adds another qualitative view alongside Metrica’s own recordings, maps and form analysis, letting you observe individual journeys through exactly the steps your data flags as problematic.
Used together, they let you find a weak step in Metrica and then watch Hotjar recordings of that step to see what is actually going wrong. The payoff is diagnosis grounded in two kinds of evidence: Metrica tells you where and how much, Hotjar tells you why, so you prioritise improvements by measurable impact and implement them based on real, visible shopper behaviour rather than assumptions.
A store using Yandex Metrica is collecting ecommerce behaviour data, and EU visitors should be able to accept or decline that tracking. Metrica measures activity; it does not present and enforce a category-based consent choice across all the scripts your store loads, so on its own it leaves you without a dependable gate for the analytics and marketing cookies a real storefront tends to accumulate over time.
Cookies Revolution is a separate consent manager that collects and enforces choices for necessary, functional, analytics and marketing cookies. It blocks matching external and inline scripts before consent, reactivates allowed ones afterwards once it is granted, and records each decision.
Used alongside Metrica, it keeps measurement and consent enforcement as separate layers, holding scripts until a shopper agrees and logging their choice. The payoff is a compliant foundation you do not have to assemble by hand: you keep measuring visitors who opt in, you have an auditable consent record, and you avoid editing what loads before someone agrees, so privacy handling sits cleanly beside your analytics rather than inside it.
30 days return right
Plug & Play Modules
Dedicated Support First
Built and maintained by David Miller and mypresta.rocks. David Miller has worked with PrestaShop since 2013, and the company behind this shop has been registered since 3 December 2018. Every module in this catalogue is our own work, so your questions to support reach the people who wrote the code. The changelog on this page lists every update with its date.
