Create Property

we want to forward an experience event out to usually to a third party (but doesn't have to be) this is usually used when a copy of an event is needed in real time to notify a third party under specific circumstances (e g notifying google, meta or tiktok about a purchase) reminder a property contains all the extensions, data elements and rules needed to decide what to forward and where to in the left rail click on event forwarding then click on new property 3\ update the property name using the following formula event forward property sb + \[sandbox number] your final name would look something this then event forward property sb01 4\ click save when done install extension click on the event forwarding property you just created 2\ you should see a screen like below click on extensions 3\ install the extension adobe cloud connector by doing the following click on catalog in the top nav click on the adobe cloud connector card in the right rail click on the install button after clicking install you should see the extension show under the installed extensions for your property as shown below create data element a data element references the incoming event and can parse it into multiple individual components if needed in the left rail click on data elements 2\ click on the create new data element button 3\ configure the new data element with the following information element type value to configure name data object extension core data element type custom code 4\ click on the button open editor to add the following custom code 5\ add custom code to the editor like so and save it var xdm = arc? event || ''; return xdm; this is grabbing the whole xdm object without doing any translations to the payload if needed we could parse out each individual pieces within the xdm object (e g page name, purchase amount), into one data element per field the reason for doing this might be if there is transformation of the structure to a different structure 6\ click the save button to save your data element when done you should see the following screen confirming your data element has been added create rules a rule contains conditions on what to forward actions that can transform the payload and define where to send it in the left rail click on rules 2\ then click on create new rule or add rule 3\ update the rule name using the following formula ef rule sb + \[sandbox number] your final name would look something this then ef rule sb01 5\ add an action to your rule by click on the (+) sign to add a new action get webhook url (to use in action) we are going to use a webhook here so we can see if the data has arrived at the destination we are sending to in a real world scenario, we would log into that destination instead and use their tools to see what has arrived use the same one as before if you need to get back to it open the following link in a new tab in your browser > https //webhook site/ copy the unique url you see and save it somewhere safe 3\ configure your action with the following information setting value extension adobe cloud connector action type make fetch call method post url use the same webhook url you used when setting up your streaming destination you can find it by opening a new tab in the and navigating to destinations > browse body raw body data { "data" { "event" "{{data object}}" } } the {{data object}} referenced here is the data element we created earlier here the requirement by the downstream system was it wanted to wrap the event in a data object with an event object you could put any formatting here if we had split {{data object}} into multiple fields (e g page name, purchase, etc ), we could transform the json structure placing each field in the desired spot, giving us more control over matching the destination when you are done validate your screen looks similar to below and then click on keep changes 4\ when done you should see your action added to your rule click save to continue when we forward an experience event, we are sending the event, not the profile, nor any of its attributes, including any audience qualifications (even if it is an edge audience) this happens for speed purposes publish the changes in the left rail click on publishing flow 2\ click on the button add library 3\ configure the library with the following information name > ef library environment > development click on add all changed resources when done your screen should look similar to the below screenshot if everything looks good click on the save & build to development button 4\ you should then see the development build go green stating its ready to use