Mumble Tracker: Install Guide & 16 Events

Summary

Mumble Tracker is a snippet of JavaScript you embed on your business website to track visitor actions. When a visitor becomes a WhatsApp customer, the information the tracker collected about their journey on your site is saved automatically to the customer record, including click source, UTM, and the Facebook or Google click ID. This article covers how to install the tracker, which 16 events you can track, and how to read the reports. If you run paid campaigns, this is a tool that completes the picture.

What Mumble Tracker is

The tracker is a JavaScript snippet you install on your website’s pages. It is conceptually similar to the Facebook pixel or Google Analytics, but with a specific purpose: to connect website activity with WhatsApp conversations in Mumble.

How it works in practice:

A visitor arrives at your site through an ad.
The tracker identifies the visitor and stores data: UTM, click source, what they viewed, whether they added something to the cart, whether they completed an order.
If the visitor opens a WhatsApp conversation with your business (for example, through CTWA or a WhatsApp button on the site), Mumble links the visitor to the new customer.
All the data the tracker collected is saved to the customer record in the Marketing section.

That means you know not only that the customer came from a particular campaign, but also which pages they viewed, which products, and what stage of the purchase they were at.

What the tracker can and cannot do

What it can do

Track 16 different types of events on the site.
Save click details and UTM details to the customer record.
Connect a website journey with a WhatsApp conversation.
Display aggregate reports on events and users.

What it cannot do (as of today)

Trigger automatic campaigns. If a visitor abandons a cart, the tracker records the event, but it does not directly trigger a WhatsApp message.
Trigger automations. The tracker is used for measurement and attribution, not for directly triggering automation flows.
Replace the dashboard. The data the tracker collects is shown in the dashboard and in the customer record.

In short: the tracker is a measurement and attribution tool, not an automation tool. But the data it collects is passed automatically to the customer record, and that is real value for anyone running paid campaigns.

Where you install the tracker

In the Mumble menu there is a section called Mumble Tracker. On this page you will find:

Mumble Tracker ID. A unique UUID for your account. This is the ID the code uses to identify that the events belong to your account.
Show Code button. Opens the full JavaScript code to copy.
Events table. A list of all 16 available events with code examples.
Analytics dashboard. Reports on events that have already been collected.

Installation steps

1. Get the tracker code

On the Mumble Tracker page, click Show Code. A window will open with a <script> snippet.

2. Add the code to your site

Paste the code inside the site’s <head> tag so that it loads on every page. On common platforms:

WordPress. Use a plugin like “Insert Headers and Footers” or add it to the theme’s header.php file.
Shopify. In the theme editor, open theme.liquid and paste it before </head>.
Wix. Settings → Custom Code → Add Custom Code → choose the Head location.
Custom site (React, Next.js, Vue). You will need a developer to add the code to the main layout.

3. Verify the code is working

Visit your site after installation. On the Mumble Tracker page in the dashboard, after 5–10 minutes, at least one PageView event should appear. If it does not, the code is not loading or was not installed correctly.

The 16 supported events

The PageView event fires automatically on every page. The other 15 events have to be wired manually to the relevant places on your site.

Mumble Tracker’s 16 events
Display name	Code name	When to track
PageView	pageview	Automatic, on every page
Lead	lead	Lead form submission
Contact	contact	Contact details filled in
Content View	contentview	Viewing specific content
View Product	viewproduct	Viewing a product page
View Category	viewcategory	Viewing a category page
Add to Cart	addtocart	Adding a product to the cart
View Cart	viewcart	Viewing the cart page
Add Payment Info	addpaymentinfo	Entering payment details
Begin Checkout	begincheckout	Starting the checkout process
Purchase	purchase	Completing a purchase
Search	search	Searching the site
Share	share	Sharing content
Comment	comment	Commenting on content
Subscribe	subscribe	Subscribing to a newsletter
Complete Registration	completeregistration	Completing account creation

Note: the display name is View Category, but in the code you need to use viewcategory. This is a common mistake.

How to fire an event

Every event is fired with a JavaScript call like this:

mumt('track', 'eventname', { params });

For example, to add a product to the cart:

mumt('track', 'addtocart', {
  cartValue: 199.90,
  productID: 'SKU-12345',
  productName: 'Blue Shirt',
  productCategory: 'Clothing',
  productVariant: 'M',
  quantity: 1
});

This code should run the moment the user clicks “Add to Cart” on the site. This usually requires a developer to add a line to the button’s click event.

Examples of common flows

A full e-commerce funnel

