Web Event to Edge

now we can send in an event to the edge to see it all work to do this we will use postman to send a web event to the datastream we created this will send in an event with no oauth token to simulate a page view coming in from the web to the edge ensure you have postman open on your machine to perform this lab because we are not passing in an authenticated token, we will not get back any attributes lab expectations experience event to hit the edge datastream configuration to use event forwarding service event forwarding to send the event to the webhook datastream configuration to use aep service edge audience to run send event to the hub postman response to include edge audience (but no attributes) profile store to receive event and add an event profile fragment identity store to add a relationship dataset to receive data and store in data lake navigate to the call postman left sidebar > collections collection > adobe summit l614 folder > profile lab api request > create web event edge (no auth) modify api request before you can execute the api request you need to add some additional pieces of information to the request start by gathering the following values gather the datastream id in the left rail click on datastreams (under the data collection heading) select your datastream and copy the datastream id value update postman query param in the request itself click on params update the value with the datastream id from the previous step click the save button to save your update change the email in body of the call to use " mailto\ depeche mode\@dep com " and hit send this be used later if you finish your lab early then change the email to your email execute the api execute your request by clicking the send button your response should look something like this, but it might be slightly different depending on how you named things what you should see coming back in the response are these core things a 200 ok response means the data was successfully sent and accepted by the edge network in the payload response you should also see the following the destinationid of the custom personalization destination you setup the alias name of that destination (yours was called edgealias) any of the audiences the profile qualified for that exist on the edge errors you might encounter below is an example of an error you may encounter this means the edge segmentation service processed the payload sent to the edge, but it timed out when responding to the calling application "errors" \[ { "type" "https //ns adobe com/aep/errors/exeg 0203 502", "status" 502, "title" "the service call has failed ", "detail" "an error occurred while calling the 'com adobe experience platform edge segmentation' service for this request try again ", "report" { "eventindex" 0 } } ] any streaming and batch audiences will not show until they are evaluated at the hub first if you were sending to server adobedc net using a bearer token you would also see the attribute you configured in the custom personalization destination try yourself if you finish early validate the profile go back to aep l ookup your profile to see that the event was ingested onto profile it should appear in seconds ( https //www dep labs com/adobesummit/how to lookup the profile ) use the email in your call to lookup the profile merge policy default time based namespace email value \[ mailto\ depeche mode\@dep com e g if your email is depeche mode\@dep com then you would put depeche mode\@dep in the value note we sent in two events with different emails, one was yours you changed this in the update postman query param step above the webhook should now have received a different payload that has the event that was sent to the edge notice the payload has added the geo lookup information you asked for when you setup the datastream you used in your edge setup how to interpret the checks you have done check for 200 response in postman (properly formatted payload) check if the webhook has the event (properly configured event forwarding) check if the profile has the events (properly configured aep service, event received and processed event on the hub) check if the profile has two identities (identity graph has linked on the hub) check if the profile qualified for the audiences (properly defined audience)