Skip to content

Automation · Operations and reporting

Ask on WhatsApp which pages of your site are losing sales, with Contentsquare

Ask on WhatsApp where your site loses sales: an AI agent queries Contentsquare and tells you which pages and errors weigh most.

How do I know which pages of my site are losing sales without opening Contentsquare?

You write to your Met "where are we losing sales this week?". The Met finds your site's project in Contentsquare, finds the purchase goal, pulls the period's bounce rate and conversion and ranks page groups by lost conversions. If your account has experience monitoring, it also ranks errors by their impact on that goal. It replies with the three pages that lose the most and the errors that weigh most. It changes nothing: the connector is read-only, and each analytics call counts against your plan's allowance.

What starts it

When someone asks for it

It starts when someone on the team asks the Met on WhatsApp where sales are being lost. Each query runs on request; this procedure does not leave a scheduled report.

A manual task: someone on the team runs it with a button, or asks the Met for it in chat.

Who runs it

Site analytics Met with Contentsquare

This is not a named, seeded Met. It is an internal Met with Contentsquare connected: its work ends when it tells you which page groups lose the most conversions and, if it applies, which errors weigh most, or when it tells you which goal or project it did not find.

Run by the data analyst Met

Channels: WhatsApp

What you need connected

5 steps · 6 tools

The procedure, step by step

Each step shows the tool that runs. They belong to the real connector: if one of them stopped existing, this page would not build.

  1. 1

    Find the project

    The Met lists the Contentsquare projects the connected account sees and picks your site's. If there are several, it asks you which, because Contentsquare recommends always naming the project.

  2. 2

    Find the purchase goal

    The Met searches the configured goals for the one that marks a purchase or an order. This search is configuration and does not use your plan's allowance.

  3. 3

    Pull the period's metrics

    The Met computes site metrics for the week you asked about, such as bounce rate, and compares them with the previous week so you can see whether something moved.

  4. 4

    Rank the pages that lose the most

    The Met brings the page groups from the project's mapping and ranks them by lost conversions. That tells you, for example, whether the problem is on the product page or in the cart.

  5. 5

    See which errors weigh on purchases

    If your account has Contentsquare's experience monitoring, the Met ranks errors by their impact on the purchase goal. If it does not, it says so and answers with the pages only.

Before you start

What you need ready

The Met solves none of these for you. If one is missing, the automation stops there.

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

FAQ

Questions about this automation

One question can use several calls, but only the ones that return analytics count. Finding the project, the goal or the page groups is configuration and is not counted.

Yes: site metrics can be grouped and filtered, and Contentsquare gives comparing conversion between mobile and desktop users as an example.

Contentsquare stops processing new queries until the allowance resets. On Pro and Enterprise you can buy additional capacity.

No. The Contentsquare MCP is read-only: it queries your data and does not create or edit anything.

Keep going

Other automations built on the same tools

Want this automation running on your own data?

We will show it to you with your accounts connected, not with a canned demo.