BT not splitting as expected for referrer
I have a measurement (revenue) that pulls an argument value from a method:
This works, I get values from it, such as revenue by location:
When I want to pull revenue by referrer it does not work - I get all the referrers but no revenue numbers (if I used revenue as a filter no information is reported), the major difference is this is by visit not PP. I cannot do this by PP as the referrer will pull the referrer of the method call:
So is there a way of pulling the very first referrer against the revenue (that could be anywhere in a visit)?
Matthew
Can someone answer me this (it will help with my issue I hope) - Referer on a visit - how does it work this out?
So I have a measure which I 'think' should pull out the very first occurrence of a referer in the visit, but this is not happening, if the first referer is www.google.com but then subsequest PP have www.thewebsitename.com the referer will record as the latter. Meaure:
easyTravel all seem to be localhost for referer so I cannot test it there.
Using the easyTravel application, I was able to get the revenue split by the header value referer and using the option of server side PP for the BT. I pulled the referer from the header value of the Purepath.
Does this help? or did I misunderstand your question?
Regards,
Harshal.
please drop me an email 
Matthew,
I'm out of ideas, but I'm still happy to jump on a WebEx and take a look, if you'd like.
-- Graeme
Hi Dave... Thanks for the suggestion as all are welcome. Unfortunately it didn't work, I even tried recreating the method sensor!
Hi Matthew,
I doubt it will help in your case, but since it may be a factor, please see this post and try the workarounds if you added the results or splits to a BT that already had been running for a while:
Business Transactions Dashlet vs. Business Transactions Hotspots Dashlet Results
dave
Hi Graeme,
Left them over night and got no results. I even set up a BT that was as minimal as possible (below) and did not get any results. (I do see revenue if based on PP as opposed to visit)
Matthew,
I verified using our easyTravel demo application that you can calculate revenue per visit using a method argument measure to collect revenue.
However, I did notice that it took a long time to see results. Part of this delay is due to the fact that visit BTs can't be calculated until after the visit is complete.
If you're still not seeing results from your last BT after letting it run overnight, perhaps you could jump on a WebEx so that I could have a look at it?
One final thought: could you try charting your revenue measure just to make sure that it's returning the values you expect?
-- Graeme
Unfortunately, that did not work.
What I have done now is set up a BT with very little in it, purely no bots and calculate revenue split on application. This too does not work, I have a feeling revenue is only working on BT's calculated on Server-side PurePath.
Matthew,
I'd try changing the aggregation in the results section from last to sum.
-- Graeme
