Learn how to set up an Experience Platform sandbox environment with sample data. Using a Postman collection, you can create field groups, schemas, datasets and then import sample data into Experience Platform.
Experience Platform business users often have to go through a series of steps that include identifying field groups, creating schemas, preparing data, creating datasets, and then ingesting data before they can explore the marketing capabilities offered by Experience Platform. This tutorial automates some of the steps so you can get data into a Platform sandbox as quickly as possible.
This tutorial focuses on a fictional, retail brand called Luma. They invest in Adobe Experience Platform to combine loyalty, CRM, product catalog and offline purchase data into real-time customer profiles and activate these profiles to take their marketing to the next level. We have generated sample data for Luma, and in the remainder of this tutorial, you will import this data into one of your Experience Platform sandbox environments.
The end-result of this tutorial is a sandbox containing the same sample data as the Getting Started with Adobe Experience Platform for Data Architects and Data Engineers tutorial.
Before you follow the steps, please ensure that you have downloaded the Postman application. Let’s get started!
Download the platform-utils-main.zip file, which contains all files required for this tutorial.
User data contained in the platform-utils-main.zip file is fictitious and is to be used for demonstration purposes only.
From your downloads folder, move the
platform-utils-main.zip file to the desired location on your computer, and unzip it.
luma-data folder, open all of the
json files in a text editor and replace all instances of
_techmarketingdemos with your own tenant id, preceded by an underscore.
Note the location of the unzipped folder, as you need it later when setting up the
FILE_PATH Postman environment variable:
To obtain file path on your Mac, navigate to the
platform-utils-main folder, right click on the folder and select Get Info option.
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 new 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.
General tab, update the request time out in ms to
5000 ms and enable
allow reading file outside this directory
If files are loaded from within the working directory it will run smoothly across devices if the same files are stored on the other devices. However, if you wish to run files from outside the working directory, then a setting has to be turned on to state the same intent. If your
FILE_PATH is not same as the Postman’s working directory path, then this option should be enabled.
Close the Settings panel.
Select the Environments and then select Import:
Import the downloaded json environment file,
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 IDin Adobe Developer Console
Organization IDin Adobe Developer Console
TENANT_ID—be sure to lead with an underscore, for example
FILE_PATH—use the local folder path where you have unzipped the
platform-utils-main.zipfile. Be sure it includes the folder name, for example
Save the updated environment
Next you need to import the collections into Postman.
Select Collections and then choose the import option:
Import the following collections:
Authentication collection, Select the
IMS: JWT Generate + Auth via User Token POST request, and click
SEND to authenticate and obtain the access token.
Review the environment variables, and notice that the
ACCESS_TOKEN are now populated.
Now you can prepare and import the data into your Platform sandbox. The Postman collections you imported will do all of the heavy lifting!
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
1-Luma-Loyalty-Data creates a schema for customer loyalty data. The schema is based on XDM Individual Profile class, standard field group, and a custom field group and dataype. The collection creates a dataset using the schema and uploads sample customer loyalty data to Adobe Experience Platform.
If any collection requests fail during the Postman collection runner, stop the execution and run the collection requests one by one.
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.
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.jsoncreates 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.jsoncreates 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.jsoncreates 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.
The sample data has been designed so that when the collections have run, Real-time Customer Profiles are built that combine data from multiple systems. A good example of this is the first record of the loyalty, CRM, and offline purchase datasets. Look up that profile to confirm the data was ingested. In the Adobe Experience Platform interface:
Luma Loyalty Idas the Identity namespace
5625458as the Identity value
By browsing through the data in the Attributes and Events tabs, you should see that the profile contains data from the various data files:
If you would like to learn about merge policies, data governance, query service, and the segment builder, jump over to lesson 11 in the Getting Started for Data Architects and Data Engineers tutorial. The earlier lessons of this other tutorial have you manually build everything that was just populated by these Postman collections–enjoy the head start!
If you would like to build a sample Web SDK implementation to link to this sandbox, go through the
Implement Adobe Experience Cloud with Web SDK tutorial. After setting up the “Initial Configuration”, “Tags Configuration”, and “Set up Experience Platform” lessons of the Web SDK tutorial, log into the Luma website using the first ten email addresses in the
luma-crm.json file using the password
test to see the profile fragments merge with data uploaded in this tutorial.
If you would like to build a sample Mobile SDK implementation to link to this sandbox, go through the
Implement Adobe Experience Cloud in mobile apps tutorial. After setting up the “Initial configuration”, “App implementation”, and “Experience Platform” lessons of the Web SDK tutorial, log into the Luma website using the first email addresses in the
luma-crm.json file to see a profile fragment merge with data uploaded in this tutorial.
Resetting a non-production sandbox deletes all resources associated with that sandbox (schemas, datasets, and so on), while maintaining the sandbox’s name and associated permissions. This “clean” sandbox continues to be available under the same name for users that have access to it.
Follow the steps here to reset a sandbox environment.