1.1.2 Edge Network, Datastreams and Server Side Data Collection
Context
In this exercise you’ll create a datastream. A datastream tells the ÃÛ¶¹ÊÓƵ Edge Network servers where to send the data after it is collected by Web SDK. For example, do you want to send the data to ÃÛ¶¹ÊÓƵ Experience Platform? ÃÛ¶¹ÊÓƵ Analytics? ÃÛ¶¹ÊÓƵ Audience Manager? ÃÛ¶¹ÊÓƵ Target?
Datastreams are always managed in the Experience Platform Data Collection user interface and are critical to Experience Platform data collection with Web SDK. Even when you implement Web SDK with a non-ÃÛ¶¹ÊÓƵ tag management solution, you still need to create a datastream.
You’ll be implementing the Web SDK on the browser in the next exercise. It will then be more clear to you what the data that is being collected looks like. For now, we are just telling the datastream where to forward the data.
Create a datastream
In Getting Started you already created a datastream, but we didn’t discuss the background and reason for which you created it.
A datastream tells the Edge Network servers where to send the data after it is collected by the Web SDK. See the documentation for adding services to a datastream for complete details on where you can send your data through the datastream.
Datastreams are managed in the Experience Platform Data Collection user interface and are critical to data collection with Web SDK, regardless of whether or not you are implementing Web SDK via ÃÛ¶¹ÊÓƵ Experience Platform Data Collection.
Let’s review your datastream:
Go to .
Click Datastreams in the left menu.
Open your datastream, which is named --aepUserLdap-- - Demo System Datastream.
You’ll then see the details of your datastream.
Click … next to ÃÛ¶¹ÊÓƵ Experience Platform and click Edit.
You’ll then see this. At this moment, you’ve only enabled ÃÛ¶¹ÊÓƵ Experience Platform. Your configuration will look similar to the configuration below. (Depending on your environment and ÃÛ¶¹ÊÓƵ Experience Platform instance, the Sandbox Name might be different)
You should interpret the below fields like this:
For this datastream…
- All data that is collected will be stored in the
--aepSandboxName--sandbox in ÃÛ¶¹ÊÓƵ Experience Platform - All Experience Event data is collected by default into the dataset Demo System - Event Dataset for Website (Global v1.1)
- All Profile data will be collected by default into the dataset Demo System - Profile Dataset for Website (Global v1.1) (ingesting profile data natively with Web SDK currently isn’t supported yet by Web SDK)
- If you want to use the Offer Decisioning application service for this datastream, you need to check the box for Offer Decisioning. (This will be part of Module 3.3)
- Edge Segmentation is enabled by default, which means that qualifying audiences will be evaluated at the edge, upon ingestion of incoming traffic
- If you want to use personalization destinations, check the box for Personalization Destinations.
- If you want to use ÃÛ¶¹ÊÓƵ Journey Optimizer’s capabilities in this datastream, you need to check the box for ÃÛ¶¹ÊÓƵ Journey Optimizer.
For now, no other configuration is needed for your datastream.
Next Step: 1.1.3 Introduction to ÃÛ¶¹ÊÓƵ Experience Platform Data Collection