Import sample data to Adobe Experience Platform

Download the platform-utils-main.zip file, which contains all files required for this tutorial.

From your downloads folder, move the platform-utils-main.zip file to the desired location on your computer, and unzip it.

In the luma-data folder, open all the json files in a text editor and replace all instances of _yourTenantId with your own tenant id, preceded by an underscore.

Open luma-offline-purchases.json, luma-inventory-events.json, and luma-web-events.json in a text editor and update all the timestamps so that the events occur in the last month (for example, search for "timestamp":"2022-11 and replace the year and month)

Note the location of the unzipped folder, as you need it later when setting up the FILE_PATH Postman environment variable:

note note
NOTE
To obtain file path on your Mac, navigate to the platform-utils-main folder, right-click on the folder and select Get Info option.

note note
NOTE
To obtain file path on your windows, click to open the location of the desired folder, and then right-click to the right of the path in the address bar. Copy address to obtain the file path.

Open Postman and create a workspace from the Workspaces dropdown menu:

Enter a Name and optional Summary for your workspace and click Create Workspace. Postman will switch to your new workspace when you create it.

Now adjust some settings to run the Postman collections in this workspace. In the header of Postman, click the gear icon and select Settings to open the settings modal. You can also use the keyboard shortcut (CMD/CTRL + ,) to open the modal.

Under the General tab, update the request time out in ms to 5000 ms and enable allow reading file outside this directory

Close the Settings panel.

Select the Environments and then select Import:

Import the downloaded json environment file, DataInExperiencePlatform.postman_environment

In Postman, select your environment in the top-right dropdown and click the eye icon to view the environment variables:

Make sure that the following environment variables are populated. To learn how to obtain the environment variables’ value, check out the Authenticate to Experience Platform APIs tutorial for step-by-step instructions.

• CLIENT_SECRET
• API_KEY—Client ID in Adobe Developer Console
• SCOPES
• TECHNICAL_ACCOUNT_ID
• IMS
• IMS_ORG—Organization ID in Adobe Developer Console
• SANDBOX_NAME
• TENANT_ID—be sure to lead with an underscore, for example _techmarketingdemos
• CONTAINER_ID
• platform_end_point
• FILE_PATH—use the local folder path where you have unzipped the platform-utils-main.zip file. Be sure it includes the folder name, for example /Users/dwright/Desktop/platform-utils-main

Save the updated environment

Select Collections and then choose the import option:

Import the following collections:

• 0-Authentication.postman_collection.json
• 1-Luma-Loyalty-Data.postman_collection.json
• 2-Luma-CRM-Data.postman_collection.json
• 3-Luma-Product-Catalog.postman_collection.json
• 4-Luma-Offline-Purchase-Events.postman_collection.json
• 5-Luma-Product-Inventory-Events.postman_collection.json
• 6-Luma-Test-Profiles.postman_collection.json
• 7-Luma-Web-Events.postman_collection.json

Open the 0-Authentication collection, Select the OAuth: Request Access Token request, and click SEND to authenticate and obtain the access token.

Review the environment variables, and notice that the ACCESS_TOKEN is now populated.

Open the 1-Luma-Loyalty-Data collection and click Run on the overview tab to start a Collection Runner.

In the collection runner window, make sure to select the environment from the dropdown, update the Delay to 4000ms, check the Save responses option, and make sure that the run order is correct. Click the Run Luma Loyalty Data button

If everything goes well, all requests in the Luma-Loyalty-Data collection should pass.

Now let’s login to Adobe Experience Platform interface and navigate to datasets.

Open the Luma Loyalty Dataset dataset, and under the dataset activity window, you can view a successful batch run that ingested 1000 records. You can also click on the preview dataset option to verify the records ingested. You might need to wait several minutes to confirm that 1000 New Profile Fragments were created.

Repeat steps 1-3 to run the other collections:

• 2-Luma-CRM-Data.postman_collection.json creates a schema and populated dataset for CRM data of customers. The schema is based on XDM Individual Profile class that comprises Demographic Details, Personal Contact Details, Preference Details and a custom identity field group.
• 3-Luma-Product-Catalog.postman_collection.json creates a schema and populated dataset for product catalog information. The schema is based on a custom product catalog class and uses a custom product catalog field group.
• 4-Luma-Offline-Purchase-Events.postman_collection.json creates a schema and populated dataset for offline purchase event data of customers. The schema is based on XDM ExperienceEvent class and comprises a custom identity and Commerce Details field groups.
• 5-Luma-Product-Inventory-Events.postman_collection.json creates a schema and populated dataset for events related to products going in and out of stock. The schema is based on a custom business event class and a custom field group.
• 6-Luma-Test-Profiles.postman_collection.json creates a schema and populated dataset with test profiles to use in Adobe Journey Optimizer
• 7-Luma-Web-Events.postman_collection.json creates a schema and populated dataset with simple historical web data.