PS PrestaShop Beginner

Conversion Funnel and Heatmap: documentation for the PrestaShop 8 and 9 module

9-step funnel, acquisition, products, heatmap with rage clicks and a weekly email report for PrestaShop 8 and 9.

Updated Module version 1.3.2

The DataFirefly – Conversion Funnel & Heatmap module (dffunnelheatmap) shows where your visitors give up, where your buyers come from and what stops them on your pages. It combines a 9-step conversion funnel, an acquisition report, product statistics, a heatmap with rage click detection and a weekly email report. All data collection is first-party: nothing leaves your server.

This documentation covers version 1.3.2, compatible with PrestaShop 8.0 to 9.x (PHP 7.2 or later).

Installation and upgrade

  1. Download the dffunnelheatmap.zip archive from your customer account.
  2. In the back office, open Modules > Module Manager, click Upload a module and select the ZIP.
  3. The module creates its 6 tables and adds the Stats > Funnel & Heatmap tab.

To upgrade from a previous version, upload the new ZIP over the installed module. The upgrade scripts run on their own: your data and settings are kept.

No external dependency: no Composer, no CDN. The default settings suit most stores: heatmap on 100% of sessions, 90-day retention, Do Not Track respected, employees excluded.

Getting started

Until the first visit is received, the dashboard shows a checklist: tracking enabled, funnel or heatmap enabled, first visit received. Browsers logged into the back office are not counted: to check data collection, open the store in a private browsing window or on another device.

The dashboard

The interface has six tabs: Dashboard, Conversion funnel, Acquisition, Products, Heatmap and Settings.

  • Indicators: sessions, unique visitors, orders placed, add-to-cart rate, conversion rate, tracked revenue (tax incl.), average order and the biggest drop-off in the funnel. Each indicator is compared with the previous period of the same length.
  • Day by day: chart of sessions, orders or conversion rate. The buttons above the chart switch the metric without reloading the page, and the Show the data link opens the table of values.
  • Recommendations: up to 6 findings sorted into To fix, To check and Good news, each with a link to the matching report.
  • Right now: visitors of the last 5 minutes, the pages they view and the split by device, refreshed every 30 seconds.

A summary card (sessions, orders and conversion of the last 7 days, visitors right now) is also added to the PrestaShop home dashboard.

Recommendations

They only appear above a minimum volume, about 30 sessions per device or channel, to avoid conclusions drawn from three visits. The module checks:

  • the biggest leak in the funnel between two steps;
  • the share of sessions that enter the checkout and place an order;
  • the conversion gap between mobile and desktop;
  • channels that bring traffic without any order, and the best converting channel;
  • the most viewed product among those rarely added to cart;
  • the page with the most rage clicks and dead clicks;
  • a rise or fall in traffic of at least 20%.

The conversion funnel

The funnel counts sessions. A session ends after 30 minutes of inactivity. Each session is counted at the furthest step it reaches, and in all previous steps: the funnel always narrows.

  1. Visit: any page view.
  2. Product page: a product page is viewed.
  3. Add to cart: detected server-side, whatever page the add comes from.
  4. Cart page: the cart is displayed.
  5. Checkout: the visitor enters the checkout.
  6. Address: address step of the standard checkout, detected in the browser.
  7. Shipping: carrier choice, detected in the browser.
  8. Payment: payment step, detected in the browser.
  9. Order placed: recorded server-side when the order is validated, then confirmed by the confirmation page.

The detailed table shows, for each step, the sessions that reach it, their share, the sessions lost since the previous step, the drop-off rate and the sessions that triggered the step itself. An add to cart from a category page, for example, skips the product page. Rows with a drop-off above 30% or 50% are highlighted.

The vs previous period column gives the change in the share of sessions, in points. The Conversion by device table compares desktop, tablet and mobile. The Export CSV button downloads the funnel with the current filters.

Acquisition

Each session is linked to a channel, based on the domain of the referring site (only the domain is stored), UTM tags and ad click identifiers.

  • Direct: no referring site and no UTM tag.
  • Organic search: search engines (Google, Bing, Qwant, DuckDuckGo, Ecosia…).
  • Paid ads: Google Ads or Microsoft Ads click identifier (gclid, msclkid), or a utm_medium such as cpc, ppc, paid or display.
  • Social networks: Facebook, Instagram, TikTok, LinkedIn, Pinterest, X, YouTube…, or a link carrying fbclid or ttclid.
  • Email: utm_medium=email or a webmail (Gmail, Outlook…).
  • Referral sites: any other site.
  • Other campaigns: a UTM tag that matches none of the cases above.

Returns from a payment page (PayPal, Stripe…) do not count as a source: they never replace the real origin of the visit.

The tab shows the channels (sessions, share, bounce, add to cart, conversion, orders and revenue), then the sources, the utm_campaign campaigns, the landing pages with a link to their heatmap, and the split between new and returning visitors. Click a channel to open the funnel filtered on that channel.

Products

For each product: views (one per session), first adds to cart, orders, quantities sold, add-to-cart rate and view-to-order rate. Four sorts are available: Most viewed, Most added to cart, Most ordered and Opportunities.

The Opportunities sort lists products viewed at least 20 times whose add-to-cart rate is below half the store average. They attract visitors, but something stops them: price, photos, description, stock or delivery time.

The heatmap

Choosing a page

Pages are grouped by type (home page, products, categories, cart and checkout…) and ranked by number of views. The search field filters by title or address. The most viewed page loads automatically. The Pages to watch block, at the top of the tab, lists the pages with the most rage clicks and dead clicks.

