GrowMyAds Popup — Discovery Interview for Heath

Section 01

Trigger — When does it appear?

Question 01

How many seconds after landing should the popup fire?

Too early and you interrupt someone still reading. Too late and most have already bounced. What feels right based on how you'd want to be treated as a visitor?

5 seconds Very aggressive — catches almost everyone 8 seconds Sweet spot — visitor has scanned the pageSuggested 15 seconds Visitor is clearly reading — more intent 30 seconds Only the most engaged visitors see it

Notes on timing

Click below to preview each delay

GrowMyAds

The PPC Agency You've Been Searching For

Top-rated Google Ads management. True industry experts. No contracts.

Question 02

Should exit intent also trigger the popup on desktop?

On desktop, exit intent fires when the mouse moves toward the browser's top bar — a reliable signal someone's about to leave. Note: exit intent doesn't work on mobile (no mouse cursor), so mobile will always use the timer only.

Yes — use both timer + exit intent on desktop Maximum coverage, catches people about to leaveSuggested Timer only — no exit intent

How triggers stack

Desktop
Timer fires at 8s. If visitor moves to close tab before 8s — fires early.

Mobile
Timer only. No cursor = no exit intent possible on mobile.

Both
Once shown, won't fire again same session.

Question 03

Which pages should the popup appear on?

All pages gets maximum reach. Limiting to high-intent pages keeps it relevant and less intrusive on content like the blog.

All pages Maximum reachSuggested Selected pages only Homepage, Services, Case Studies… All pages except… Exclude blog, FAQ, contact, etc.

List pages to include or exclude

WP Admin settings preview

WP Admin → GMA Popup Settings

Show onAll pages

Delay8 seconds

Exit intentEnabled

MobileTimer only

Question 04

Should the popup show on mobile at all?

Mobile uses a timer trigger only (no exit intent). The popup will be fully responsive. The only question is whether to enable it — some teams prefer desktop-only to avoid friction on smaller screens or to protect SEO rankings.

Yes — show on mobile, same timer More reach, responsive design handles the restSuggested Yes — mobile only, but longer delay Give mobile users more time to scroll No — desktop only

GrowMyAds●●●

Get Your Free
Google Ads Audit

Get My Free Audit →

Question 05

If someone closes the popup without filling it, should it come back?

Showing it again on the next visit catches people who were distracted the first time. Longer windows respect the visitor's decision more but capture fewer leads.

Show again on next visit New browser session = fresh start. Most common choice.Suggested Show again after 7 days Show again after 30 days Never show again Requires storing a permanent cookie

How the cookie works

1.Visitor closes popup → browser cookie is set

2.On next page load, popup checks for cookie

3.If cookie found and not expired → popup stays hidden

4.Your choice above sets how long the cookie lasts

Section 02

Form Fields — What do we collect?

Question 06

What fields should Step 1 collect?

Step 1 should be short — friction kills conversions. Goal: get name and email so even if they abandon Step 2, we still have a lead.

First name Personalises follow-upRequired Last name More friction, better for Pipedrive contact Work email Primary contact fieldRequired Company name Website URL Lets team pre-audit before the call

Question 07

What fields should Step 2 collect?

Step 2 is where qualifying happens. Each extra field adds friction — keep it tight. Phone + spend is the core.

Phone number Required for outbound callRequired Monthly Google Ads spend The pipeline qualifierRequired Which platforms? Google / Meta / Microsoft / Other Currently working with an agency?

2-step form — click Continue

Question 08

What are the exact spend ranges for the dropdown?

These values drive the Pipedrive pipeline routing. They need to exactly match what the sales team expects to see. The options below are a starting point.

Your spend ranges (one per line, in order)

Which option triggers Main Pipeline (vs Triage)?

Spend dropdown preview

Monthly Google Ads Spend *

Select your budget…

Under $1,000/mo

$1,000 – $3,000/mo

$3,000 – $5,000/mo ← threshold here?