The order of the events you want to track:

PageView. Automatic on every page.
View Product. On a specific product page.
Add to Cart. On clicking “Add to Cart.”
Begin Checkout. On entering the checkout page.
Add Payment Info. On entering credit card details.
Purchase. On the order confirmation page.

If you track all six, you can see exactly where on the site you are losing customers, and distinguish between customers on a long purchase journey and customers who complete a purchase quickly.

A lead-generation funnel

PageView on the landing page.
Search if there is search on the site.
Lead on filling in a contact form.
Subscribe on signing up for a newsletter.

Reading the analytics dashboard

On the Mumble Tracker page, below the settings section, there are two data areas:

Events and users table

A table with a row for each event. In each row you see:

Event name.
Event count. How many times the event was created in total.
User count. How many unique visitors created an event of this type.

The gap between the two numbers tells you something. PageView with 1,000 events from 200 users = an average of 5 pages per user. Lead with 25 events from 20 users = some users submitted the form twice, perhaps by mistake.

Time graph

A line graph that shows event volume over time. Useful for spotting spikes after a campaign, sharp drops that indicate a fault, or a weekly pattern that helps you time upcoming campaigns.

Integration with Facebook and Google ads

This link lets you track the full customer journey, from the ad to the conversation. Example:

You run a Facebook campaign that leads to a landing page.
A visitor clicks the ad and lands on the page. The tracker remembers the UTM and fbclid.
The visitor sees a WhatsApp button on the page and clicks it, or starts a conversation through a CTWA ad.
The WhatsApp conversation opens. On the new customer record in Mumble, in the Marketing section, you see: campaign_id, ad_id, UTM source, and all the click IDs.
You know exactly which campaign brought the customer, which page they viewed, and maybe even which product.

This link is created automatically. You don’t need to do anything except make sure the tracker is installed.

For more on how the data is used in campaigns, see CTWA, the complete guide.

Best practices

Start with PageView and Lead. These two events provide most of the value. If only these are installed, you already have a good picture. Add more events gradually.
Record every possible parameter on each event. The parameters are not required, but without them the reports will be thin. It is better to include all the specs.
Use a standard currency. ILS, USD, EUR, GBP. No free-form names.
Test after every change to the site. If you redeveloped the site and changed the checkout, Begin Checkout events may stop working. Monitor after a deploy.
Compare the tracker to the Facebook pixel. If you have a Facebook pixel installed, the events should be similar. Large discrepancies between the two indicate an installation problem.
Use the data in the customer record. When an agent sees a new customer, information about the campaign that brought them and what they viewed on the site helps tailor the conversation.

Common issues

I installed the tracker but events aren’t showing in the dashboard

Check:

The code is actually installed on every page (sometimes it is installed only on the home page).
The Tracker ID in the code matches the ID shown on the Mumble Tracker page.
There are no JavaScript errors on the site stopping the tracker from loading. Open DevTools and check the Console.
You don’t have an ad blocker active. It can block the tracker.

PageView works but other events don’t

PageView fires automatically, but the others have to be wired manually on the site. If only PageView works, it means the code for the specific events was not installed. Talk to your site developers.

Events appear but the data in the customer record isn’t updating

The link between visitor and customer happens when the visitor opens a WhatsApp conversation from the same browser and the same session. If the customer moved to a different browser or device, the link will not happen. This is a technical limitation of the cookie mechanism.

I see a lot of PageView events but few new customers

This is normal—most visitors do not become customers. In many industries, conversion rates of 1–5% are common. If you want more visitors to become customers, invest in clearer calls to action on your pages, or run a CTWA campaign.

The report isn’t showing data for the past month

If the report is not showing data from the recent period, check that the tracker is still installed on the site and that new events are still being sent. If it is unclear, contact Mumble support to check the situation specific to your account.

I want to track an event that isn’t in the list of 16

As of today, only the 16 standard events are supported. If you need a custom event, contact Mumble support and request the addition. In the meantime, use Lead or Content View with custom parameters.

The bottom line

Mumble Tracker is a measurement and attribution tool that connects the activity on your website with the WhatsApp conversations you manage. Installation is a one-time, quick task. The value materializes when you start seeing leads arrive with full context: which campaign they came from, what they viewed on the site, and what stage of the purchase they were at. Even though you cannot trigger automatic campaigns from the tracker itself, the data it collects is the foundation for smarter campaigns and more tailored conversations.

Want to Use WhastApp API?

Mumble Tracker: Installation, Setup, and What It Measures

Mumble Team