Skip to content
Audience

One person, from first visit to loyal customer.

Audience is where you keep the people you know. Visits, form submissions, imports and connected systems all land on one person, with what they have agreed to, and you decide what happens as they move through the funnel.

What it does

One record per person

Several emails, phone numbers and keys from other systems on one person. A verified identity belongs to only one person, and a duplicate can be merged. A merge can be reversed.

Consent you can see

Each person carries which channels they have agreed to, and on what basis. Audience never sends to a channel a person has not agreed to or has opted out of, and checks again at the moment of sending.

A lifecycle you design

Awareness, Acquisition, Conversion, Retention and Advocacy, each a state machine you shape on a canvas, with actions such as sending a message. A preset for each stage gets you started.

Audiences and scoring

Define an audience as a rule over a visit and, for someone who agreed to be recognised, what you know about them. Give an audience points and a person’s score follows their membership.

Broadcasts and sends

Send one message to a whole audience on a day you choose, or a message to one person when something happens to them. Write it in Audience, or build it as a page in Content.

Reports

Funnel, activity, forms, audiences and sends: counts from what Audience already records. A report never lists people; you follow its link to see them.

Made to respect the person

A visitor is linked to a person only if they agreed to be recognised on that device. Without that agreement your site still gets an answer, worked out from the visit alone, and it says why.

Forgetting a person removes them from Audience and from every app that holds data about them in your organization, and leaves a receipt. If it cannot be completed everywhere, nothing is partly removed.

Connected to the rest of the suite

Forms

Add the ebitex Audience plugin to a form and each submission is recorded as a person.

Members-only pages

Restrict a site, a section or a page in Content to an audience. Where it matters, ask a visitor to prove their email with a one-time link.

Personalized pages

Your site asks which audiences a visitor is in, and Content varies the page to match.

Connected systems

Bring Stripe customers in as people and record what happens to the email you send through SendGrid. A connection pauses, rather than fails, if a subscription lapses.

Plan it as a campaign, watch it from Hub

Campaigns

A campaign is a named, dated piece of work that spans your apps, planned in Hub: a lifecycle from Draft to Closed, readiness checks before it goes live, and the work each app holds for it on one page.

Broadcasts that wait for it

A broadcast made for a campaign waits until the campaign is live. List your own hosts and its links are tagged, so your analytics can tell which campaign brought a visitor.

Dashboards

Build organization dashboards in Hub from figures your apps provide, Audience’s reports among them. A tile shows only what you could open yourself.

Tasks and notifications

Work no app owns becomes a task with an assignee and a due day. My tasks gathers yours, and the bell in every app tells you when something needs you.

For developers

A Management API lets your own server identify a visitor, and read and write people. A delivery API tells your site which audiences a visitor is in, and signs a short-lived claim for members-only content. Both use keys you create in the app.

The guides, the API reference and the changelog are on the developer site.

Ready to know your audience?

Start with a 14-day free trial of Pro, no card required. The number of people is limited by plan; see Pricing for the numbers.