Set up a schema and dataset

To ingest data into Adobe Experience Platform, you first must define which data you want to collect. All data ingested into Adobe Experience Platform must conform to a standard, denormalized structure for it be recognized and acted upon by downstream capabilities and features. Experience Data Model (XDM) is the standard framework that provides a structure in the form of schemas.

Once you have defined a schema, you use one or more datasets to store and manage the collection of data. A dataset is a storage and management construct for a collection of data (typically a table) that contains a schema (columns) and fields (rows).

All data that is ingested into Adobe Experience Platform must conform to a pre-defined schema before it can be persisted as a dataset.

Set up a schema

You want to track some minimal data from profiles playing your game on a console, for example identification, scores, progress, and other information.
You first must define a schema that models this data.

To set up your schema:

  1. In the Adobe Experience Platform UI, in the left rail, select Schemas within DATA MANAGEMENT.

  2. Select Create schema.
    .

  3. In the Select a class step of the Create schema wizard:

    1. Select Experience Event.

      Create a schema

      INFO
      An Experience Event schema is used to model the behavior of a profile (like scene name, push button to add to cart). An Individual Profile schema is used to model the profile attributes (like name, email, gender).
    2. Select Next.

  4. In the Name and review step of the Create schema wizard:

    1. Enter a Schema display name for your schema and (optional) a Description.

      Name your schema

    2. Select Finish.

  5. In the Structure tab of Example Schema:

    1. Select + Add in Field groups.

      Add field group

      Field groups are reusable collections of objects and attributes that allow you to easily extend your schema.

    2. In the Add fields groups dialog, select the Blinding Light field group from the list. This fieldgroup is created to track user progress playing a fictitious game titled Blinding Light on a console.

      Blinding Light fieldgroup

      You can select the preview button, to see a preview of the fields that are part of this field group, like scores > afterMatch.

      Blinding Light fieldgroup preview

      Select Back to close the preview.

    3. Select Add field groups.

  6. Select + next to your schema name.

    Example Schema Add Field button

  7. In the Field Properties panel, enter identification as the Field name, Identification as the Display name, select Object as the Type and select ExperienceEvent Core v2.1 as the Field Group.

    NOTE
    If that field group is not available, look for another field group containing identity fields. Or create a new field group and add new identity fields (like ecid, crmId, and others you need) to the field group and select that new field group.

    Identification Object

    The identification object adds identification capabilities to your schema. In your case, you want to identify profiles playing your game using the Experience Cloud Id and email address they use to log in to their gaming console. There are many other attributes available to track your person’s identification.

    Select Apply to add this object to your schema.

  8. Select the ecid field in the identification object you just added, and select Identity and Primary Identity and ECID from the Identity namespace list in the right panel.

    Specifiy ECID as identity

    You are specifying the Experience Cloud Identity as the primary identity the Adobe Experience Platform Identity service can use to combine (stitch) the behavior of profiles with the same ECID.

    Select Apply. You see that a fingerprint icon appears in the ecid attribute.

  9. Select the email field in the identification object you just added, and select Identity and Email from the Identity namespace list in the Field Properties panel.

    Specifiy email as identity

    You are specifying the email address as another identity the Adobe Experience Platform Identity service can use to combine (stitch) the behavior of profiles.

    Select Apply. You see that a fingerprint icon appears in the email attribute.

    Select Save.

  10. Select the root element of your schema displaying the name of the schema, then select the Profile switch.

    You are prompted to enable the schema for profile. Once enabled, when data is ingested into datasets based on this schema, that data is merged into the Real-Time Customer Profile.

    See Enable the schema for use in Real-Time Customer Profile for more information.

    IMPORTANT
    Once you save a schema enabled for profile, it can no longer be disabled for profile.

    Enable schema for profile

  11. Select Save to save your schema.

You have created a minimal schema that models the data you can capture from your game. The schema allows profiles to be identified using the Experience Cloud Identity and email address. By enabling the schema for profile, you ensure data captured from your console game is added to the Real-Time Customer Profile.

Next to behavior data, you can also capture profile attribute data from your console (for example details of profiles signed into the console).

To capture profile data, you would:

  • Create a schema based on the XDM Individual Profile class.

  • Add the Profile Core v2 field group to the schema.

  • Add an identification object based on the Profile Core v2 field group.

  • Define Experience Cloud ID as primary identifier and email as identifier.

  • Enable the schema for profile

See Create and edit schemas in the UI for more information on adding and removing field groups and individual fields to a schema.

Set up a dataset

With your schema, you have defined your data model. You now have to define the construct to store and manage that data by using datasets.

To set up your dataset:

  1. In the Adobe Experience Platform UI, in the left rail, select Datasets within DATA MANAGEMENT.

  2. Select Create dataset.

    Create dataset

  3. Select Create dataset from schema.

    Create dataset from schema

  4. Select the schema that you created earlier and select Next.

  5. Name your dataset and (optional) provide a description.

    Name dataset

  6. Select Finish.

  7. Select the Profile switch.

    You are prompted to enable the dataset for profile. Once enabled, the dataset enriches real-time customer profiles with its ingested data.

    IMPORTANT
    You can only enable a dataset for profile when the schema, to which the dataset adheres, is also enabled for profile.

    Enable schema for profile

See Datasets UI guide for much more information on how to view, preview, create, delete a dataset. And how to enable a dataset for Real-Time Customer Profile.

Set up a datastream

A datastream represents the server-side configuration when implementing the Adobe Experience Platform Web and Mobile SDKs and the Adobe Experience Platform Edge Network Server API. When collecting data with the Adobe Experience Platform SDKs and Edge Network Server APIs, data is sent to the Adobe Experience Platform Edge Network. It is the datastream that determines to which services that data is forwarded.

In your setup, you want the data you collect from the game to be sent to your dataset in Adobe Experience Platform.

To set up your datastream:

  1. In the Adobe Experience Platform UI, select Datastreams from DATA COLLECTION in the left rail.

  2. Select New Datastream.

  3. Name and describe your datastream. Select your schema from the Event Schema list.

    New Datastream

  4. Select Save.

  5. Select Add Service.

  6. In the Add Service screen:

    1. Select Adobe Experience Platform from the Service list.

    2. Ensure Enabled is selected.

    3. Select your dataset from the Event Dataset list.

      Datastream AEP service

    4. Leave the other settings and select Save to save the datastream.

Your datastream is now configured to forward the data collected from your game to your dataset in Adobe Experience Platform.

See Datastreams overview for more information on how to configure a datastream and how to handle sensitive data.