Suppress existing customers from prospecting campaigns
Support submissions build a Customer Match list you exclude from prospecting, so budget goes to people who have not bought.
New Submission on your "Existing customer support" form
Add the contact to a Customer Match exclusion list in Google Ads
One-directional. A submission triggers the action — nothing is written back into your form.
Prospecting campaigns have no idea who already bought. An ecommerce brand can spend a chunk of its acquisition budget showing first-purchase ads to the same people who are emailing support about an order from last week.
Every support submission carries the thing needed to stop that: a verified contact address. This flow feeds those addresses into a Customer Match list that sits on prospecting campaigns as an audience exclusion. Retention and win-back campaigns can point at the same list from the other direction, targeting it rather than excluding it.
Setting it up
- 1
Publish the support form with Email Address required — an exclusion list is only as useful as its match rate, and email is the strongest key.
- 2
In Audience manager, create a customer list named "Existing customers — suppress" and keep it separate from any list you target.
- 3
Set up the Zap with formformform's New Submission trigger on the support form, then Google Ads "Add Contact to Customer List" pointed at that suppression list.
- 4
Map Email Address to the email input and Phone Number to the phone input so a customer who used a throwaway address can still match on their number.
- 5
Add a Zapier filter on Order or Account Number so only people with a real order reference are suppressed — pre-sale questions should stay in the prospecting pool.
- 6
Split Customer Name into first and last name with a Formatter step to lift the match rate on the addresses Google cannot resolve alone.
- 7
In Google Ads, attach the list as an audience exclusion on every prospecting campaign, and deliberately leave it off retention and win-back campaigns.
- 8
Submit a test complaint with an order number, confirm Zap history shows the contact added, then re-check the exclusion is still attached after any campaign is copied or rebuilt.
What maps where
Using the Customer Complaint Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Google Ads |
|---|---|
| Email Address | Email identifier on the suppression list member |
| Phone Number | Phone identifier on the same list member |
| Customer Name | Split into the first name and last name inputs on the customer list upload |
| Order or Account Number | Zapier filter — only submissions carrying an order reference reach Google Ads |
| Complaint Type | Zapier path routing returns and refunds to a separate win-back list |
Variations worth knowing
Take the branch where Complaint Type is a return or refund into its own Customer Match list, then target it with an apology-and-offer campaign. The upload is identical; the difference is whether the list is attached to a campaign as an exclusion or as a segment.
A complaint form catches only unhappy customers. Point your warranty claim, refund request and account cancellation forms at the same Customer Match list with their own Zaps, so the suppression covers everyone who has bought rather than the small share who complain.
If something isn't arriving
Check the exclusion is applied at campaign level and not just on one ad group, and that it was added to campaigns created after you set the list up. Matching also depends on the person being signed in to a Google account with that address, so expect some leakage.
The filter on Order or Account Number is letting blanks through. Set the Zapier filter condition to "exists" and "is not empty" rather than a text match, and make the field required on the form so pre-sale enquiries cannot reach the Google Ads step.
Frequently asked questions
Can one Customer Match list be excluded and targeted at the same time?
Yes. Exclusions and targeting are set per campaign, not on the list itself. The same list can sit as an exclusion on your prospecting campaigns and as a targeting segment on a retention campaign, which is what makes a single suppression list worth maintaining.
If I close a support ticket, does the person leave the list?
No. The flow only adds — the connection is one-directional, so nothing in Google Ads is changed by activity in your helpdesk or by editing a response. Removing members is a separate job you do in Audience manager or with a second automation.
How long do contacts stay in the suppression list?
Until the membership duration you set on the list lapses, or until you remove them by hand. Nothing takes people out automatically, so if your customers churn, plan a periodic clean-up rather than assuming the list stays accurate for ever.
Related automations
- Add webinar registrants to a remarketing list
Every webinar registration joins a Customer Match audience you can run follow-up campaigns to after the session.
- Build a Customer Match audience from quote requests
Each quote request adds the lead to a Customer Match list you can retarget across search and display.
- Grow a seed audience from newsletter subscribers
Each new subscriber joins a Customer Match list that seeds targeting towards people who resemble your readers.
- Record an offline conversion from a captured GCLID
A hidden GCLID field turns each demo request into a valued offline conversion Smart Bidding can learn from.
- Report a completed application as a qualified-lead conversion
A completed application reports a valued offline conversion to the specific conversion action you bid on.
- Capture webinar registrations as track events
Each webinar signup fires a "Registered" event tied to the work email and session name, so reminders and reporting agree.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free