Analytics Lab / Instrumentation

Adobe Analytics sandbox

AppMeasurement sends two kinds of server calls. s.t() records a page view. s.tl() records a link or custom interaction without counting a page view. Use the controls below to see the call each interaction makes. The console shows a simulated beacon; nothing is sent.

Report suite: jwiedeman.sandbox
Endpoint: https://metrics-demo.sc.omtrdc.net/b/ss/.../s

linkName: cta:request-demo · linkType: o

Custom link: demo request

A button click tracked with s.tl() and link type o (custom link). linkTrackVars and linkTrackEvents list the variables and events the call may send. Anything not listed is dropped.

events: event5
prop4: cta:request-demo
eVar4: Request a demo
contextData: component=pricing-page · priority=primary

s.tl(this, 'o', 'cta:request-demo', {
  linkTrackVars: 'events,prop4,eVar4,contextData.component,contextData.priority',
  linkTrackEvents: 'event5',
  events: 'event5',
  prop4: 'cta:request-demo',
  eVar4: 'Request a demo',
  contextData: { component: 'pricing-page', priority: 'primary' }
});

linkName: download:pricing-pdf · linkType: d

Download link: pricing PDF

Link type d reports the click as a file download. Type e is used for exit links. AppMeasurement can track both automatically with trackDownloadLinks and trackExternalLinks; the explicit call below adds custom variables.

events: event8
prop6: download:pricing-pdf
eVar6: Pricing PDF
contextData: component=pricing-page · file=pricing.pdf

Download pricing PDF

s.tl(this, 'd', 'download:pricing-pdf', {
  linkTrackVars: 'events,prop6,eVar6,contextData.component,contextData.file',
  linkTrackEvents: 'event8',
  events: 'event8',
  prop6: 'download:pricing-pdf',
  eVar6: 'Pricing PDF',
  contextData: { component: 'pricing-page', file: 'pricing.pdf' }
});

linkName: form:newsletter-signup · linkType: o

Custom link: newsletter sign-up

A form submission tracked as a custom link. The selected topic is sent in eVar9. Submission is blocked in this demo so you can read the payload.

events: event12
prop9: form:newsletter
eVar9: Newsletter topic (form value)
contextData: component=newsletter · submission=form

s.tl(this, 'o', 'form:newsletter-signup', {
  linkTrackVars: 'events,prop9,eVar9,contextData.component,contextData.submission',
  linkTrackEvents: 'event12',
  events: 'event12',
  prop9: 'form:newsletter',
  eVar9: topic, // e.g. 'product-updates'
  contextData: { component: 'newsletter', submission: 'form' }
});

linkName: cart:add · linkType: o

Commerce: add to cart

Commerce events use the reserved names prodView, scOpen, scAdd, scRemove, scCheckout and purchase. s.products is a comma-separated list of products in the form category;product;quantity;price;events;eVars. Quantity and price are only counted on purchase.

events: scAdd
products: Plans;pro-annual

s.tl(this, 'o', 'cart:add', {
  linkTrackVars: 'events,products',
  linkTrackEvents: 'scAdd',
  events: 'scAdd',
  products: 'Plans;pro-annual'
});

// On the order confirmation page (s.t()):
s.events = 'purchase';
s.purchaseID = 'ORD-10042';
s.products = 'Plans;pro-annual;1;199.00';

Page view variables

The s.t() call on page load sends every variable that is set on the s object. Props hold values for the current hit only. eVars persist according to their expiration setting, so later conversions can be credited to them.

pageName = lab:analytics:adobe-analytics
channel = lab
eVar1 = Adobe Analytics Sandbox
prop1 = lab:analytics
events = event1
contextData.page.section = analytics
contextData.page.template = sandbox

s.pageName = 'lab:analytics:adobe-analytics';
s.channel = 'lab';
s.prop1 = 'lab:analytics';
s.eVar1 = 'Adobe Analytics Sandbox';
s.events = 'event1';
s.contextData['page.section'] = 'analytics';
s.contextData['page.template'] = 'sandbox';
s.t();

Variable reference

propN: traffic variable. Hit-scoped, used for pathing and counts.
eVarN: conversion variable. Persists until it expires; success events are credited to it.
eventN: custom success event. Counter by default; can be numeric or currency.
contextData: key/value pairs mapped to props and eVars with processing rules.
s.tl(this, type, name): link call. o custom, d download, e exit.

With the Web SDK (alloy.js) the same data is sent as XDM. Page views and link clicks are both sendEvent calls, distinguished by eventType and web.webInteraction.

alloy('sendEvent', {
  xdm: {
    eventType: 'web.webinteraction.linkClicks',
    web: { webInteraction: { name: 'cta:request-demo', type: 'other', linkClicks: { value: 1 } } },
    _experience: { analytics: {
      customDimensions: { eVars: { eVar4: 'Request a demo' }, props: { prop4: 'cta:request-demo' } },
      event1to100: { event5: { value: 1 } }
    } }
  }
});