Full processing

IMPORTANT

Adobe recommends customers use the Bulk Data Insertion API (BDIA) instead of full processing data sources. Adobe plans to deprecate full processing data sources in the future.

Data Sources supports the following variables when processing data as a standard server call (Generic > Full Processing).

Full Processing data sources data is processed as if it were received by Adobe servers at the time specified (each hit contains a timestamp).

Visitor Profile

Full processing data sources data is processed using separate visitor profiles, so even if the visitor ID in uploaded data matches data collected using JavaScript or other AppMeasurement library, the visitor profiles are not connected from an eVar allocation perspective.

For example, a user with a visitor ID of "user@example.com" visits your site from a marketing campaign named “Spring Sale”, which is stored in the campaign variable. If you later upload a transaction using the same visitor ID, the “Spring Sale” campaign does not receive credit for any revenue or success events uploaded using full processing data sources.

Column Reference

JavaScript Variable Full Processing Column Variable Description

campaign

campaign

Conversion campaign tracking code.

channel

channel

Channel string (for example, Sports Section).

currencyCode

currencyCode

Note: This variable is also supported by Standard data sources as currency code .

Revenue currency code (for example, USD).

timestamp

date

Use the ISO 8601 date format of YYYY-MM-DDThh:mm:ss±UTC_offset (for example, 2013-09-01T12:00:00-07:00 ), or Unix Time Format (the number of seconds elapsed since January 1, 1970).

eVarN

eVarN, i.e. <eVar2>…</eVar2>

Conversion eVar name. You can have up to 75 eVars ( eVar1 - eVar75 ).

You can specify the eVar name (eVar12) or a friendly name (Ad Campaign 3).

events

events

Events string, formatted using the same syntax as the s.events variable.

For example:

scAdd,event1,event7

hierN

hierN, i.e. <hier2>…</hier2>

Hierarchy name. You can have up to 5 hierarchies ( hier1 - hier5 ).

You can specify the default hierarchy name ( hier2 ) or a friendly name ( Yankees ).

linkName

linkName

Name of link.

linkType

linkType

Type of link. Supported values include:

  • d: Download link
  • e: Exit link
  • o: Custom link.

linkURL

linkURL

HREF of link.

pageName

pageName

Page Name

pageType

pageType

Page Type ("Error Page").

pageURL

pageURL

Page URL (for example, https://www.example.com/index.html).

products

products

Product list (for example, "Sports;Ball;1;5.95"). Can hold a maximum value of 4096 bytes per row.

prop1 - prop75

propN, i.e. <prop2>…</prop2>

Property# string (for example, Sports Section ).

purchaseID

purchaseID

Purchase ID number.

s_account

reportSuiteID

Report suite ID(s) to which to attribute the hit.

server

server

Server string.

state

state

Conversion state string.

zip

zip

Conversion zip code.

The following table contains traffic variables that are populated automatically when using the JavaScript libraries. These properties do not have associated variables but can be imported using data sources.

Full Processing Column Variable

Description

browserHeight

Browser height in pixels (for example, 768).

browserWidth

Browser width in pixels (for example 1024).

charSet

The supported cahracter set for your Web site. For example, UTF-8, ISO-8859-1, and so forth.

See the Multi-Byte Character Sets (Internationalization) whitepaper for a complete list.

clickAction

Object identifier for visitor click map (oid)

clickActionType

Object identifier type for visitor click map (oidt)

clickContext

Page identifier for visitor click map (pid)

clickContextType

Page identifier type for visitor click map (pidt)

clickSourceID

Source index for visitor click map (oi)

clickTag

Object tag name for visitor click map (ot)

colorDepth

Monitor color depth in bits (for example, 24).

connectionType

Visitor's connection type ( lan or modem ).

cookiesEnabled

Y or N for if the visitor supports first party session cookies.

currencyCode

The default currency code used on your Web site.

For example, USD=U.S. dollars, EUR = Euros, JPY = Japanese Yen, etc.

homePage

Y or N -- is the current page the visitor's homepage.

javaEnabled

Y or N -- does the visitor have Java enabled.

javaScriptVersion

JavaScript version (for example, 1.3).

plugins

Semicolon separated list of browser plug-in names.

propN

Property values for your properties.

referrer

URL for page referrer.

resolution

Monitor resolution (for example, 1024x768).

scXmlVer

Marketing reports XML request version number (for example, 1.0).

timezone

Visitor's time zone offset from GMT in hours (for example, -8).

visitorID

Visitor ID number.

On this page