Research

/

2026

WhatsApp Ads: Why Clicks Didn’t Become Downloads.

WhatsApp’s ads were getting people to the App Store, but they weren’t downloading. I found out why: the page wasn’t showing what the ads had promised.

Project details

Company

Meta / WhatsApp

Role

Research lead, end to end

Methods

Unmoderated usability study, between-subjects (n=16)

Year

2026

Overview

The Problem: A WhatsApp ad campaign was celebrated for driving clicks to the App Store, but clicks aren’t downloads, and people were dropping off right at that step. Nobody could say why.

The Method: 16 US iPhone users each watched one of three ads, then reviewed the real App Store page and decided whether to download, talking through their reasoning on a screen recording.

The Core Insight: Every ad made a promise. When the page didn’t keep it, people went looking, and then they left.

The Impact: Reframed the problem from weak ads to an ad-to-page mismatch, and handed off 5 fixes and a 4-experiment test plan to the App Store page and ad creative teams.

Team: I led the research within Meta’s Creative X team, working with WhatsApp’s App Store page team and ad creative team.

What was this?

Lots of clicks. Not many downloads.

WhatsApp was running ads on social media that sent people straight to the iOS App Store. The campaign was being celebrated because so many people clicked through. I was skeptical: a click isn’t a download, and few people in the US use WhatsApp to begin with. People were dropping off at the download step, and nobody knew why.

How did I test it?

Three ads, one App Store page.

Each ad sold a different reason to download, but all three sent people to the same page. I randomly showed each participant just one ad, so I could compare how the page held up after each one:

  • Privacy (“All The Chats”): end-to-end encryption

  • Connection (“Family Ties”): texting, photos, and video calls for family moments

  • Productivity (“Pickleball”): pinned messages in busy group chats

Then they browsed the real App Store page, rated how likely they were to download, and explained why, out loud.

Diagram of how the synthetic panel was built: 400+ real people applied, 135 were screened, and 100 digital twins were built 1:1 from real interviews.
Did people want to download it?

The clearest signal wasn’t a number.

It was people scrolling the page looking for a feature that wasn’t there. Download intent pointed the same way: the ad whose features the page showed landed best (4 of 5), and the ad whose feature was missing landed worst (3 of 6). Directional with 16 people, but behavior and numbers agreed.

Diagram of how the synthetic panel was built: 400+ real people applied, 135 were screened, and 100 digital twins were built 1:1 from real interviews.
How did the page hold up after each ad?

One page, three different reactions.

  • Privacy: mixed. The ad was so abstract that one person couldn’t tell it was a messaging app. The page actually rescued it, but nobody could say why they’d use WhatsApp over iMessage.

  • Connection: thematic, but cold. The screenshots matched the ad’s features, but its warmth disappeared. “Very dated, very clinical, cold.”

  • Productivity: broken promise. The whole ad was about pinned messages, and that feature was in zero screenshots. People scrolled looking for it. “Pinned messages isn’t in any screenshot.”

Diagram of how the synthetic panel was built: 400+ real people applied, 135 were screened, and 100 digital twins were built 1:1 from real interviews.
What came up across all three?

The page had the right ingredients in the wrong order.

  • “Why should I switch from iMessage?” went unanswered, even for people who liked the page. The answer (2 billion users, 180+ countries, works on any phone) was hidden behind a “more” tap.

  • Ratings did the selling. 4.7 stars from 18 million ratings was noticed by nearly everyone and pushed people toward downloading.

  • New users hit the wrong content first. CarPlay and bug-fix notes showed up before any screenshots.

  • “From Meta” hurt trust, most of all for the privacy pitch.

Diagram of how the synthetic panel was built: 400+ real people applied, 135 were screened, and 100 digital twins were built 1:1 from real interviews.
What did I recommend?

Five fixes for two teams, and a plan to test them.

For the App Store page:

  • Move Events and What’s New below the screenshots, so new users see the product first

  • Stop burying “why switch?” Move the 2B users / 180+ countries stat up, or add a screenshot showing it working across iPhone and Android

  • Warm up the screenshots. The one with real people was the one participants responded to

For the ads:

  • Check every ad against the screenshot set before production. If the feature isn’t on the page, reframe the ad

  • Test a tagline that answers “why switch?” “Reliable” read as a baseline, not a reason. Try “Message anyone, on any phone.”

Then four experiments to prove it: two page tests (lead with ratings and privacy; add a cross-platform screenshot) and two ad tests (a Pickleball version about group chat instead of pinned messages; a family-call version where one person doesn’t have an iPhone).

Diagram of how the synthetic panel was built: 400+ real people applied, 135 were screened, and 100 digital twins were built 1:1 from real interviews.
Where does it fall short?

I was upfront about its limits.

  • 16 people shows direction, not proof. Enough to see consistent themes, not to make conversion claims. A live A/B test is the right next step.

  • Unmoderated sessions catch reactions, not deep reasoning. Next time, I’d add a few live sessions to dig into the page critique.

  • iPhone only, by design. Android and global WhatsApp users behave differently, which is a separate study.

What came of it?

Outcome

  • Reframed the problem from “weak ads” to an ad-to-page mismatch

  • 5 prioritized fixes split across the App Store page and ad creative teams

  • 4-experiment test plan handed off, with page and ad tracks running in parallel

  • Flagged the “From Meta” label as a trust risk worth testing on its own

Next project

Meta for Business: Support Panel Usability Testing

Meta for Business: Support Panel Usability Testing

Fieldwork cover