Conversion variables
Variable | Read/write status | Description |
---|---|---|
eVar 1-250 | Read + write | eVar dimensions. |
Campaign | Read + write | The Tracking code dimension. |
Purchase ID | Read + write | The purchaseID implementation variable. |
State | Read + write | The state implementation variable is retired. |
Zip | Read + write | The Zip code dimension. |
Currency code | Read + write | The currencyCode implementation variable. IMPORTANT: If you set this variable to an invalid value, the hit is discarded. |
Transaction ID | Read + write | The transactionID implementation variable. |
Adobe does not support setting the
products
implementation variable using processing rules.Traffic variables
Variable | Read/write status | Description |
---|---|---|
Prop 1-75 | Read + write | Prop dimensions. |
Hierarchy 1-5 | Read + write | Hierarchy dimensions. |
Server | Read + write | The Server dimension. |
Channel | Read + write | The Site section dimension. |
Context variables
All Context data variables that this report suite has seen in previous image requests. If processing rules do not place context data into another variable, that data is permanently lost. See Copy a context data variable to an eVar and Set an event using a context data variable for usage examples.
Success events
Processing rules can set events but cannot read them as conditions. Set the rule action dropdown to Set event to see available metrics to increment.
Variable | Read/write status | Description |
---|---|---|
Orders | Write only | The Orders metric. |
Carts | Write only | The Carts metric. |
Cart views | Write only | The Cart views metric. |
Checkouts | Write only | The Checkouts metric. |
Cart additions | Write only | The Cart additions metric. |
Cart removals | Write only | The Cart removals metric. |
Event 1-1000 | Write only | Custom events. |
Product views | Write only | The Product views metric. |