Preview features reference a set of profiles stored in the ProfileAdapterRepository on the asset management server. The profiles let you simulate the experience of various users. Preview profiles reside in a preview profile repository, which you first define, then populate.
Defining the Repository
Preview profiles should have the same properties as external profiles in your system, so you can accurately simulate the experience of external users. For example, if you extend the default profile definition so external user profiles have an income property, and you create a targeter that displays different content according to that property’s value, the same property must exist in the preview profile. To achieve this, make sure that the preview profile repository uses the same userProfile.xml definition file as the external profile repository.
Populating the Repository
After you define the profile repository, you populate it by creating profiles like other user profiles (see Creating Profiles in the next chapter). For more information on profile repositories, refer to the ATG Personalization Programming Guide.
