I am trying to understand fully what discrepancies you are seeing, since I can't really see your data.
First, while you can use Tracking Code and a custom Visit Level eVar for analysis (I do, as another dimension to our data), I should point out that this will differ from Marketing Channels for a few reasons:
- Marketing Channels have a default 30 day attribution, though you may have changed this to 7 days to match up better with tracking code
- Unless you changed the default behaviour, "direct" traffic won't override other specific marketing channels, your Visit level eVar when no parameters will use "Direct" as the last touch.
Now, I am interested in how you built your segments?
Keep in mind that one visit may have multiple tracking codes...
Example:
- Google Search - Paid Campaign Params = X
- Back out to Google, click on Organic result = no param, so last touch is still "X"
- Newsletter arrives, user clicks on a link, Email Campaign = Y
- User gets a ping on Social Media, click through with Social Campaign = Z
- Order is made (last touch should be Z)
The same visit touched X, Y and Z
Now, if you created Visit Level Segments, you will have overlap between these three, since all three were in the same visit...
Example:
| |
Orders |
| |
3 |
| Segment: X (Visit) |
1 |
| Segment: Y (Visit) |
1 |
| Segment: Z (Visit) |
1 |
Now, when you use segments in table, the totals are not de-duplicated, so if this is what you are seeing, yes, your orders and revenue will be over-counted.
It's a little strange, but Segments and "locked" dimensions (i.e. dimension values that are dragged over one at a time and are locked act like a Quick Segments) don't de-duplicate, but pulling over a Dimension that will auto adjust based on all values (standard drag of the dimension item, i.e. eVarX), will de-duplicate.
You really should be using a Hit level Segment, when paired with the Order, you will see the last touch value "Z" associated to the Order...
| |
Orders |
| |
1 |
| Segment: X (Hit) |
0 |
| Segment: Y (Hit) |
0 |
| Segment: Z (Hit) |
1 |
The Hit shouldn't have multiple values, the last carried forward value (whether for the week, or for the visit) should be the only item that pairs with your Order/Revenue values. Keep in mind that both Tracking Code and your eVar have attribution... all hits will have the value.. you don't need to build your segments to Visit level attribution, you really want to see what specific value was tracked at the time of the Order... hence using "Hit".
You can still use order attribution, changing the model to "Participation" or another custom model, but the totals will likely go wonky again.. mostly because of using segments... if you were applying the model based on the dimension alone, the totals should de-duplicate...
We really need more controls on our totals, to allow us to select whether or not to apply de-duplication when dealing with segments as breakdowns