$5,000 – $15,000/mo

$15,000 – $30,000/mo

Not sure yet

Section 03

Pipedrive — Routing & Integration

Question 09

Confirmed: $3,000+/mo → Main Pipeline. Anything to clarify?

Based on what we know: leads spending $3,000/mo or more → GMA Sales Main pipeline. Anything below (including "Not sure") → Triage Calls pipeline. Does this match exactly, or are there edge cases?

Confirmed — $3,000+/mo goes to Main, below goes to TriageConfirmed Actually a different threshold — see my notes

Any edge cases or exceptions?

Routing diagram

Main Pipeline

GMA Sales Main

$3,000+/mo

Triage

Triage Calls

Below $3k or Not Sure

Under $1,000/mo→ Triage

$1,000 – $3,000/mo→ Triage

$3,000 – $5,000/mo→ Main

$5,000 – $15,000/mo→ Main

$15,000 – $30,000/mo→ Main

Not sure yet→ Triage

Question 10

How does lead data get into Pipedrive right now — and how should it work with the new plugin?

This is a critical technical decision. The plugin needs to know what mechanism puts a lead into the correct Pipedrive pipeline. It's unclear whether this currently happens automatically or manually. What's the setup right now and what should it be?

Currently manual — team enters leads into Pipedrive by hand New plugin should automate this via API Currently via Zapier or Make (automation tool) New plugin could trigger same zap or replace it Currently direct Pipedrive API Plugin can use the same API key Currently via Pipedrive's email-in feature No Pipedrive connection yet for the popup — starting fresh

How it works now (describe the current flow)

How it should work with the new plugin

3 ways the plugin can send to Pipedrive

Option A — Direct API

Plugin calls Pipedrive REST API directly. Needs API key. Creates contact + deal + assigns to pipeline in one shot. Most reliable.

Option B — Zapier / Make

Plugin sends data to a webhook URL. Zapier/Make picks it up and creates the Pipedrive deal. Uses existing automation if one exists.

Option C — Email to Pipedrive inbox

Pipedrive has an email address that auto-creates deals. Plugin sends a formatted email. Simplest, but least control over pipeline assignment.

Question 11

Who gets new deals assigned to in Pipedrive right now — and how should it work?

Currently it's unclear who owns a new inbound deal in Pipedrive before a booking happens. What's the current process and what's ideal?

How it works now (who sees a new lead in Pipedrive today?)

How it should ideally work with the new plugin

Pipedrive user email(s) for assignment (if known)

Assignment options the plugin can handle

Fixed owner

All leads → one specific person's Pipedrive ID

Split by pipeline

Main leads → Person A, Triage → Person B

Unassigned

Deal created with no owner — team claims it manually

Section 04

Post-Submit — What does the client see?

Question 12

After a client hits submit, what should happen?

The moment right after they click. Three options — click any card to see a live mockup.

A

Popup closes quietly

Popup disappears. Visitor stays on whatever page they were reading.

👋

Popup closes — visitor stays on page

No redirect. Salesperson follows up.

Best when: Team responds within hours, no Calendly.

B

Thank you screen inside popup

Popup flips to a confirmation screen. Calendly button optional here.

✅

Thank you, John!

We'll be in touch within 24 hours

📅 Book Your Strategy Call

Best when: You want Calendly but optional.

C

Redirect to Thank You page

Browser goes to /thank-you — full branded page with next steps.

🚀

Full thank-you page

Separate URL — trackable in GA4

Best when: Calendly embedded + conversion tracking.

You're all set, John!

We've received your request

1

We'll review your account and prepare personalised insights

2

A member of our team will reach out within 24 hours

3

We'll walk you through exactly what's holding your ads back

No thanks, I'll wait for your email →

Question 13

Should Main Pipeline and Triage leads see a different thank-you message?

Suggested timelines based on what we know: Main Pipeline → 24 hours, Triage → 48 hours. Does this match your current SLAs?

