AJO orchestrated campaign Entity is missing: inspect the identity model

The campaign designer selects an audience, but the Entity selector is empty. An Experience League question describes this blocker. Rebuilding the canvas before checking identity alignment usually wastes time: the Entity is part of the campaign's target model, not just a menu choice.

Write down the three identities

Record the audience's identity namespace, the schema and identity used by the campaign targeting dimension, and the link from that schema to Profile. Adobe's targeting-dimension guide explains that a custom dimension needs a relational schema with a direct identity relationship to Profile. The Read audience activity asks for an Entity from that campaign dimension to reconcile audience members.

Distinguish a missing option from a runtime miss

If the Entity menu is empty, validate configuration first: targetable schema, identity namespace and supported relationship path. If the menu is populated but people disappear later, inspect reconciliation and Profile availability at runtime. These are different failure stages. Adobe's orchestrated campaign guardrails require a string identity field mapped to a defined namespace for a target schema.

Test with a small, known audience

Use a few records with known entity IDs and a single relationship path. Check whether each source identity resolves to the intended target entity and Profile. Only then scale the campaign. Document the chosen namespace in the audience contract so later imports or schema changes cannot quietly break targeting.

Adovo’s view

Campaign design starts with who an entity is. A missing selector is often the first visible sign that the data model cannot answer that question. Fix the identity contract once and the canvas becomes simpler for every campaign that follows.