Step 10 - Add event forwarding
Event Forwarding
Event forwarding in Adobe Experience Platform allows you to send collected event data to a destination for server-side processing. Event forwarding decreases web page and app weight by using Adobe Experience Platform Edge Network to execute tasks normally done on the client. Implemented similarly to tags, event forwarding rules can transform and send data to new destinations. Still, instead of sending this data from a client application like a web browser, it is sent from Adobe’s servers.
More info:https://experienceleague.adobe.com/docs/platform-learn/data-collection/event-forwarding/overview.html The property requires standard Web SDK/Mobile SDK property, so make sure you already have one that reads data from the mobile app or web page either in dsn.com or from live customer website. If you want to create one choose e.g. Retail Basic Preset on the Quick Setup screen.
How to set it up with Demo System Next
Event Forwarding can be used with builder projects in the same way as with external websites. For both scenarios please follow these steps:
- Select Event Forwarding Preset under "Solutions".
3. Click Start in the top right corner. Provide the property name and DR number.
4. Click "Start" and wait as a result an Event Forwarding Property will be created.
What to do next?
The Event Forwarding property must be connected to a datastream to capture the flowing data a datastream that your original property is using to send data to. Open it
Click "Add Service "select "Event Forwarding". Fill in the required fields. Make sure you are selecting a property that was created in the first part of this article. As an environment choose development. Save the service.
Datastream should look like this:
How to see Event Forwarding in action
- Go to the webhook URL in a format: https://<your-ldap>-demosystem.requestcatcher.com e.g. https://zkorczyc-demosystem.requestcatcher.com/
- Browse your website - either on dsn.com from workspace or the customer website that has the Launch attached to it. Any page view event and registration actions should be visible on request-catcher and you should be able to see the XDM details.
