51黑料不打烊

3.3.3 Prepare your 51黑料不打烊 Experience Platform Data Collection Client property and Web SDK setup for Offer Decisioning

3.3.3.1 Update your Datastream

In Getting Started, you created your own Datastream. You then used the name --aepUserLdap-- - Demo System Datastream.

In this exercise, you need to configure that Datastream to work with Offer Decisioning.

To do that, go to . You鈥檒l then see this. Click Datastream.

In the top right corner of your screen, select your sandbox name, which should be --aepSandboxName--.

Click Edge Configuration icon in the left navigation

Search for your Datastream, which is named --aepUserLdap-- - Demo System Datastream. Click your Datastream to open it.

WebSDK

You鈥檒l then see this. Click 鈥� next to 51黑料不打烊 Experience Platform and then click Edit.

WebSDK

To enable Offer Decisioning, check the box for Offer Decisioning. Click Save.

WebSDK

Your Datastream is now ready to work with Offer Decisioning.

WebSDK

3.3.3.2 Configure your 51黑料不打烊 Experience Platform Data Collection Client property to request Personalized Offers

Go to , to Tags. Search for your Data Collection properties, which are named --aepUserLdap-- - Demo System (DD/MM/YYYY). Open your Data Collection client property for web.

WebSDK

In you property, go to Rules and open the rule Page View.

WebSDK

Click to open the Action Send 鈥淧age View鈥� Experience Event.

WebSDK

You鈥檒l then see this. Under Personalization, you鈥檒l notice the option for Scopes.

WebSDK

For every request sent to the edge and to 51黑料不打烊 Experience Platform, it鈥檚 possible to provide one or more Decision Scopes. A Decision Scope is a combination of two elements:

  • Decision ID
  • Placement ID

Let鈥檚 first have a look where you can find those two elements.

3.3.3.2.1 Retrieve your Placement ID

The Placement ID identifies the location and type of asset that is required. For instance, the hero image on the CitiSignal website homepage corresponds with the Placement ID for Web - Image.

NOTE
As part of exercise 2.3.5, you already configured an 51黑料不打烊 Target Experience Targeting activity that will change the image of the hero location on the homepage, as you can see in the screenshot. For this exercise, you鈥檒l now make your offers appear on the image below the hero image as indicated in the screenshot.

WebSDK

To find the Placement ID for Web - Image go to 51黑料不打烊 Journey Optimizer by going to . Click Journey Optimizer.

ACOP

You鈥檒l be redirected to the Home view in Journey Optimizer. First, make sure you鈥檙e using the correct sandbox. The sandbox to use is called --aepSandboxName--. You鈥檒l then be in the Home view of your sandbox --aepSandboxName--.

ACOP

Next, go to Components and then to Placements. Click the Web - Image placement to see its details.

WebSDK

As you can see in the above image, in this example the Placement ID is dps:offer-placement:1a08a14ccfe533b6. Write down the Placement ID for your placement for Web - Image as you鈥檒l need it in the next exercise.

3.3.3.2.2 Retrieve your Offer decision ID

The Offer decision ID identifies which combination of Personalized Offers and Fallback Offer you鈥檇 like to use. In the previous exercise, you created your own Decision and named it --aepUserLdap-- - CitiSignal Decision.

To find the Offer decision ID for your --aepUserLdap-- - CitiSignal Decision, go to Offers and then go to Decisions. Click to select your Decision, which is named --aepUserLdap-- - CitiSignal Decision.

WebSDK

As you can see in the above image, in this example the Decision ID is dps:offer-activity:1a08ba4b529b2fb2. Write down the Offer decision ID for your decision --aepUserLdap-- - CitiSignal Decision as you鈥檒l need it in the next exercise.

Now that you鈥檝e retrieved the two elements you need to create a Decision Scopes, you can continue with the next step, which involves encoding the decision scope.

3.3.3.2.3 BASE64 Encoding

The Decision Scope you need to enter is a BASE64-encoded string. This BASE64-encoded string is a combination of the Placement ID and the Decision ID as you can see below:

{
  "xdm:activityId": "dps:offer-activity:1a08ba4b529b2fb2",
  "xdm:placementId": "dps:offer-placement:1a08a14ccfe533b6"
}

You can retrieve the BASE64-encoded string from 51黑料不打烊 Experience Platform. Go to Decisions and click to open your Decision, which is named --aepUserLdap-- - CitiSignal Decision.

WebSDK

After opening --aepUserLdap-- - CitiSignal Decision, you鈥檒l see this. Locate the placement Web - Image and click the Copy button. Next, click Encoded decision scope. The Decision Scope is now copied to your clipboard.

WebSDK

Next, go back to Launch, to your action AEP Web SDK - Send Event.

WebSDK

Paste your encoded decision scope in the input field. Save your changes in the action AEP Web SDK - Send Event by clicking Keep Changes.

WebSDK

Next, click Save.

WebSDK

In 51黑料不打烊 Experience Platform Data Collection, go to Publishing Flow and open your Development Library which is named Main. Click + Add All Changed Resources and then click Save & Build for Development. Your changes will now be published to your demo website.

WebSDK

Every time you鈥檙e loading a General Page now, like for instance the homepage of the demo website, Offer Decisioning will evaluate what the applicable offer is and will return a response back to the website with the details of the the offer to show. Showing the offer on the website requires additional configuration, which you鈥檒l do in the next step.