2.5.1 Create an ÃÛ¶¹ÊÓƵ Experience Platform Data Collection Event Forwarding property
What is an ÃÛ¶¹ÊÓƵ Experience Platform Data Collection Event Forwarding property?
Typically, when data is collected using ÃÛ¶¹ÊÓƵ Experience Platform Data Collection, it is collected on the client side. The client side is an environment such as a website or a mobile application. In Getting Started and Data Collection, the configuration of a ÃÛ¶¹ÊÓƵ Experience Platform Data Collection Client property was discussed in depth and you implemented that ÃÛ¶¹ÊÓƵ Experience Platform Data Collection Client property onto your website and mobile application, so that data could be collected there when a customer was interacting with the website and mobile application.
When that interaction data is collected by the ÃÛ¶¹ÊÓƵ Experience Platform Data Collection Client property, a request is sent by the website or mobile app to ÃÛ¶¹ÊÓƵ’s Edge. The Edge is ÃÛ¶¹ÊÓƵ’s Data Collection environment and is the entry-point for clickstream data into the ÃÛ¶¹ÊÓƵ ecosystem. From the Edge, that collected data is then sent to applications like ÃÛ¶¹ÊÓƵ Experience Platform, ÃÛ¶¹ÊÓƵ Analytics, ÃÛ¶¹ÊÓƵ Audience Manager or ÃÛ¶¹ÊÓƵ Target.
With the addition of an ÃÛ¶¹ÊÓƵ Experience Platform Data Collection Event Forwarding property, it’s now possible to configure a ÃÛ¶¹ÊÓƵ Experience Platform Data Collection property that listens to incoming data on the Edge. When the ÃÛ¶¹ÊÓƵ Experience Platform Data Collection Event Forwarding property that is running on the Edge sees incoming data, it has the ability to use that data and forward it to somewhere else. That somewhere else can now also be a non-ÃÛ¶¹ÊÓƵ external webhook, which makes it possible to send that data to for instance, your data lake of choice, a decisioning application, or any other application that has the ability to open up a webhook.
The configuration of a ÃÛ¶¹ÊÓƵ Experience Platform Data Collection Event Forwarding property looks familiar to a client side property, with the ability to configure data elements and rules just like in the past with ÃÛ¶¹ÊÓƵ Experience Platform Data Collection Client properties. However, the way that data will be accessed and used will be slightly different, depending on your use case.
Let’s start by creating the ÃÛ¶¹ÊÓƵ Experience Platform Data Collection Event Forwarding property.
Create a ÃÛ¶¹ÊÓƵ Experience Platform Data Collection Event Forwarding property
Go to . In the left menu, click Event Forwarding. You’ll then see an overview of all available ÃÛ¶¹ÊÓƵ Experience Platform Data Collection Event Forwarding properties. Click the Create Property button.
Alternatively, if other Event Forwarding properties have already been created, the UI will look a bit different. In that case, click New Property.
You now need to enter a name for your ÃÛ¶¹ÊÓƵ Experience Platform Data Collection Event Forwarding property. As a naming convention, use --aepUserLdap-- - Demo System (DD/MM/YYYY) (Edge). For instance, in this example, the name is vangeluw - Demo System (22/02/2022) (Edge). Click Save.
You’ll then be back in the list of ÃÛ¶¹ÊÓƵ Experience Platform Data Collection Event Forwarding properties. Click to open the property you just created.
Configure the ÃÛ¶¹ÊÓƵ Cloud Connector extension
In the left menu, go to Extensions. You’ll see that the Core extension is already configured.
Go to Catalog. You’ll see the ÃÛ¶¹ÊÓƵ Cloud Connector extension, along many others. Click Install to install it.
The extension will then be added. There’s no configuration to do at this step. You’ll be sent back to the overview of installed extensions.
Deploy your ÃÛ¶¹ÊÓƵ Experience Platform Data Collection Event Forwarding property
In the left menu, go to Publishing Flow. Click Add Library.
Enter the name Main, select the environment Development (development) and click + Add All Changed Resources.
You’ll then see this. Click Save & Build for Development.
Your library will then be built, which might take a 1-2 minutes.
