Record page Title and subsequest URI
I want to record the page title from where a button was clicked and the subsequent URI of the request.
So, I am on a page www.notreal.com/all (title "ALL"), on that page is a button "play this", when I click "play this" it creates a new window. I want to record the "ALL" title and the URI that comes from clicking the "play this" button. This will allow me to record what is being played the most and from which page people are selecting the game.
I feel like I should know this one!! But all I seem to do is record either the URI of the new page or just the number of "play this" count.
Hi Matt,
Do you have UEM? If so you could create a Business Transaction that filters on the 'play this' action (Page Action Count Measure) and splits by Source Page Title (Page Actions - Name Measure) and Target Page URI (Page Actions - Name Measure).
thanks,
ted
Hi Ted,
Yes we do have UEM. I have set up a Measure, Metric "Count (User Actions)" action name matches "click play this". I create a BT, filter on this measure, I then get a list, split on Page Source Title.
Am I missing something here - if I drill down in to the visits of any of the details I'd expect to see a "click "play this"" as a user action - but I do not always see it?
Is the BT "User Action" or "Visit" based? Also, what threshold and aggregation are you using for the filter measure?
Rick B
I think you have found it.. my lower threshold was 0..... dumb yes!!! Set it to 1 and it looks (initially) like it is weeding out the non measurements.
I have the BT set to User Action - is this correct?
It works with page source title, as soon as I add target uri I get no measurements!
You need two measures - one for source and one for target - add them both to the split table.
My issue is when I add target URI. If I have the filter and source - it pulls in info. As soon as I add target nothing get pulled in. is there anyway i can test target URI? The Target URI measure is Page Action - Target URI, threshold exceeds 1
Can you share any of the following (ranked from most to least helpful):
- Exported visit with example desired action
- Exported system profile
- Screenshots of BT and Measure configuration screens
Matt,
The info Rick is requesting would be very helpful, but just to be clear, you should have 1 Filter Measure (Page Action Count) and 2 Split Measures (Page Action Name with Source Page Title checked and another Page Action Name with Target URI checked)..
---ted
Hi
Attached is an exported visit, if you look at the visit there is "click on "Play Now" on **", I would expect my BT to show 4 entries, all showing the same Title, but showing 4 different Target URI's -which comes from the web requests.
Also attached is the BT and measurements (Target URI is left out because it is stopping any info from reporting).
Filter measurement:
Page source works:
Target URI does not:
Cheers for the help guys - much appreciated.
Hey Matt,
OK - I see the problem now. The click on "Play Now" Action does not result in a page load. If it did, we'd see a "Loading of Page..." node right below the Action node in the User Action PurePath - basically a node between the action and the Web Requests node. So, there is no 'target page'. You could split on the Web Request instead, maybe with a Complete URI Pattern Measure, but you'd end up with lots of split values, one for every web request in the User Action PurePath. I can't see the URI names due to confidential strings, but maybe you could configure the URI Pattern to not match any javascript, images, etc. to get it down to only 'meaningful' URIs (using contains or not contains or the like. Or even some configuration that will only match the typical first web requests.
===ted
Hi Ted,
That makes sense. I have created the following measurement that works if source URI is not present i.e it picks out the web requests. If I add it to the BT (So both source URI and web request are present) there are no splittings - it shows the count increasing but in the splittings column I get "-". The BT has no restriction on splittings.
Hey Matt,
It's going to be a little tricky for me to help since I don't have the data (confidential strings prevents me from seeing URIs), but if I were in your situation I would create a BT that simply splits on your URI Pattern Value measure - no filter, no other custom split - and verify it works. I think your regex might be off (missing \ before ) within []?). Then I'd create a BT that filters on the click on play and only splits on the URI and verify it works and then I'd try the filter with 2 splits BT.
I have duplicated the intent of your BT in my easyTravel System Profile - using different URI Pattern Values and Click Actions of course - and it does work. That is to say it does work technically - I get the expected filter and multi-splits, but it's not interesting in my case since the Click Action doesn't result in a new page load so the source and 'target' are effectively the same page. Again, without seeing your URIs and I don't know if that's the case with you too.
===ted
