Personalization

A variant is one entry a content slot can show. To add one, choose Personalization → Content Variants in the sidebar, then Create variant:

• Slot: required. Slots are set up under Content → Content Slots.
• Entry: the entry the variant shows.
• Priority: 0 to start. Higher wins first.
• Weight: 1 to start. It sets the variant's share when variants tie on priority.

Choose Create variant. New variants are Active and have no targeting rules, so they match everyone until you add rules under Targeting Rules.

Each row shows the variant's entry, slot, priority and weight, and its status: Active, Paused or Archived. Filter by status and search slots and entries. The ⋯ menu has Pause or Activate, Duplicate, which makes a Paused copy, and Delete, which removes the variant straight away, without asking. Changing variants needs the Manage settings permission, which the Owner and Admin roles have.

When your app asks a content slot what to show a visitor, Content decides like this:

1. It takes the slot's Active variants whose entries are published.
2. It keeps those whose targeting rules all match the profile and context your app sent. A variant with no rules matches everyone.
3. It keeps the matches with the highest priority.
4. If several tie, it picks one in proportion to their weights. The pick is keyed to the visitor, so the same visitor gets the same variant while the tied set stays the same.
5. If nothing matches, it serves the slot's fallback entry, as long as that entry is published. Otherwise it returns no entry.

Every answer comes with a plain-language reason, such as which rules matched and why the variant won. When a visitor has denied personalization consent, Content only considers variants without rules for them and doesn't record the decision.

Targeting rules decide who a variant is for. Choose Personalization → Targeting Rules and click a variant in the list. In the Rule editor, each clause has a Key, an Operator and a Value:

• Key: the name of a value your app sends with the request, in the visitor's profile or the context, like segment, locale or device. A dotted key, like plan.tier, reads a nested value.
• Operator: equals (the default), not_equals, contains, gt or lt. equals, not_equals and contains compare text; gt and lt compare numbers.
• Value: what to compare with.

Add clause adds a row and the trash icon removes one. Choose Save rules to keep them. Clauses without a key or a value are dropped when you save. A variant matches only when all its clauses match, and a variant without clauses is a default that matches everyone.

The list shows each variant's slot and its clauses, and the figures across the top count Variants, those With rules and Defaults. Search by slot name. Changing rules needs the Manage settings permission.

Four screens show your targeting from different angles. They read the clauses on your variants and don't change anything; you edit clauses under Targeting Rules.

• Segment Targeting lists variants with a segment clause and the segment each serves. Your app passes the visitor's segment name in the request: segments built under Audiences → Segments aren't applied automatically.
• Context Targeting lists variants with locale, device, country or timezone clauses.
• Component Targeting lists every content slot with its number of variants, its highest priority and whether it's personalized. A slot without variants serves only its fallback entry.
• Behavior Targeting lists variants with stage, topic, visits, last_seen or converted clauses.

Each screen has a search box, and figures across the top that count what it lists.

Boosts and exclusions adjust recommendation rankings by hand. To add one, choose Personalization → Boosts & Exclusions, then Create rule. Pick the Entry (required) and the Rule type:

• Boost multiplies the entry's ranking score by its Weight, which is 1.5 to start.
• Exclude removes the entry from rankings.

Choose Create rule. New rules are Active. Each rule's ⋯ menu has Pause or Activate and Delete, which removes it straight away, without asking. The figures across the top count active Boosts and Exclusions and the Entries affected.

Active rules apply to the rankings in Recommendations. Changing rules needs the Manage settings permission.

Your website or app asks a content slot for its entry with a POST request to /content/api/decide, on the domain you open Content on. The body is JSON:

• projectId and slotKey: required. The slot key is the one shown on the slot, like homepage_hero.
• profile: optional facts about the visitor that rules can match, like { "segment": "pro" }. Include id or anonymousId so the same visitor gets the same pick and their consent applies.
• context: optional facts about the request, like { "locale": "de", "device": "mobile" }.

The answer is { "entryId": …, "variantId": …, "reason": "…" }, with entryId null when nothing applies. Fetch the entry itself from the delivery API; see Developer tools. Requests with a missing project or slot key get status 400, an unknown project or slot gets 404, and bodies over 20,000 bytes are refused.