You can measure a Shopify WhatsApp button by three counts: button clicks, popup opens, and send taps. Squadkin’s WhatsApp Chat Button records those events per shop, per day, and shows them for a date range as today, a total, and a by-day series. Optional Google Analytics and Meta Pixel events can fire on trackable clicks. None of this is revenue, and none of it is a transcript of the chat.
That limit is the useful part. The button earns its place when people reach WhatsApp with a real question, not when a dashboard invents a sales total. Read the three counts, then read a sample of the actual WhatsApp thread on your phone. The catalog does not connect the two.
What is counted
Click tracking runs on button activation. Engagement tracking adds popup opens and send taps. A click means the button was used. A popup open means the panel was shown. A send tap means someone pressed the control that builds the WhatsApp link. Direct-link mode makes the button itself the link, so the mix of clicks and send taps will differ from popup mode. Compare a shop to its own history, not to a shop on the other mode.
- Today: a same-day check after you move the button or change the greeting.
- Total: the running count, which gets less sensitive as it grows. Do not judge a redesign by the lifetime number alone.
- By day: the series that shows weekends, campaigns, and days you were closed.
The free plan in the catalog includes this analytics tracking together with button design, the popup, business hours, the consent checkbox, and page rules. You do not need a separate analytics tier based on that list. Confirm the screen in the app after install, and give it a day of traffic before you decide the embed is broken. A new shop with no visits will show empty counts for an honest reason.
What is not counted
The catalog does not document a conversion rate, an order total, or revenue attributed to WhatsApp. A send tap is not a purchase. A customer can open WhatsApp, ask a question, buy later on another device, and never connect those events inside this app. If you need revenue, use Shopify’s orders and a method you can explain. Do not label these three counts as sales.
A per-page click report is also not spelled out. Page rules can include or exclude templates and URLs, so you can choose where the button appears, but the dashboard description is date-ranged counts, not a table of product handles. Do not promise a merchandiser a ranking of which product’s button was tapped. If that ranking matters, you would need a tracking setup this catalog does not describe.
The text of the message is not in the dashboard. You will not see sizes, order numbers, or complaints there. Those words are in WhatsApp. Agent choice is not a documented per-agent scoreboard either. The shopper can pick a name, and each name has a number, but the counts described are shop-level clicks, opens, and send taps.
Google Analytics and Meta Pixel forwarding
In the Tracking settings tab you can turn on passthrough to Google Analytics and to a Meta Pixel. The catalog says those events fire on every trackable click, per merchant, when the toggle is on. Use them when your existing property is where the team already looks. Leave them off when you have not told shoppers about those tools in your privacy notice.
A forwarded click is still a click. It does not become a purchase because it passed through a pixel. Check the event in your own property after a test tap. This article does not invent the payload field list.
Consent sits beside this. A checkbox can disable Send and agent links until the shopper ticks it, and the tick is remembered in the browser. It is not a consent archive, and it is not a switch that the catalog describes as blocking analytics. Know which tools load on the page before you call the setup private. The button’s own counts and a pixel are two different pipes.
What you still cannot see
You cannot see the WhatsApp thread, who replied, or how long they took. You cannot see a shared inbox, because there is none in this catalog. You cannot see the WhatsApp Business API, because it is not documented. Hours change the storefront: outside your weekday window the popup text changes and the button dims, and the button stays visible. Those late clicks can still increment the daily count. They do not tell you the reply was on time.
Offline days are worth a look for that reason. A spike in send taps after close means the offline sentence is doing the work, or failing to. Read the sentence. If it promises a fast reply, fix the words. The chart will not fix them for you.
Device and page rules change the denominator. If you hide the button on desktop, desktop sessions are not “failed clicks.” If you exclude a wholesale URL, that page’s silence is by design. Write down the rules next to the chart so a later reader does not treat a quiet day as a broken embed.
A 14-day reading plan
Start the clock on a normal Monday, not in the middle of a sale you will never repeat, unless the sale is the question you are asking. For fourteen days, open the dashboard on the same weekday morning and note the three by-day numbers. Ignore lifetime totals until the end.
- Day 1: send yourself a test. Confirm today’s click, open, and send figures move, and that Shopify admin still has no ticket.
- Days 2 to 7: watch for a gap between popup opens and send taps. A large gap means people open the panel and leave. Shorten the greeting.
- Days 8 to 14: compare open hours with closed hours. Dimmed buttons can still be tapped. The offline text should match what your team does the next morning.
- End of day 14: if you enabled Analytics or Pixel passthrough, confirm those tools show the same kind of click, not a revenue line you did not build.
Decide with a sentence you can defend. “People send from the button on product pages often enough that we will keep it” is a fair reading of send taps plus a look at WhatsApp. “The button made this much revenue” is not a reading this catalog supports.
Questions about button analytics
Does the app track sales from WhatsApp?
No. It tracks clicks, popup opens, and send taps. It does not document a conversion rate or revenue from the chat.
Can I see which page was clicked?
A per-page click report is not spelled out in the catalog. You can limit where the button shows, by page type or URL. The dashboard description is shop-level counts over time.
Will Meta or Google receive the chat?
Passthrough is for trackable clicks, and only if you enable it. It is not a copy of the WhatsApp conversation. The conversation stays in WhatsApp.
The counts are part of the WhatsApp Chat Button page. Install WhatsApp Chat Button when you want those three numbers, and keep your order reports in Shopify when you want sales.