Six ready-made GA4 audience recipes for remarketing to people who talked to you and excluding customers, open deals and unhappy contacts from acquisition.
Once Karmaflow.ai sends your conversations, deals and tickets to Google Analytics 4, you can turn them into audiences: people who talked to you and did not book, customers you should stop paying to acquire, contacts with a deal already open. You build the audience in GA4, and GA4 shares it with your linked Google Ads account. The Google Analytics 4 page gives you each recipe with the event names from your own event map, ready to copy.
Open Settings (the gear icon) → Integrations → Google Analytics 4 (sign-in required). Scroll to 4 · On Google's side (we cannot do these for you). Under the list you will find Audience recipes.
Each recipe shows:
The recipes read your event map as it is on the page. If you rename an event in section 3, the recipe follows the new name. If you have unsaved changes, the recipes already reflect them and say so; save the map before building anything in GA4.
| Recipe | Use | Built from | Membership |
|---|---|---|---|
| Talked to you, did not convert | Remarketing | a conversation_outcome event, excluding anyone who sent generate_lead or purchase |
30 days |
| Existing customers | Exclusion | purchase, sent when a deal moves to closed won |
540 days |
| Open pipeline | Exclusion | deal_stage_changed, excluding purchase and deals moved to closed_lost |
90 days |
| Unhappy conversations | Exclusion | conversation_outcome with sentiment of negative or very_negative |
90 days |
| Low satisfaction score | Exclusion | csat_received with score of 1 or 2 |
90 days |
| Support only | Exclusion | ticket_created, excluding anyone who became a lead or a customer |
180 days |
Event names in the table are the defaults. The page prints yours.
Low satisfaction score and Support only start with Needs an event turned on, because the satisfaction and ticket events are off by default. Turn on CSAT survey received or Ticket created in section 3 and save. Those events stay off by default for a reason: a support ticket looks like demand to a bidder, so do not mark them as key events unless they really are conversions for you.
If a parameter such as sentiment or deal_stage is not offered in the condition picker, register it first: Admin → Custom definitions → Create custom dimension, scope Event, parameter name as the recipe prints it.
A new audience starts filling from the moment you save it. It then shows in Google Ads under the shared audience list for the linked account, usually within a day. Add remarketing audiences to a campaign's targeting and exclusion audiences to its exclusions.
Google Ads can show an ad only to someone GA4 has seen in a browser. Karmaflow.ai ties a contact's events to their browser through the web identity captured when they chatted, submitted a form or clicked a tracked link on your site. Callers, text-only and Local Services contacts who never visited have none: their events are not sent, so they join no audience. If you turn on the synthetic option in section 2, their events are sent under an id no browser carries, so an audience can count them but Google Ads still cannot reach them. The Last 7 days line in section 5 shows how many events had no web identity.
You decide which audiences to build and how to use them in Google Ads. Google's personalised advertising policies apply to your audiences and campaigns, and you are responsible for following them.