Adobe Analytics with Datastreams

Overview

The newly developed “alloy.js” library from Adobe is a JavaScript library that helps merchants measure how users interact with their website.

The new approach of the current “alloy.js” is that it improves:

• Page performance by loading a smaller tracking library.
• Use the same visitor identifier across different solutions from Adobe platform.
• On client-side data, it minimizes the transmissions from website to Adobe platform.

Implementing Adobe Analytics using the Adobe Experience Platform Web SDK (alloy.js) probably will charge fees, so be in touch with your Adobe provider. For more information on the Adobe Experience Platform Web SDK and how to install it, click here.

Setting the Adobe Analytics configuration

To implement Adobe Analytics on your website, follow these steps: 

1. Log into your 2Checkout (now Verifone) Merchant Control Panel and navigate to Setup.
2. Select Ordering Options.
3. Click on the Analytics tab.
4. Click on the Convert Plus & Inline Checkout button.
5. In the Adobe Analytics panel click on Setup.
   
   
6. Fill in the two fields. The information can be extracted from the datastream creation in the Adobe platform.
   
   
   
   The Adobe Analytics Edge Configuration ID and Experience Cloud Organization ID can be found in Adobe Experience Platform.
   • The Edge Configuration ID means Datastream ID and represents the ID of the configuration that is set on the datastream created for transferring data to the Adobe Analytics module.
   • The Organization ID means the ID that Adobe is creating for a user and helps the Adobe Platform to recognize the user between the changes from different module/applications.

   

7. Click on the Inactive button to activate the configuration credentials for Adobe Analytics.
   
   

Setting the Adobe Experience Platform for using Adobe Analytics

To implement a report in Adobe Analytics from the data sent in the shopping cart, first you need to create a datastream and a schema to set the logic data into the datastream.

1. Go to Adobe Experience Platform and click on the Schemas option from the left side panel. Then, click on the Create schema button. This schema should use the XDM Adobe pre-build schemas in order for the data to be recognized in the Adobe Analytics report.
   
   The XDM ExperienceEvent is used as the primary selection for the Adobe pre-build class because this is the way that Adobe Analytics service can recognize the schema in the datastream.
   
   
2. In the new schema, go to Scheme properties and enter the Display name and Description. In the left-side panel, go to the Fields group and click on Add; this will open the pre-built schema for Adobe Analytics to be selected.
   
      This step is very important as here we get the data that will be mapped in the datastream with the data sent from the shopping cart.

   

3. After saving the schema, go back to the Datastreams section, and create a New Datastream, selecting the already created schema from the Event schema drop-down option.
   
   

The steps on how to map the data will be treated in the section Mapping the data to Adobe Analytic context.

All of these 3 steps can be reproduced in the Adobe Experience Platform Data Collection module from the same Adobe Experience Cloud environment.

Mapping the data to Adobe Analytics context

For mapping the correct data into Adobe Analytics module, the 2Checkout comes with the schema that is sent from the shopping cart. For mapping the data, you need to know two aspects, one of the data that is sent from 2Checkout, and secondly, the data recognized (or created as new evar/events) in the Adobe Experience Platform.

Data sent from 2Checkout

A general overview of this data is presented in the code snippet below:

{
  "event": "checkout",
  "ecommerce": {
    "currencyCode": "string required",
    "sessionId": "string required",
    "checkout": {
      "actionField": {"<< ActionField object >>"},
      "products": ["<< List of product object >>"]
    },
    "purchase": {
      "actionField": {"<< ActionField object >>"}
    },
    "products": ["<< List of product object >>"],
    "add": {
      "products": ["<< List of product object >>"]
    },
    "remove": {
      "products": ["<< List of product object >>"]
    },
    "impressions": ["<< List of impression object >>"]
  },
  "PAGE_NAME": "string => string",
  "VENDOR_CODE": "string => string",
  "ONESTEPCART": "true => bool",
  "SHORT_FORM": "true => bool",
  "PURCHASE_COMPLETE": "bool",
  "TEST_ORDER": "bool => bool",
  "PRODUCT_SOURCE": "string",
  "CART_LOCK": "bool => bool",
  "DISCOUNT_COUPON_STATUS": "string",
  "AUTO_RENEWAL": "string => string",
  "PURCHASE_TYPE": "string => string",
  "LANGUAGE": "string => string",
  "BILLING_COUNTRY": "string",
  "VISITOR_COUNTRY": "string",
  "BILLING_CURRENCY": "string",
  "COMPANY_NAME": "string",
  "ORDER_EXT_REF": "string",
  "CUSTOMER_EXT_REF": "string",
  "TEMPLATE_LAST_MODIFIED_DATE": "string",
  "TEMPLATE_CREATION_DATE": "string",
  "PAGE_STYLE_NAME": "string",
  "ADDITIONAL_HIDDEN_FIELDS": "array",
  "SELLER_TYPE": "string",
  "PAYMENT_METHOD": "string",
  "PAYMENT_METHOD_TYPE": "string",
  "QUANTITY_CHANGED": "string",
  "CART_STEP": "string",
  "ADDITIONAL_FIELDS_COUNT": "number",
  "SOURCE": "string",
  "PURCHASE_FLOW": "string",
  "CREDIT_CARD_INSTALLMENTS": "string",
  "LEAD_MANAGEMENT": "string",
  "PAYMENT_CATEGORY": "string",
  "time": "number"
}

In the next tables, each event is described in detail:

Data needed from Adobe Experience Platform

Go back to the new created datastream from Adobe Platfom, and click on the Edit Mapping section.

Here is an example of a partial mapped scheme:

How to create Events and Variables in the Adobe Analytics application

1. Log into Adobe Analytics.
2. Go to Admin > Report Suites.
   
   
3. Click on the Report suites for which you want to build variables or events.
   
   

Example on how to build a custom event in Adobe Analytics:

• Click on Edit Settings > Conversion > Success Events to build custom events.
  
  
• Click on Add New and then define the new event, for example event10: write a name for the event (ex: “Product Discount Value”).
• Under the Type column, select Currency if a monetary value is sent under this event, as in the example below. The other fields should be left as preselected by Adobe in this example.
  
  
• Click the Save button at the bottom of the page.
  
  
• After the event was created, it will appear in Adobe Analytics Workspaces, if you search for “event10” in the left-side panel.
  
  

Example on how to build a custom variable in Adobe Analytics

A. Session level variable – example evar8 Order ID (order ID/ purchase ID is not captured automatically by Adobe; if we want to capture this value, then it needs to be captured under a custom evar)

• Click on Edit Settings > Conversion > Conversion Variables to build custom variables.
  
  
• Click on Add New and define the new variable, for example evar8, add as name Order ID. Select Linear as allocation for order ID.
  
  
• Click Save at the bottom of the page.
• After the evar was created, it will appear in Adobe Analytics Workspaces, if you search for evar8 in the left-side panel.
  
  

B. Merchandising variable (this is a product level variable) – example evar26 Product Discount Coupon Value

• Click Add New and define the new variable with Product Name “Product Discount Coupon Value”
• Click Enable merchandising (this is only applicable for merchandising evars – evars that send information specific for certain products, e.g., certain products in an order can have different coupon discounts).
• For Merchandising click Product Syntax from the drop-down list and Allocation Most Recent (Last).
  
  
• Click Save at the bottom of the page.
• After the evar was created, it will appear in Adobe Analytics Workspaces, if you search for evar26 in the left-side panel.