The page is shown in a preview at the most common screen size of its visitors, for the chosen device (desktop, tablet or mobile). Scroll the preview: the heat layer follows.

Each click is placed back on the element the visitor clicked, at the same position inside it, whatever their screen width, the height of their page at the time of the click or a sticky header. Clicks on a fixed element (an add-to-cart bar at the bottom of the screen) stay on it while you scroll. If the element does not exist or is hidden in the preview (closed menu, closed modal), the click falls back on its original coordinates. In the preview, consent banners are hidden and only the store’s own scripts run: third-party scripts (tags, chats) are blocked.

The three modes

  • Clicks: click heatmap, from yellow (few clicks) to dark red (many).
  • Scroll: share of visitors who reach each height of the page, with the average fold line.
  • Frustration: markers for rage clicks (red) and dead clicks (grey). Nearby clicks are grouped and their number is shown.

A rage click is a series of 3 clicks within one second on the same spot. A dead click is a click on an image or an element that looks clickable, with no reaction from the page.

Segments and clicked elements

The segment selector shows All visitors, buyers only (sessions that placed an order) or non-buyers only. The side panel ranks the most clicked elements with their rage clicks and dead clicks. Hover an element to locate it in the preview.

The preview loads the store page inside the back office. The store and the back office must be on the same domain, and the server must not send X-Frame-Options: DENY: use SAMEORIGIN.

Weekly email report

Every Monday, an email sums up the past week (Monday to Sunday) compared with the week before:

  • sessions, orders placed, conversion rate and tracked revenue, with their change;
  • up to 4 points to look at first, taken from the recommendations;
  • the funnel in 5 key steps (visit, product page, add to cart, checkout, order placed);
  • the top 5 acquisition channels with their conversion and revenue;
  • a button that opens the dashboard on that week.

Report settings

In Settings > Weekly email report:

  • Send a report every Monday: enabled by default.
  • Recipients: one address per line. Left empty, the report goes to the store email.
  • Report language: the store language by default. The report is available in French, English, Spanish, German, Italian, Dutch, Polish and Portuguese.
  • Save and send a test: sends last week’s report to the recipients right away.
  • Preview last week: opens the report in a new tab, exactly as the recipients will see it.

When is the report sent?

No cron job is needed. The first visit recorded on Monday triggers the send, after the visitor has received their response, so they do not wait. A lock prevents two sends for the same week. No email is sent after a week without visits. After installing or upgrading, the first report goes out the following Monday.

The report uses the PrestaShop email configuration. If emails are disabled in Advanced parameters > E-mail, a warning is shown in the settings. The links in the report open the back office without a security token: PrestaShop asks for a confirmation before showing the page, which is expected.

Filters

The reports share a filter bar: period (7, 30, 90 or 365 days, or custom dates), device, channel (dashboard and funnel) and store in multistore. Filters are kept when you move from one tab to another.

Settings

Tracking

  • Enable tracking, then enable the conversion funnel and the heatmap separately.
  • Heatmap sampling (1 to 100%): share of sessions recorded for the heatmap. The funnel always records every session.

Privacy

  • Respect Do Not Track and Global Privacy Control: enabled by default.
  • Cookieless mode: the session lives in the browser tab. Unique visitors are no longer counted.
  • Data retention in days (90 by default). Older events are deleted automatically, at most once an hour.

Exclusions

  • Track logged-in employees: disabled by default, browsers logged into the back office are not counted.
  • Excluded IP addresses: one per line, exact address, CIDR range (192.168.1.0/24) or prefix (10.0.*). Your current address is shown.
  • Exclude this browser: sets an exclusion cookie, handy on a phone or a computer not logged into the back office.

Maintenance

The Data maintenance block shows the stored volume and offers three actions: purge beyond retention, generate a new tracking key and delete all data.

Privacy and GDPR

  • No IP address, no email and no form field value is stored.
  • Only the text of clickable elements (buttons, links) is kept, and no text at all on account and order pages. Emails and long digit sequences are masked in the browser, then on the server.
  • First-party technical cookies: dffh_sid (session, 30 minutes), dffh_vid (anonymous visitor, 13 months) and dffh_optout (exclusion). Cookieless mode removes them.
  • Bots and audit tools (Lighthouse, PageSpeed…) are ignored.
  • The tracking endpoint only accepts POST requests signed with a tracking key, and only addresses of your store are recorded.

Depending on your own assessment and your DPO’s, you can mention this tracking in your privacy policy or enable cookieless mode.

Troubleshooting

No data appears. Check that you are not testing from a browser logged into the back office or from an excluded IP address, and that Do Not Track is not enabled in your browser. Clear the PrestaShop cache after installing if a full-page cache is active.

The address, shipping and payment steps stay at zero. They rely on the standard PrestaShop checkout (Classic and Hummingbird themes). A third-party checkout module may not expose them. The other steps, including the placed order, are still tracked server-side.

The heatmap preview stays empty. The store and the back office must be on the same domain, without an X-Frame-Options: DENY header.

The weekly report does not arrive. Use Save and send a test: a message tells you whether the send failed, emails are disabled or a recipient is missing. Also check the spam folder.

Uninstalling

Uninstalling removes the tab, the hooks and the settings. Collected data is kept by default. To delete it, enable Delete the data when uninstalling in the settings before uninstalling: the 6 module tables are then dropped.

Was this page helpful?

Still stuck? Contact support