On this page
- How to work out your WhatsApp button CTR
- Where the two numbers come from
- The formula and what goes into it
- Why there’s no “good” WhatsApp CTR to aim for
- How to measure your WhatsApp CTR in WordPress
- Step 1: clicks per page from WhatsLink
- Step 2: views per page from GA4
- Step 3: divide, page by page
- Without a click tracker: GA4 alone
- Reading your rates
- What to try on a low-rate page
- Test one change at a time
- Is the difference real?
- Tell variants apart in the click log
- What WhatsLink gives you for this
- FAQ
- Official sources
How to work out your WhatsApp button CTR
Divide a page's WhatsApp clicks by its views for the same dates and multiply by 100: 12 clicks on 600 views is 2%.
Where the two numbers come from
Clicks per page come from a click log such as WhatsLink, which also catches chat widgets. Views come from GA4's Pages and screens report.
Your WhatsApp button’s click-through rate (CTR) is the number of WhatsApp clicks on a page divided by that page’s views, times 100. There is no reliable public benchmark for it, so the number worth having is your own rate per page, tracked over time and compared before and after one change at a time.
This guide shows where to get both numbers in WordPress, how to read them, and how to run a simple test without a testing tool.
The formula and what goes into it
WhatsApp CTR (%) = WhatsApp clicks on the page ÷ views of the page × 100
Example: 12 clicks ÷ 600 views × 100 = 2%
- Clicks: taps on any link, button or chat widget that opens WhatsApp on that page. A visitor who taps twice is two clicks, so the rate is “clicks per view”, not “share of visitors”.
- Views: page views of the same page over the same dates. In GA4 this is the Views metric.
You can divide by sessions or users instead of views. Any of them works, as long as you keep the same one every time you compare.
Why there’s no “good” WhatsApp CTR to aim for
Figures you find online rarely say how they were measured: which pages, which counting method, which audience. A contact page and a long blog post can sit on the same site with rates that have nothing in common, and both can be fine.
So compare a page with itself over time, and with pages of the same kind on your site. A product page that converts worse than your other product pages is a lead; a blog post that “only” reaches a fraction of your contact page’s rate isn’t.
How to measure your WhatsApp CTR in WordPress
Step 1: clicks per page from WhatsLink
WhatsLink Click Tracker (free) logs every WhatsApp click with the page it happened on, including chat widgets that open WhatsApp from JavaScript. To count one page:
- Open WhatsLink Click Tracker in your WordPress admin.
- Set the date filter to Last 30 days (or Last 7 days).
- Type the page’s title or part of its address in the search box. The total above the table is your click count.
The log stores the full page address, query string included. Visits with UTM tags therefore appear as separate addresses in Top Pages; searching by the page path counts them all together.
Step 2: views per page from GA4
In GA4, open Reports → Engagement → Pages and screens, set the same date range and read the Views column for that page. Any analytics tool that counts page views will do; just use the same dates.
Step 3: divide, page by page
A spreadsheet with one row per page is enough. The numbers below are an invented example to show the reading:
| Page | Views (GA4) | WhatsApp clicks (WhatsLink) | CTR |
|---|---|---|---|
| /contact/ | 400 | 36 | 9.0% |
| /services/kitchen-renovation/ | 2,500 | 30 | 1.2% |
| /services/bathroom-renovation/ | 900 | 27 | 3.0% |
| /blog/renovation-costs/ | 5,000 | 15 | 0.3% |
Here the two service pages are the useful comparison: same kind of page, very different rates, and the kitchen page has almost three times the views. That is where a change is worth testing first.
Without a click tracker: GA4 alone
With enhanced measurement on, GA4 records clicks on links to other domains as a click event with link_url and link_domain, and that includes wa.me links. In an exploration, filter Event name = click and Link domain = wa.me (or api.whatsapp.com), and break it down by page path.
It misses chat widgets that open WhatsApp from JavaScript without a normal link, and visitors whose consent settings block the GA4 tag. The other options are in How to Track WhatsApp Clicks in Google Analytics 4 (3 Ways).
Reading your rates
- Many views, low rate: people reach the page but don’t use the button. Look at the button and the page first.
- Few views, high rate: the page works; it needs more of the right visitors, not a new button.
- A rate that drops suddenly: check that the button still works and is still tracked before you redesign anything. WhatsApp Button Not Tracking in WordPress lists the usual causes.
- Rate per campaign: WhatsLink stores the UTM source, medium and campaign of each click, so clicks per campaign divided by the campaign’s sessions in GA4 shows which traffic actually starts conversations. Tagging is explained in WhatsApp UTM Tracking: Tag Links and Attribute Chats.
What to try on a low-rate page
These are common candidates, not guaranteed wins. What helps on one site does nothing on another, which is why the next section matters.
- Visibility on mobile. Open the page on a phone: is the button visible without scrolling, and easy to tap?
- A recognisable button. WhatsApp offers an official “Chat on WhatsApp” button and recommends using it unchanged, visible and easy to read.
- A label that says what happens next. “Ask about this service on WhatsApp” tells people more than an icon alone.
- Placement near the question. Next to the price, the availability or the booking details, where visitors actually hesitate.
- Desktop visitors. Click-to-chat links also work with WhatsApp Web; a QR code of your wa.me link next to the button is another way to move the chat to a phone.
Test one change at a time
A true A/B split test shows two versions to different visitors at the same time, and needs a testing tool. For most WordPress sites a sequential test is the practical alternative: measure, change one thing, measure again over the same length of time.
- Baseline. Record the page’s CTR week by week for at least two weeks without touching it.
- One change. Change a single thing: the label, the position or the button style. Nothing else on the page.
- Same length. Measure for as many weeks as the baseline, avoiding holidays, sales or new campaigns that change who visits.
- Same sources. Use the same tools and the same counting method for both periods.
- Decide and write it down. Keep the change, revert it, or extend the test, and note what you tried.

