\n eVar1<\/strong>
\n events<\/strong><\/td>\n
\n“Page A”
\n“event1”<\/td>\n
\n“Page B”
\n“event1”<\/td>\n
\n“Page C”
\n“event1”<\/td>\n
\n“Page D”
\n“event1”<\/td>\n
\n“”
\n“event2”<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
I saw this<\/em> in Reports and Analytics (so far, so good):<\/p>\n But then in Analysis Workspace for that prop, trying to recreate the same report, I saw this, where the props were only getting credited for events that happened on their beacon (none got credit for the newsletter signup): Basically, I lost that participation magic.<\/p>\n Similarly, for the eVar, I saw this report in Reports and Analytics:<\/p>\n And in Workspace, it behaved exactly like a “Most Recent” eVar: Again, it lost that linear magic.<\/p>\n With the help of some industry friends (thanks, Jim Kultgen at Kohler and Seth Burke at Adobe) I learned that this is not a\u00a0bug<\/em>, necessarily- it’s the future! Analysis Workspace has a different way of getting at that data (one that doesn’t require changing the backend settings for your variables and metrics). On further testing, in Analysis Workspace, it seems that eVars with the back-end settings of either “Most Recent” and “Linear” allocation are treated the same: both will act like “Most Recent” with a metric brought in, and both will act like “Linear” when you bring in a calculated metric where you specified to have Linear Allocation. One might say, if you use Analysis Workspace exclusively, you no longer would need to ever set an eVar to “Linear”.<\/p>\n “Default” does<\/strong><\/em> still seem to defer to the eVar settings when it comes to Most Recent or Original (just not Linear). So in an eVar report where the eVar’s backend setting is “Original”, whether I used my “normal” Newsletter Signups event (column 2), or my Calculated one with Linear Allocation (column 3), credit went to the first page: So, the Calculated Metric allocation did NOT overwrite my eVar setting of “Original”.<\/p>\n To get back that Linear Allocation magic, I would create a new Calculated Metric, but I would specify “Linear Allocation” for it in the Calculated Metric Definitions. Then I can see that linear metric applied to that eVar (the original metric in blue, the new calculated one with linear allocation in purple) : Similarly, with the prop, when I bring in my new “Linear Allocation” calculated metrics I just set up for my eVar (in blue), I now see it behave like participation for my Newsletter Signup metric, unlike the original non-calculated metrics (in green): …but those Page View numbers look just like linear allocation in an eVar would (2.08, 1.08, .58, .25), not the nice clean numbers (4, 3, 2, 1) I’d get for a prop with participation. At this point, I still don’t have my Content Velocity prop report, but I’m getting closer.<\/p>\n Analysis Workspace has a “Page Velocity” Calculated metric built into its Content Consumption template, which reports the same data as my Content Velocity (participation-enabled) prop did in Reports & Analytics.<\/p>\n Though my friend Jim Kultgen suggested a metric he prefers:<\/p>\n This shows you how a page contributed to later page views, discounting how it contributed to itself (because obviously it did that much- every page does), and looking at visits to that page (so repeat content views don’t count for much).<\/p>\n These two calculated metrics would show in an AW report like this: If I use Analysis Workspace exclusively, I may no longer need to enable participation on metrics or props- I could just build a Calculated Metric off of existing metrics, and change their allocation accordingly, and that would work the same with either my eVars or my Props.<\/p>\n Knowing a few of these quirks and implications, I can see a future with simpler variable maps (no more need for multiple eVars receiving the same values but with different allocation settings) and the ability to change allocation without tweaking the original data set (my “Newsletter Signups” metric retains its original reporting abilities, AND I can build as many Calculated Metrics off of it as I want). I’m excited to see how Adobe will keep building more power\/flexibility into Workspace!<\/p>\n","protected":false},"excerpt":{"rendered":" I recently posted about some of the implications and use cases of using Linear Allocation (on eVars) and participation (props\/events) and in my research, I thought I had encountered a bug in Analysis Workspace. After all, for this flow: Page A Page B Page C Page D Newstletter Signup event (s.tl) prop1 eVar1 events “Page … Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,23],"tags":[19,3,58],"_links":{"self":[{"href":"https:\/\/www.digitaldatatactics.com\/index.php\/wp-json\/wp\/v2\/posts\/370"}],"collection":[{"href":"https:\/\/www.digitaldatatactics.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.digitaldatatactics.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.digitaldatatactics.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.digitaldatatactics.com\/index.php\/wp-json\/wp\/v2\/comments?post=370"}],"version-history":[{"count":7,"href":"https:\/\/www.digitaldatatactics.com\/index.php\/wp-json\/wp\/v2\/posts\/370\/revisions"}],"predecessor-version":[{"id":435,"href":"https:\/\/www.digitaldatatactics.com\/index.php\/wp-json\/wp\/v2\/posts\/370\/revisions\/435"}],"wp:attachment":[{"href":"https:\/\/www.digitaldatatactics.com\/index.php\/wp-json\/wp\/v2\/media?parent=370"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.digitaldatatactics.com\/index.php\/wp-json\/wp\/v2\/categories?post=370"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.digitaldatatactics.com\/index.php\/wp-json\/wp\/v2\/tags?post=370"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"\"](\"\/\/digitaldatatactics.com\/wp\/wp-content\/uploads\/2018\/01\/participationRAfull-1.png\")
<\/a><\/p>\n
\n<\/a><\/p>\n<\/a><\/p>\n
\n<\/a><\/p>\nCalculated Metrics to the Rescue<\/h2>\n
\nIn Analysis Workspace reports, allocation can be decided by a Calculated Metric<\/a>, instead of the variable’s settings. In the calculated metric builder, you can specify an allocation by clicking the gear box next to the metric in the Calculated Metric Definition:<\/p>\n<\/a><\/p>\nA Note On “Default” Allocation here<\/h4>\n
\n<\/a><\/p>\nSo how do I replicate my Linear eVar report?<\/h2>\n
\n<\/a>
\nNote that it’s 40-20-20-20, rather than 25-25-25-25. I’ll admit, this isn’t what I expected and makes me want to do more testing. I suspect that it’s looking at my FIVE beacons (four page views, one success event) and giving that Page D double credit- one for its page view beacon, and one for the success event beacon (even though it wasn’t set on that beacon, it WAS still persisting). So it isn’t perfectly replicating my R&A version of the report, but it is helping me spread credit out between my four values.<\/p>\nAnd my participation prop?<\/h3>\n
\n<\/a><\/p>\nSo how do I get my Content Velocity?<\/h3>\n
<\/a>\u00a0If I want to recreate this calculated metric for myself, I use the formula “Page Views (with Visit Participation)\/Page Views”<\/em>:
\n<\/a><\/p>\n((Page Views 'Visit Participation')\/(Visits))-1<\/pre>\n
<\/a><\/p>\nConclusion<\/h3>\n