Marketing

Understand which tools coordinate marketing, collect data, and guide visitors.

A scenario selects the integrations: Default uses PostHog; Segment uses Segment instead. Both include consent handling, interaction detection, and Widgets. Configured audience lookup uses PostHog in either scenario.

These scenarios currently include neither Google Analytics nor an advertising pixel. Widgets work independently of optional marketing consent.

Distinguish a page visit, meaningful Preferences use, and an action inside an App.

The active destination receives these signals when the applicable consent permits:

Opening Preferences alone does not qualify. Hidden-tab time does not count, and the event excludes selected preference values.

Images events can include generation settings, template, and history count. Successful-generation events include prompt text; some history actions include an image title or description.

PostHog's automatic interaction collection and session recording are disabled: this integration does not collect every click or produce session replays.

Understand how events relate to a returning browser and its supplied information.

The Homepage remembers Preferences and connects permitted events through a stable browser identifier. Recognition does not automatically extend across devices.

With Functional consent, the active destination can receive the visitor's supplied name, relationship, company association, email, email history, and selected interests, together with consent choices. Screen-size categories and a distinction between local preview and public-site traffic provide reporting context.

With Marketing consent alone, profile updates contain the browser identifier and current email when available. With Analytics alone, page views are associated with the identifier without those additional profile fields.

See what each category currently permits and how combined choices affect reporting.

Change choices in Preferences → Profile → Consent or the Consent questionConsent question. Necessary is always enabled; optional categories start off until a choice is saved.

Each optional category below is on its own; selecting several combines their permissions.

Disabling Analytics alone does not stop measurement permitted by Functional or Marketing. Detecting an interaction locally and sending it to a destination are separate steps.

Saved changes apply without reloading. Withdrawing Functional can send one final consent update. Turning categories off limits subsequent activity, without deleting data already held by a destination.

Use saved preferences and PostHog audience groups to make content relevant.

A cohort is an audience group defined in PostHog. The Homepage finds memberships for the current browser identifier, allowing editors to target content by group name. Content can also use saved interests, relationships, and other Preferences.

For example, an editor could prepare a passage for a “Frequent readers” audience. Both the audience and matching content rule must first exist.

Membership is checked at initialization and, when due, during page activity, with a one-hour refresh interval. Failed lookups retain previous groups. Refreshed groups are saved for subsequent page decisions without replacing the page currently being read.

Understand what the integration prepares for outreach and what remains to be set up.

The integration shares a current email under the applicable consent rules. Campaigns, newsletters, audience selection, permission checks, and email delivery must be configured separately; this integration sends no marketing emails itself.

Clearing an email does not erase all previously shared addresses. Marketing-only updates omit an empty address, leaving the destination's old value intact. Functional updates can clear the current address while retaining email history.

Find your audience groups and review the integration with a technical colleague.

Local previews and the public Homepage use separate provider configuration. When reports differ, check the scenario, project, consent, and event definition. Detection alone does not prove delivery.