A profile in AEP is not automatically an Edge personalization profile

An AEP practitioner saw a recently authenticated profile with many Hub attributes but could not see those attributes at the Edge for AJO or Target. The missing step is often the assumption that a Hub profile is copied wholesale. Adobe describes Edge profiles as lightweight and says the selected attributes must be activated for the lookup use case.

Trace the actual lookup path

Start with one test identity and one non-sensitive attribute. Confirm the intended audience and Active-on-Edge merge policy, the personalization destination connection, its attribute mapping, and the datastream service settings. Adobe's Edge lookup procedure names these prerequisites. If the destination is configured for audience membership only, do not expect arbitrary Hub attributes in the response.

Distinguish propagation from retrieval

The profile may exist in Hub while the selected Edge projection is still unavailable. Test the documented authenticated lookup for the same identity and inspect whether the returned handle contains the mapped attribute. Compare a profile that works with one that does not. A missing response can reflect identity, merge policy, activation or timing; the community thread alone does not identify the cause in a particular tenant.

Limit the data exposed

Adobe notes that Edge profile attributes can be sensitive and requires the authenticated Edge Network API interactive endpoint for this lookup. Keep the mapping to attributes the experience actually needs. Record why each field is needed, who can retrieve it and how it will be removed if the use case ends. Do not copy a full customer profile to Edge to make a demo work.

Adovo’s view

Personalization needs a named data contract, not a promise that every field follows the customer. Identity, activation and retrieval must agree on the same profile. Make that path visible before adding more attributes.