Same message for everyone — simpler Different message per pipeline Main = faster response promise, Triage = longerSuggested

Main Pipeline — response time promise (e.g. "24 hours")

Triage — response time promise (e.g. "48 hours")

Suggested message routing

Main Pipeline — $3k+

"A member of our team will reach out within 24 hours"

Triage — below $3k

"We'll review your details and be in touch within 48 hours"

Section 05

Calendly — Booking Flow

Question 14

How is the booking process structured right now — and how should it work with the new popup?

Before deciding on a Calendly setup, we need to understand the current booking process. Is Calendly already in use? Does the salesperson reach out manually? What's ideal?

How it works right now (after someone fills out the current form)

How it should ideally work with the new popup

Is Calendly currently being used on growmyads.com?

3 Calendly options

A — Optional button

Thank you screen has "Book a call" button. Client can choose or skip.

B — Auto-redirect

After submit, browser goes straight to Calendly. No choice.

C — No Calendly

Just thank-you message. Team books manually after.

Question 15

Should Main Pipeline and Triage leads go to different Calendly links?

A $15k/mo lead probably shouldn't land on the same calendar as a "not sure" prospect. Routing high-value leads to a senior AE's calendar can improve close rates.

One link for everyone Different link per pipeline Main = senior AE, Triage = SDRSuggested No Calendly for now

Main Pipeline Calendly URL

Triage Calendly URL

Optional Calendly button preview

You're all set!

We'll be in touch within 24 hours

Want to skip the wait? Book a 15-min strategy call now.

Book a Strategy Call

No thanks, I'll wait

Question 16

Should the client's name and email be pre-filled when they land on Calendly?

Calendly supports pre-filling via URL parameters. The plugin can pass name + email automatically so the client doesn't retype them. This works by storing the form data briefly in the browser session. Should we implement this? It improves the booking experience but adds a small amount of complexity.

Yes — pre-fill name + email automatically Plugin passes data via Calendly URL paramsBetter UX No — client fills it in on Calendly themselves

Calendly pre-fill URL format

              // Built from form data in sessionStorage

              https://calendly.com/growmyads/strategy

              ?name=John+Smith

              &email=john%40company.com

Client opens Calendly with name and email already in the fields. One fewer step = more bookings.

Section 06

Backup & Notifications

Question 17

If Pipedrive fails or the connection drops, where should lead data go as a backup?

APIs go down occasionally. A lead that doesn't make it into Pipedrive is a lost opportunity. What's the safety net?

Email to a specified inbox Simplest — always worksSuggested Google Sheet log Every submission logged regardlessSuggested Slack channel ping

Backup email address(es)

Pipedrive

Primary. Creates deal + contact automatically.

Email Backup

Fires on every submit as safety net.

Google Sheet

Running log. Good for reporting.

Slack

Real-time ping on new lead.

Question 18

Should the team get a Slack notification on every new submission?

A quick ping lets the team react immediately without checking Pipedrive. Needs a Slack webhook URL to be set up.

Yes — ping Slack on every submission Yes — but only for Main Pipeline leads High-value leads only No — email backup is enough

Slack channel name (if yes)

Example Slack notification

#new-leads

🎯

GrowMyAds BotToday at 2:14 PM

New Lead — Main Pipeline 🟢

Name: John Smith
Spend: $3k–$5k/mo
Email: john@company.com
Phone: +1 555 000 0000

Section 07

Open Questions

Question 19

Is there anything about the current popup that's working well and should be kept?

Before replacing something entirely, it's worth knowing what shouldn't change — a specific line of copy, a field, a trigger behaviour, anything.

Keep this from the current popup

Question 20

What's the biggest frustration with the current popup setup?

The thing that made us want to replace it — understanding this makes sure the new one doesn't have the same problem.

Main frustration to fix

Anything else?

Other ideas, edge cases, or requirements

Free notes

Before we build theperfect popup