eVars and events in product variable are proceeded by 1&2 respectively.
we are passing eVar17,19.
but in product string in debugger it's capturing as eVar117,119.
similarly for events, we are passing as event52
but in product string in debugger it's capturing as event252
@jennifer_dungan @yuhuisg @andrey_osadchuk @akt0m3r
Yes, Adobe is confusing that way.. but this is actually expected....
The "Name" that you see when tracking eVars and events (i.e. eVar17, eVar19, event52) are different than the raw data identifiers in the database.
You get to know this really quickly when you work with the Raw Data Feeds (well at least for events... I actually had to contact support for the eVar mappings to support post_product parsing).
Remember that there are standard reserved events like "Purchase", "Product View", "instance of eVarX", etc... all of those show up in processed data....
So if you look at the event.tsv file that comes with Raw Data Feed, it will map them out:
Purchase is event ID 1
Instance of eVar1 - Instance of eVar100 are actually IDs 100-199 (these are standard account eVars)
Then when Prime and Ultimate packages came along, Instance of eVar 101-250 are actually IDs 10000-10149
You custom events (event1, event2, through to event100) are actually IDs 200-299 (again standard package)
Premium package events (event101-1000) are actually IDs 20100-20998
Most of the mobile instance of events are in the 5xx, AMO in the 6xx, Mobile App Lifecycle in the 7xx; etc...
Likewise, eVars have mapping to Adobe's DB...
101-175 | eVars 1-75
275-299 | eVars 76-100
1200-1349 | eVars 101-250
Since you are looking at "Post Processed" Data, you will see things appear like this, but it's expected.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.