# Marketing

_How my Homepage understands its visitors and makes their experience more relevant._

MTAM, the MarTech Agents Manager, connects visitor profiles, selected interactions, and audience groups across the Homepage's marketing tools.

## Integrated tools [v]

_Understand which tools coordinate marketing, collect data, and guide visitors._

| Tool | Role in the Homepage |
| --- | --- |
| MTAM | Coordinates the tools and consent rules for sending browser events. Its “agents” are small integrations for individual tools. |
| PostHog | The default destination for visitor profiles, page views, and selected actions. It also supplies audience groups for personalization. |
| Segment | An alternative destination for profiles and events, selected through the Segment scenario. |
| CXWidgets | Provides contextual help, such as the tooltip explaining the OpenAI key. See [Widgets](https://homepage.sefzig-net.workers.dev/docs/widgets) for examples. |

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.

## Measurement [v]

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

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

| Signal | What it means |
| --- | --- |
| Page view | A visited page or changed address, reported with its title and address. PostHog names this event `$pageview`. |
| `Use Preferences` | Someone opened Preferences through the Homepage logo, interacted with a control, and kept the panel visible for at least three seconds. It fires at most once per qualifying opening. |
| `Images` | Activity inside the embedded Images App. An accompanying action distinguishes requesting or generating an image, using templates, downloading, and other interactions. |

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.

## Visitor profiles [v]

_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.

## Consent [v]

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

Change choices in **Preferences → Profile → Consent** or the [Consent question](https://homepage.sefzig-net.workers.dev/questions#consent). 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.

| Category | Profile information | Page views | Selected actions |
| --- | --- | --- | --- |
| Necessary only | None sent through browser events | No | No |
| Analytics | Identifier only | Yes | No |
| Functional | Available profile and consent | Yes | Yes |
| Marketing | Identifier; current email if supplied | No | Yes |

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.

## Audiences and personalization [v]

_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.

> [Info]
> Audience lookup currently runs separately from browser-event consent: turning off optional categories does not prevent a configured PostHog cohort lookup. Personalization follows the content's authored rules; Functional is not a universal personalization switch. A consent-dependent passage needs an explicit consent rule.

## Email marketing [v]

_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.

## Explore the integration [v]

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

1. Open Preferences using the Homepage logo.
2. Choose **APIs → MTAM → Show your cohorts** to inspect your audience groups. An empty list means no groups are currently available for this browser.
3. For an integration review, use the development walkthrough in the [MTAM article](https://homepage.sefzig-net.workers.dev/blog/mtam). Development mode reveals diagnostics and the Default/Segment scenario selector in Preferences.

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.