Download this Postman Collection for Offer Decisioning to your desktop and unzip it. You’ll then have this:
You now have this file on your desktop:
In Exercise 3.3.3 - Postman authentication to Adobe I/O you installed Postman. You’ll need to use Postman again for this exercise.
Open Postman. Click Import.
Click on Upload files.
Select the file _Module 14- Decisioning Service.postman_collection.json and click Open.
You’ll then have this collection available in Postman.
You now have everything you need in Postman to start interacting with Adobe Experience Platform through the APIs.
Click to open the request GET - List Containers.
Under Params, you’ll see this:
In that parameter, aepenablementfy21 is the name of the sandbox that is used in Adobe Experience Platform. The sandbox you should use is
--aepSandboxId--. Replace the text aepenablementfy21 by
After replacing the sandbox name, click Send.
This is the response, which shows the offer container for the sandbox that you specified. Please copy the container instanceId as indicated below and write it down in a text file on your computer. You’ll need to use this container instanceId for the next exercise!
Click to open the request GET - List Placements. Click Send.
You’re now seeing all available placements in your offer container. The placements you’re seeing were defined in the Adobe Experience Platform UI, as you could see in Exercise 14.1.3.
Click to open the request GET - List Decision Rules. Click Send.
In the response, you’ll see the Decision Rules that you defined in the Adobe Experience Platform UI, as you could see in Exercise 14.1.4.
Click to open the request GET - List Personalized Offers. Click Send.
In the response, you’ll see the Personalized Offers that you defined in the Adobe Experience Platform UI in Exercise 14.2.1.
Click to open the request GET - List Fallback Offers. Click Send.
In the response, you’ll see the Fallback Offer that you defined in the Adobe Experience Platform UI in Exercise 14.2.2.
Click to open the request GET - List Collections.
In the response, you’ll see the Collection that you defined in the Adobe Experience Platform UI in Exercise 14.2.3.
Click to open the request POST - Get Detailed Offers for Customer Profile. This request is similar to the previous one, but will actually return details like image URLs, text etc.
For this request, similar to the previous exercise which has similar requirements, you need to provide the values for xdm:placementId and xdm:activityId to retrieve the specific offer details for a customer.
The field xdm:activityId is already populated as the result of a previous request you sent, after which you stored the key OFFER_ACTIVITY_ID in your Postman environment.
The field xdm:placementId needs to be filled out. You can retrieve that in the Adobe Experience Platform UI, as indicated below. In the below example, you can see the placementId for the placement Web - Image.
Go to Body and enter the email address of the customer for whom you’d like to request an offer. Click Send.
Finally, you’ll then see the result of what kind of personalized offer and what assets need to be displayed to this customer.
In the previous exercise you used the API to retrieve information from Adobe Experience Platform and Offer Decisioning. Let’s now have a look at a practical example.
You’ve seen the Xray panel on the website before. The Xray panel is using the Adobe Experience Platform API’s to retrieve information on every payload. Let’s now add the response from the Offer Decisioning API on Xray.
In order to make this possible, you’ll need three values:
Where can you find these values?
The container instanceId was returned by the first API call you sent as part of this exercise. Scroll back up you see the List Containers step. Follow the instructions there to collect the container instanceId.
The format of the container instanceId looks like this: 02068be3-17ae-3ca6-bed6-0daf0084c5a1 and it was part of the output of the List Containers request:
The Offer Placement ID identifies the location and type of asset that is required. For instance, the hero image on the Luma website homepage corresponds with the Offer Placement ID for Web - Image.
To find the Offer Placement ID for Web - Image go to https://platform.adobe.com.
Next, go to Components and then to Placements. Click the Web - Image placement to see its details.
As you can see in the above image, in this example the Offer Placement ID is
xcore:offer-placement:129048460001fd30. Write down the Offer Placement ID for your placement for Web - Image as you’ll need it in the next exercise.
The Decision ID identifies which combination of Personalized Offers and Fallback Offer you’d like to use. In the previous exercise, you created your own Decision and named it ldap - Luma Decision.
To find the Decision ID for your ldap - Luma Decision, go to https://platform.adobe.com.
Next, go to Offers, then go to Decisions and click to select your Decision, which is named ldap - Luma Decision.
As you can see in the above image, in this example the Decision ID is
xcore:offer-activity:1290525f4441fd6e. Write down the Decision ID for your Decision ldap - Luma Decision as you’ll need it in the next exercise.
Before you can test your end-to-end demonstration, you’ll need to update your Configuration ID settings and update the fields for Offer Decisioning Container ID, Offer Decisioning Placement ID and Offer Decisioning Decision ID on the Update Configuration ID page of the demo website.
You’ll then see this:
Enter your Configuration ID and then click Load Configuration. You’ll see your Configuration ID values being loaded.
Scroll down until you see the fields Offer Decisioning Container ID, Offer Decisioning Placement ID and Offer Decisioning Decision ID.
You now need to enter the values for these three fields. You collected these values a couple of minutes ago in the previous step.
Next, on the Update Configuration ID page, scroll down and click Update Configuration ID.
After this change, the Offer Decisioning API response will be showcased on Xray!
Open a new, clean incognito browser window and go to https://public.aepdemo.net.
You’ll then see this.
Enter your Configuration ID and click Load Configuration. Your configuration is then loaded.
Scroll down and click Save Configuration.
You’ll then be redirected to the Admin homepage. Go to Select LDAP. Select your LDAP and click Save.
You’ll then be redirected to the Admin homepage. Go to Select Brand and select the brand Luma, click Save.
You’ll then be redirected to the Admin homepage. Click the Luma logo.
You’ll then see the Luma homepage. You should immediately see your hero image change, and you should see the Fallback Offer that was defined as part of your Decision, just like in the previous exercise. Additionally, when you open the Xray panel and have a look at the Offer Decisioning panel, you’ll now also see the applicable offer being displayed there.
It’s important to understand the difference:
This means that there are two ways of getting the offer in the context where it is needed, which offers you a lot of flexibility!
Go to the page Login/Register. Fill out the fields and then click CREATE ACCOUNT to create your account.
As part of the configuration of your Personalized Offers, you defined offers for either male customers or female customers. Based on the gender selection you made on the Login/Register page, you’ll now see another offer on the Luma homepage. This time it isn’t a Fallback Offer anymore, but instead a Personalized Offer. You can now again see the same offer on the hero image and on Xray.
In this example, the gender selection is male. For male customers, the highest priority offer is the offer for the Zeppelin Yoga Pant.
Thanks to the integration between Web SDK and Adobe Experience Platform, offers can be delivered in a nice and easy way, with a limited amount of configuration.
You’ve now completed this exercise.