Skip to content
PrestaInsight
Fig. 01 · PrestaShop analytics

PrestaShop analytics, re-specified.

GA4 and Looker Studio treat your shop as web traffic. PrestaShop is not web traffic. It is orders, products, categories, manufacturers, refunds, and customer cohorts. This is what an analytics tool looks like when you start from those.

Fig. 02 · The GA4 problem

Why GA4 falls short of "PrestaShop analytics"

GA4 measures events on a page. PrestaShop has business objects: an order has a status, a customer, line items, a payment method, optional refund history. Once you collapse that into a "purchase" event you lose almost everything you would actually want to analyse.

You can stitch the data back together with a Looker Studio connector and a manual ETL. The cost is the time you spend maintaining it. Most shops we see have either given up on this or pay an agency to do it.

PrestaInsight starts from PrestaShop's own data model. Order rows are order rows. A refunded order is a refunded order. Status changes are tracked. The questions you ask of a sales report ("show me orders by manufacturer", "what is the AOV by category last week", "which products are running materially above their 28-day baseline") are first-class queries here, not custom dimensions.

PrestaShop is not web traffic. It is orders, products, categories, manufacturers, refunds, and customer cohorts.
Fig. 03 · What you get instead

What a PrestaShop-native analytics tool gives you

In practice, these are the four things merchants stop reaching for spreadsheets to compute:

  1. 01

    Order-level KPIs that match the back office

    Revenue includes or excludes VAT consistently. Cancelled and refunded orders are categorised the way PrestaShop categorises them, with timestamps from ps_order_history.

  2. 02

    A real morning summary

    One email at 8 a.m. The product, category, and customer-cohort movements that crossed a threshold. AI-rewritten so it reads as English, not as a CSV.

  3. 03

    Catalog views, not just traffic views

    Top products. Top categories. Top manufacturers. Stock health. RFM grid for customers. Acquisition curves for repeat versus new.

  4. 04

    Team-friendly access

    Invite your developer, accountant, or agency as Viewer. Invite your marketing lead as Marketing role. Five roles, sensible defaults.

Fig. 03 · The dashboards

The same components you see here are what runs in the app.

The KPI cards, the revenue chart, the top-products list, the order heatmap. They render from a seeded fake shop on this site. When you connect a real PrestaShop store they render from your data. No drift. No "the marketing site looked nicer than the product".

Real product
Lampe & Linenlast 30 days
Revenue
€97,386
+€8,288 (+9.3%)vs prev
Orders
1,435
+129 (+9.9%)vs prev
AOV
€68
-€0 (-0.5%)vs prev
Visitors
32,144
+2,890 (+9.9%)vs prev
Revenue trend
confirmed orders · last 30 days
CurrentCompare
€01.2K2.4K3.6K4.9KApr 12Apr 19Apr 27May 4May 11
Top products
  • 01
    Linen napkin set, slate
    124 units-18.6%
    €4,812
  • 02
    Olive linen tablecloth (180)
    59 units-10.8%
    €4,287
  • 03
    Lambswool throw, charcoal
    29 units+20.1%
    €2,252
  • 04
    Stoneware bud vase, oat
    58 units+4.6%
    €1,909
  • 05
    Olivewood serving board
    37 units+11.0%
    €1,731
Fig. 04.A · The actual production components, rendered against the demo dataset. Not a screenshot.
Fig. 05 · Install

How the five-minute install actually works

No GA4 events to wire up. No Webservice API to enable. The module is the integration.

  1. 01

    Sign up on PrestaInsight. Skip the credit card.

  2. 02

    Download the module zip. Upload it through PrestaShop > Modules.

  3. 03

    Paste the one-time setup code from the onboarding screen.

  4. 04

    PrestaInsight backfills 365 days of orders. Done.

Fig. 06 · FAQ

Questions PrestaShop merchants ask first.

Which PrestaShop versions does the module support?

PrestaShop 1.7.6+ and 8.x. We test against both major branches on every release.

Does PrestaInsight need API access or just the module?

Just the module. We do not call the PrestaShop Webservice API; the module pushes data outbound from your server, which is a friendlier model for shared hosting.

Why not just use Looker Studio with the PrestaShop connector?

You can. The trade-off is setup time, ongoing maintenance, and the fact that every new dashboard is a from-scratch project. PrestaInsight ships the dashboards on day one and writes you a morning brief; Looker Studio gives you a blank canvas and a learning curve.

I sell on multiple PrestaShop multistores. Does it work?

Yes. Each shop in a multistore setup becomes its own scope in PrestaInsight, with one combined billing account on Pro.

Fig. 08 · Closer

Want to look at the live dashboard before you commit?

The demo runs on a seeded fictitious shop. Everything works: change the period, sort the order table, click into a top product.

Last 7 mornings · Lampe & Linendemo
  • Mon
    May 5
    Quiet morning. Two anomalies, neither urgent.
    2 cards
  • Tue
    May 6
    "Beeswax pillar candle" broke out — up 22% on the week.
    3 cards
  • Wed
    May 7
    "Stripe linen runner" up 18%. Replenishment recommended.
    2 cards
  • Thu
    May 8
    AOV slipped 4% over the trailing week. Mix shift, not price.
    1 card
  • Fri
    May 9
    No movement worth interrupting. You're free this morning.
  • Sat
    May 10
    "Linen napkin set, slate" hit zero stock at 14:20.
    4 cards
  • Sun
    May 11
    Repeat buyers spiked. 31% of yesterday's orders.
    3 cards
Tomorrow 8:00 a.m. · Already scheduled
Fig. 09 · Some mornings the brief is busy. Some mornings it tells you to go back to your coffee.