Audiences

An audience is a group of people defined by their behavior rather than by a fixed list. You describe the kind of person you care about, for example “people who added something to their cart but did not buy”, and leadmaps gathers everyone who currently fits. Because it is based on behavior, the group updates as people’s behavior changes: someone who completes a purchase leaves the “abandoned cart” audience on the next refresh, and someone new who abandons a cart joins it.

Think of it like a smart playlist instead of a hand-made one. You set the rule once (“songs I rated five stars”), and the list keeps itself current as things change, rather than you adding and removing names by hand.

What you see

• A page title that reads “Audiences”, with your saved audiences listed.
• Each audience with its definition (the rules that decide who belongs) and how many people currently match.
• A refresh action that recomputes the membership so you see who matches right now, not who matched when you first built it.

How to read it

An audience is a living answer to “who are the people who did this?”. Read the count to see how big the group is, and refresh when you want the current membership rather than a stale one.

Here is the flow. You define an audience, say “visited the pricing page twice but never started a trial”. leadmaps gathers everyone who fits, and shows you the count. A week later you refresh, and the membership has shifted: some of those people have since started a trial and dropped out of the group, while new people who match have joined. The audience always reflects behavior as it is now, which is what makes it useful for acting on.

Customize it

• Define the rules. Describe who belongs by the actions and traits that matter, for example “did a certain event”, “visited a certain page”, or “has a certain property”. Stack rules to sharpen the group. A single rule gives a broad audience; several rules give a precise one.
• Refresh to recompute. Membership does not update on its own the instant someone changes; refresh when you want the current list. Refresh before you act on an audience so you are working from who matches now.
• Scope to one website. If you track more than one site, keep each audience to the site it is about.

Use cases

• Follow up with people who almost converted. Build an audience of near-misses, like cart abandoners or trial-page visitors who never signed up. Action: refresh it, then reach out to exactly those people with the right message.
• Understand a specific group in your other reports. Define the group of people you care about, then study how they behave across the rest of your data. Action: use the audience to keep your analysis focused on the people who matter, not everyone.
• Track a group over time. Save an audience for a group you want to keep an eye on and watch its size as you make changes. Action: if a “highly engaged” audience grows after a change, the change is working.

Tips

• Behavior, not a fixed list. The strength of an audience is that it keeps itself current. Someone leaves or joins as their behavior changes, so you are never acting on a stale list, as long as you refresh.
• Refresh before you act. The count you see is from the last refresh. When timing matters, refresh first so you are working from who matches right now.
• Sharp rules beat broad ones for action. A precise audience (“abandoned a cart in the last week”) is easier to act on than a vague one (“visited the site”). Add rules until the group is the people you actually want.
• Build the audience around the action you plan to take. Start from what you will do (a message, a follow-up, an analysis), then define the group that action is for.