Is the difference real?
Your baseline weeks already vary on their own. If the test period’s rate falls inside the range your baseline weeks showed, you haven’t learned anything yet: run it longer or try a bigger change. Only a rate clearly outside that range is worth acting on. Pages with few clicks a week need longer tests.
Tell variants apart in the click log
WhatsLink doesn’t record the device, but it stores the clicked link in full. Give each variant its own pre-filled message, for example a mobile button and a desktop button with slightly different text, and the variants show up as different Clicked URL values. Take views by device from GA4 to compute each rate.
What WhatsLink gives you for this
WhatsLink counts clicks, not page views: you always need GA4 or another analytics tool for the other half of the formula.
- Free: click log with search, sorting and the 7-day, 30-day and all-time filters, Top Pages (top 5), and UTM source, medium and campaign per click.
- PRO: reports for any date range, so baseline and test periods line up exactly, with a daily trend chart, Top Pages and Top Clicked URLs (the ten busiest of each), UTM filters, and a CSV export of every click for your own counts.
If you haven’t set up tracking yet, start with How to Track WhatsApp Button Clicks in WordPress (No Code).
What WhatsLink gives you for CTR
- Every WhatsApp click logged with its page and date
- Chat widgets included: Click to Chat, Joinchat, WP Social Chat
- Search plus 7-day, 30-day and all-time filters to count clicks per page
- Top Pages: your five pages with the most clicks
- The clicked link stored in full, to tell button variants apart
FAQ
What is a good CTR for a WhatsApp button?
There is no reliable public benchmark: published figures rarely say how they were measured, and rates depend on the page, the audience and the placement. Compare each page with itself over time and with similar pages on your own site.
How do I calculate WhatsApp button CTR?
Divide the WhatsApp clicks on a page by that page's views for the same dates, then multiply by 100. For example, 12 clicks and 600 views give a 2% CTR. Clicks come from a click tracker such as WhatsLink; views come from GA4 or another analytics tool.
Can I see WhatsApp CTR in Google Analytics 4 alone?
Partly. With enhanced measurement on, GA4 records clicks on wa.me links as outbound click events, which you can compare with page views in an exploration. It misses chat widgets that open WhatsApp from JavaScript and visitors whose consent settings block the tag.
How do I A/B test a WhatsApp button without a testing tool?
Run a sequential test: record the page's weekly CTR for at least two weeks, change one thing, measure for the same length of time, and compare. Only trust a result that falls clearly outside the range your baseline weeks already showed.
Does WhatsLink show mobile and desktop clicks separately?
No, WhatsLink doesn't record the device. To compare them, give the mobile and desktop buttons slightly different pre-filled messages: the log stores the clicked link in full, so each variant appears as its own Clicked URL.