I won’t go into how Adobe’s new edge network functions, plenty is written on that elsewhere, but the short version is that you no longer send data separately to different Adobe products. Once in here, you should create a new configuration and then you’ll see a set of development, staging and production environments: Edge ConfigurationsĬlicking into one of these you’ll see switches for various Adobe products. You can find the Edge Configuration in a new drop-down in the top left of Launch. Data elements and rules will be familiar but there are a few differences with AEP. If you’ve used Launch before then the first two things will be new. Configure the new AEP Web SDK extension.Next you need to do three things in Launch: We will have other datasets in AEP in the future, but for now this is all we need for Analytics. In AEP this will be the dataset for our website data. Navigate to Datasets, create a new one and select ‘Create dataset from schema’. At least not for what we’re doing here, perhaps there is a different intended use-case for it.)įinally, there’s one last step we need to do in Experience Platform, and that is to create a Dataset from our new Schema. My understanding is that the point of the XDM schema is to send tool-agnostic data to the Edge so I wouldn’t recommend using this Mixin. However, if you try it, you’ll find that these variables aren’t automatically mapped to evars and props in Analytics. It even contains fields for evars and props, which you might think is what you should use to get your data into evars and props. (One thing worth noting is that there is a Mixin called “Adobe Analytics ExperienceEvent Template”, which contains a ton of stuff that looks very relevant to Analytics. There we go! Obviously, your schema would be much larger and better planned in a real scenario but that’ll do for now. I’ll also add a couple of custom fields by creating my own Mixin, and adding fields to the ‘webPageDetails’: Adding custom fields to the Schema This mainly seems to add clutter, but I have also found that if you make the schema too big by adding lots of Mixins, the UI does begin to slow down and struggle. The main negative I think is that they will likely contain a lot of fields that your particular implementation may never need or use. Although at this point there’s no way to know which fields are populated automatically and which are not. Secondly, as we’ll come to shortly, some of these fields are automatically populated by the Launch AEP extension (‘URL’ for example). Once that is done, you can see that these Mixins come with a lot of pre-configured fields: Creating an XDM SchemaĪs far as I can tell these Mixins have some useful benefits: Firstly, they come with a lot of standardised fields already set up for us in a consistent naming scheme. I’ll add Web Details, Environment Details and Implementation Details.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |