This help page describes how to implement eVars. For information on how eVars work as a dimension, see eVars in the Components user guide.
eVars are custom variables that you can use however you’d like. If you have a solution design document, most dimensions specific to your organization end up as eVars. By default, eVars persist beyond the hit they are set on. You can customize their expiration and allocation under Conversion variables in Report suite settings.
The number of available eVars depends on your contract with Adobe. Up to 250 eVars are available if your contract with Adobe supports it.
Before using eVars in your implementation, make sure you configure each eVar in report suite settings. See Conversion variables in the Admin guide.
eVars are mapped for Adobe Analytics under the XDM fields
You can set eVars either while configuring the Analytics extension (global variables) or under rules.
You can set an eVar to a value or a data element. You can also copy the value from another Analytics variable.
Each eVar is a string that contains custom values specific to your organization. Their max length is 255 bytes; values longer than 255 bytes are automatically truncated when sent to Adobe.
s.eVar1 = "Example custom value";
eVar values typically contain a string value. However, you can configure eVars to instead contain a counter. For example, you would like to count the number of internal searches made before a purchase. Instead of setting a text value, you would use the following syntax:
// Increment a counter eVar by 1 s.eVar1 = "+1"; // Increment a counter eVar by 12.49 s.eVar1 = "+12.49";
If more than two decimal places are given, the eVar counter rounds to two decimal places. An eVar counter cannot contain negative numbers.
You must first configure eVars to ‘Counter’ in the Admin Console before using counter eVars. See Conversion variables in the Admin guide.