AboutStoriesNewsroomLabPricingEvents
Ask GaganGet started
  1. Stories
  2. Google

Explore

  • Home
  • About
  • Stories
  • Newsroom
  • Archive
  • Events
  • Pricing

Connect

  • Ask
  • Book a call
  • Send an email

Resources

  • Documentation
  • Media Kit
  • Release Notes
  • Lab
  • Site Map
  • RSS Feed

Legal

  • Privacy
  • Terms of Use
AI site summary·AI full corpus

Copyright © 2026 Gagan Malik. All rights reserved.

Privacy|Terms of Use|Site Map
  1. Stories
  2. Google

Better onboarding and activation

4 min read

10M

Users

2M+

Publishers

22→41%

Activation

Google Ads helps advertisers reach people across websites and apps. Publishers monetize with products such as AdSense so pages readers use can stay free.

Company website

10M

Users

2M+

Publishers

22→41%

Activation

Overview

The snippet sits in your clipboard and the revenue line stays flat. Auto Ads could find inventory site owners missed, but most publishers never finished setup. One tag, scattered docs, and a black-box story about ML meant capable tools sat idle while manual placements felt safer. The job was not to explain the algorithm louder. It was to meet each publisher where they stalled and get them to the first impression.

My role

I led product design and onboarding strategy for Google AdSense Auto Ads, designing segmented email flows to improve publisher activation and reduce setup friction.

The opportunity

Two million publishers, one snippet, and a 58% cliff before the first ad shows

Auto Ads used machine learning to place ads and surface inventory owners overlooked, yet adoption lagged behind the product's depth. The integration was a single snippet, but it read opaque if you did not ship code every day. Manual placements stayed familiar; the ML path sounded like a gamble you could not verify from a kitchen table on a Sunday night.

My JTBD research surfaced three blockers: unclear value (why trust ML over hand-placed units?), technical confusion (where does the snippet actually go on WordPress versus a custom CMS?), and verification anxiety (how do I know it is working?). Support tickets showed 'Auto Ads not showing revenue' as the top activation issue. Publisher surveys found 68% did not understand the difference between Auto Ads and manual placements. Funnel analysis showed 58% drop-off between copying the snippet and seeing the first ad impression.

Constraints were strict: no in-product UI changes, email-only intervention. Messages had to work across WordPress, custom CMS builds, and static sites. Success metric upfront: activation above 35% within 30 days of signup.

The solution

Three emails for three stalls: explain, paste, prove

I closed the gap with segmented email so each publisher saw copy matched to where they were stuck, not a generic welcome blast. A single email to all signups could not serve technical and non-technical owners equally; platform diversity across WordPress and custom stacks ruled out an in-product tutorial overlay. I shipped a behaviour-led email journey segmented by signup source and stall point.

Each email had a fixed layout hierarchy: subject line named the stall ('Paste your snippet in 3 steps'), hero screenshot showed the expected outcome (revenue line moving), numbered steps with CMS-specific screenshots, and a single primary CTA ('Verify in reporting') so publishers knew what to do next without opening docs.

I wrote the first email to explain what Auto Ads actually did, with side-by-side examples of ML placements next to manual ones. I wrote the second, sent to publishers who read the docs but never pasted, to walk through code placement with screenshots for common CMS platforms. I wrote the third, sent to those who pasted but saw no impressions, to cover reporting verification and troubleshooting. I wrote follow-ups that carried publisher proof (for example Sarah increasing RPM 28% without touching placements) and deeper technical paths for owners ready for mobile anchor ads, AMP, and cross-device setups.

I validated before scale. A/B tests on subject lines, send timing, and technical depth ran against 50K publisher cohorts before full rollout.

The impact

From 22% to 41% activation, with 35% fewer setup tickets

Activation climbed from 22% to 41% within 30 days of signup after the segmented programme launched, clearing the 35% target I set upfront: segment 2 (paste instructions) recovered the largest stall cohort, and segment 3 (verify impressions) converted publishers who had pasted but never saw revenue move. Support tickets tied to Auto Ads setup dropped 35% quarter-over-quarter because screenshots replaced abstract ML copy at each stall point.

Segmenting email by stall point with CMS-specific paste steps and reporting verification screenshots lifted activation from 22% to 41% and cut setup tickets 35% quarter-over-quarter. The same segmentation patterns later applied to matched content and in-feed ads with similar lift.

Lessons learnt

  • Segmented email meets publishers at the stall point, not at signup vanity.
  • 22→41% activation and −35% setup tickets followed stall-mapped email layout.
  • Peer revenue proof beats feature lists when trust is the real blocker.

Testimonial

“I am not a developer. I used to quit halfway through documentation that only makes sense if you already ship code, so earning stayed out of reach. Short steps, plain English, emails when I stalled, and I went from stuck to earning in days, not lost weekends trying to read manuals I could not follow.”

Site ownerIndependent publisher

In the product

Email wireframe explaining Auto Ads value with ML vs manual placement side by side.

Segment 1 — explain value before asking for paste. Placeholder SVG — replace with annotated screenshot (see project-documentation/CASE_STUDY_PROOF_ARTEFACTS.md).

Email with CMS-specific paste instructions and screenshots for WordPress.

Segment 2 — walk through paste for stalled publishers. Placeholder SVG — replace with annotated screenshot (see project-documentation/CASE_STUDY_PROOF_ARTEFACTS.md).

Email showing reporting verification steps to confirm first ad impression.

Segment 3 — prove revenue line moved after paste. Placeholder SVG — replace with annotated screenshot (see project-documentation/CASE_STUDY_PROOF_ARTEFACTS.md).

  • Media in this story

    Download all images

More

View all

Simplifying sales reporting

7 months ago

Improving restaurant order tracking

8 years ago

Gamified car insurance

1 year ago

From Hold to Handled

1 year ago

Better product discovery

10 months ago

Faster checkout

11 months ago

Predictable spend forecasting

9 months ago

Service requests made faster

8 years ago

One workspace for team collaboration

8 months ago

Expert travel guides

3 months ago

Loyalty for food lovers

3 months ago

Better team collaboration

1 year ago

Ready to take the next step?

Choose the right plan for your team.

Get startedBook a call