In this exercise, you’ll create a custom Event by making use of Journey Orchestration in combination with Adobe Experience Platform.
You’ll see the Adobe Experience Cloud homepage.
Click on Journey Orchestration.
Next, you’ll see the Journey Orchestration homepage.
In the menu, click on Events.
You’ll then see the Events list.
Click Add to start adding your event.
You’ll see an empty event popup.
As a Name for the Event, use
geofenceEntryLdap and replace
Ldap with your LDAP. In this example, the Event Name is
Set Description to:
Geofence Entry Event.
Next is the Event ID Type selection. Select System Generated.
Next, you need to select a Schema. All Schemas that are shown here, are Adobe Experience Platform Schemas.
You’ll notice that not all Schemas are shown. There are many more Schemas available in Adobe Experience Platform.
To show up in this list, a Schema needs to have a very specific Mixin linked to it. The Mixin that is needed to show up here is called
Let’s have a quick look how these Schemas are defined in Adobe Experience Platform.
Log in to Adobe Experience Platform by going to this URL: https://experience.adobe.com/platform
After logging in, you’ll land on the homepage of Adobe Experience Platform.
In the left menu, go to Schemas.
In Schemas, go to Browse to see the list of available Schemas.
Open the Schema
AEP Demo - Location Service Geofence Schema.
After opening the Schema, you’ll see that the Mixin
Orchestration eventID is part of the Schema.
This Mixin only has one field,
Once this Mixin and this specific field are part of a Schema, that Schema will be available for usage by Journey Orchestration.
Go back to your Event configuration in Journey Orchestration.
In this use-case, you want to listen to a Geofence Event to understand if a customer is in a specific location, so now, select the Schema
AEP Demo - Location Service Geofence Schema v.1 as the Schema for your Event.
Journey Orchestration will then automatically select some required fields, but you can edit the fields that are made available to Journey Orchestration.
Click the pencil icon to edit the fields.
You’ll then see a popup-window with a Schema Hierarchy that allows you to select fields.
Fields like the ECID and the Orchestration eventID are required and as such preselected.
However, a marketeer needs to have flexible access to all data points that provide context to a Journey. So let’s make sure to select the following fields as a minimum as well:
Once that’s done, click OK.
Journey Orchestration also needs an Identifier to identify the customer. Since Journey Orchestration is linked to Adobe Experience Platform, the Primary Identifier of a Schema is automatically taken as the Identifier for the Journey.
The Primary Identifier will also automatically take into account the full Identity Graph of Adobe Experience Platform and will link all behavior across all available identities, devices and channels to the same profile, so that Journey Orchestration is contextual, relevant and consistent.
Click Save to save your custom event.
Your event will then be part of the list of available events.
Finally, you need to recover the
Orchestration eventID for your custom event.
Open your event again by clicking it in the list of events.
On your Event, click on the View Payload icon next to Fields.
Clicking the View Payload icon opens up a sample XDM payload for this event.
Scroll down in the Payload until you see the line
Write down the
eventID as you’ll need it in the last to test your configuration.
In this example, the
You’ve now defined the event that will trigger the Journey we’re building. Once the Journey is triggered, the geofence-fields like City, Country, Name, Latitude and Longitude will be made available to the Journey.
As discussed in the use-case description, we then need to provide contextual promotions that depend on the weather. In order to get weather information, we’ll need to define an external data sources that will provide us with the weather information for that location. We’ll use the OpenWeather service to provide us what that information, as part of 2.
Next Step: 12.2 Define an External Data Source