DocumentationTutorialsUse Cases & Blueprints

Send an Edge Event

Last update: September 11, 2026

CREATED FOR:

  • Developer
  • User

Now that everything is configured, send in an event to the Edge to see it all work.

To do this, use Postman to send a Web Event to the Datastream you created.

This sends 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.

NOTE
Because you are not passing in an authenticated token, you don’t get back any attributes.

Lab expectations

  1. Experience Event to hit the Edge

  2. Datastream configuration to use Event Forwarding Service

  3. Event Forwarding to send the Event to the webhook

  4. Datastream configuration to use AEP Service

    1. Edge Audience to run
    2. Send Event to the Hub

  5. Postman Response to include Edge Audience (but no attributes)

  6. Profile Store to receive event and add an Event Profile Fragment

  7. Identity Store to add a relationship

  8. Dataset to receive data and store in Data Lake

  1. Postman Left Sidebar -> Collections
  2. Collection -> AEP Foundations Bootcamps (Labs)
  3. Folder -> Profile Lab
  4. API Request -> Create Web Event Edge (No Auth)

Postman sidebar navigation to the Create Web Event Edge (No Auth) API request in the Profile Lab folder

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

  1. In the left rail click on Datastreams (under the Data Collection heading)
  2. Select your Datastream and copy the Datastream ID value

Datastreams list with the Datastream ID value highlighted for copying

Update Postman query param

  1. In the request itself click on Params
  2. Update the Value with the datastream ID from the previous step
  3. Click the Save button to save your update

Postman Params tab with the datastream ID value pasted into the Value field

Change email to your email

Postman request body showing the email value updated to the tester's own email address

Execute the API

Execute your request by clicking the Send button.

Postman Send button being clicked to execute the Create Web Event Edge request

What you should see coming back in the response is this core thing:

  • A 200 OK response means the data was successfully sent and accepted by the Edge Network
NOTE
Any streaming and batch segments don’t show until they are evaluated at the hub first

Validate event forwarding

On webhook.site you should immediately see the same payload body you sent via your Postman request appear.

Webhook.site showing the forwarded event payload received from Event Forwarding

NOTE
Notice the payload has added the geo lookup information you asked for when you set up the datastream you used in your edge setup

Look up the profile

In Adobe Experience Platform look up the profile you just sent in from the event you just sent into the Edge Network. Navigate to Profiles -> Browse to perform the lookup using the following information:

  • Merge policy -> Default Time-based
  • Identity Namespace -> Email
  • Identity Value -> edge-email@dep.com
    • Note: change this to match the email you used in the Update Postman Query Param step above

  1. Click View to look up the profile

  2. Click on the Profile ID to open the profile

    Profile Browse search results with the View link to open the matched profile

  3. Click on Events in the top nav and you can see the event you just sent in

    Profile Events tab showing the experience event that was just sent to the Edge

  4. Validate the Profile has qualified for the Audiences by reviewing the Audience Membership tab in the top nav. You should see the following:

  • Any Event Edge (within 15 minutes)
  • dep: Any Event Streaming (within the hour)

Audience Membership tab showing qualification for Any Event Edge and dep: Any Event Streaming audiences

How to interpret the checks

  1. Check for 200 response in Postman (properly formatted payload)
  2. Check if the webhook has the event (properly configured Event Forwarding)
  3. Check if the Profile has the events (properly configured AEP Service, event received and processed event on the Hub)
  4. Check if the Profile has two identities (Identity Graph has linked on the Hub) after a few minutes
  5. Check if the Profile qualified for the audiences (properly defined audience)
  6. Check if Data Lake has the event.
recommendation-more-help
blueprints-learn-help-blueprints