Audiences

A profile is one person your project knows about. To create one, choose Audiences → Profiles in the sidebar, then Create profile, type the person's Primary identifier, such as a user id or an email address, and choose Create profile. The identifier is the only field, and it's required.

Each row shows the profile's identifier, how many aliases it has, the date it was created, its first three aliases, and when it was last active. The figures across the top count Total profiles, Anonymous ones (with a single alias), Merged ones and those New this week. Search matches any identifier.

To remove a profile, choose Delete in its ⋯ menu and confirm. Its traits and consent records go with it. Changing profiles needs the Manage settings permission, which the Owner and Admin roles have.

• A profile is a person, known by one or more identifiers, called aliases: a browser's anonymous id, a user id, an email address. A profile with a single alias counts as an anonymous visitor.
• Merging joins an anonymous profile into a known one, for example after the visitor signs in on your site.
• Events are things a visitor did, like viewing a page, sent to Content by your website or app. Each event carries the visitor's anonymous id, user id or both.
• Traits are facts you store on a profile, like its plan.
• Segments group profiles by their traits and event counts.
• Consent is recorded per profile and purpose. Only an explicit Denied holds a purpose back: with analytics denied, Content drops that visitor's events, and with personalization denied, slots show them only variants without targeting rules.

Audiences → Anonymous Visitors lists the profiles that have only one alias, with when each was first seen and last active. The figures across the top count Anonymous visitors (with their share of all profiles), Known profiles and those New this week. Search by anonymous id.

When you learn who a visitor is, choose Resolve into known… in their ⋯ menu, type the Known identifier and choose Merge profiles. Content joins the two: the known profile gets every alias, the traits it lacks and the visitor's events, and the anonymous profile is removed. Content creates the known profile if it doesn't exist yet.

To merge an anonymous visitor into a known profile, choose Audiences → Identity Resolution and fill in both fields of the Merge tool: the Anonymous identifier and the Known identifier. Preview shows each side as Found or New, with its aliases and traits. Merge profiles does the merge:

• The known profile gets every alias of both.
• Traits the known profile doesn't have are copied from the anonymous one. Where both have a trait, the known value stays.
• The anonymous visitor's events are attributed to the known identifier.
• The anonymous profile is removed.

Either profile is created first if it doesn't exist. Both identifiers are required and must differ. The list shows each resolved identity with its merged aliases, and the figures across the top count Resolved identities (with their share of all profiles), Pending anonymous profiles and Total profiles. Merging needs the Manage settings permission.

Traits are key and value pairs on a profile, like a plan or a lifecycle stage, that segments can match on. Choose Audiences → Traits, pick the profile from the menu, then choose Set trait:

• Key: required, like plan. It can't be changed once the trait exists.
• Value (JSON or plain text): "pro", 42, true and ["a","b"] keep their type. Anything that isn't valid JSON is stored as text.

Choose Save trait. Setting a key the profile already has replaces its value. Each trait's ⋯ menu has Edit and Delete, which asks you to confirm first; segments that match on a deleted trait stop matching. Changing traits needs the Manage settings permission.

Audiences → Calculated Attributes counts each profile's events: Page views, Total events, Conversions and when the profile was Last active. Content works them out from the events each time you open the screen, so there's nothing to edit. The figures across the top show Total events, Active profiles (with at least one event), Avg. events / profile and Conversions. Search by profile.

Audiences → Behavior Events lists every event the project has received, newest first. Each row shows the event type (Page view, Conversion, Session start, Click or Signup; other types show their own name), the actor (the user id, or the anonymous id), the first characters of the entry's id, and the time. Events can't be added, changed or deleted here.

Filter by type, which starts on All Types, and search actors, entries and types. The figures across the top count Total events, Page views, Conversions and Unique actors.

Your website or app sends events with a POST request to Content's collect endpoint, /content/api/content/v1/collect, on the domain you open Content on. The body is JSON:

• projectId: required, the project's id.
• anonymousId or userId: at least one is required, each up to 200 characters.
• type: the event type, in lowercase letters, numbers and underscores, like page_view (the default) or conversion.
• entryId: optional, the id of a published entry the event is about.
• context: optional, an object of extra details.

The endpoint accepts requests from any website. It answers { "ok": true } with the event's id when it records the event, and { "ok": true, "suppressed": true } when the visitor has denied analytics consent. Bodies over 20,000 bytes are refused.

A segment is a group of profiles defined by rules. To create one, choose Audiences → Segments, then Create segment, type a Name and choose Create segment. Then click the segment, or choose Edit rules in its ⋯ menu, to open the rule builder:

1. Pick ALL or ANY in Match … of these rules.
2. For each rule, set the Field: trait.plan or plan for a trait, or events.page_view for how many events of a type the profile has. The box suggests fields found in your data.
3. Pick the Operator: equals, not_equals, contains, not_contains, gt, gte, lt, lte, exists or not_exists.
4. Type the Value, as text or JSON. exists and not_exists don't need one.
5. Use Add rule for more rules and the × to remove one, then choose Save rules.

Member preview shows how many profiles match as you edit. A segment with no rules matches everyone. All segments goes back to the list, which shows each segment's match mode and number of rules. Delete asks you to confirm first. Changing segments needs the Manage settings permission.

Audiences → Consent State shows one profile's consent for each purpose: analytics, personalization and marketing. Pick the profile from the menu. A purpose nobody has answered shows as Pending, which counts as allowed: only Denied holds a purpose back. The figures across the top count Granted, Denied and Pending answers across every profile, and the Profiles covered.

To record a profile's consent for analytics or personalization, use Governance → Consent & Privacy, which only project owners can save. See Governance.

Audiences → Profile History shows every event of one profile, across all its aliases, newest first. Pick the profile from the menu. Each row shows the time, the event type, the first characters of the entry's id and up to three details from the event's context. The figures across the top show the profile's Events, Entries touched, Conversions and Span (days) from its first event to its last.

Audiences → Data Connections keeps a list of the outside systems that feed your audience data. To add one, choose Create connection, type a Name (required), pick a Type, which is Webhook (the default), Warehouse, CDP, CSV import or API, and choose Create connection. New connections are Active.

A connection's status is Active, Paused or Error, and you set it by hand: Pause and Activate are in its ⋯ menu, along with Delete, which asks you to confirm first. Filter by status, and search names and types. The figures across the top count Total connections, Active, Paused and Error. Only project owners can change connections.