I am trying to track events that take place on an embedded training on a page. When a user clicks various items on the training, I am firing a s.tl() call. I see it is successfully firing in the debugger. How do I view the data when building a report in the Analysis workspace?
Solved! Go to Solution.
Views
Replies
Total Likes
Not sure how familiar you are with the Adobe tracking architecture, so I will start with some basics.
s.t - as you probably know are "Page Views"
s.tl - are "clicks" or actions
What you may not realize, even though you see a pageName and pageURL value being sent on your s.tl calls, these are actually stripped from the tracking during the process... the reason being that Adobe uses the presence of "pageName" or "pageURL" to determine when to increment a page view metric, so in order to not inflate you PVs, those two fields are removed (basically when Adobe sees the linkName, and Page Event Vars (pev1 / pev2).
Now, if you aren't setting an explicit event on your calls, you will need to use the Custom Link Instance (you can use Occurrence, but depending on your correlation variables, this may cause issues). If you do have an explicit event being sent (like event1 or event27, etc) then use that.
Now, take a look in your debugging at the "Link Name", assuming you are using link type "o" for "other", the Link Name should appear in a dimension called "Custom Link" in your Workspace. (If it's "e" or "d" then the data will go into specific Exit Link or Download dimensions).
If you are sending any additional props or eVars on your s.tl calls, you can breakdown your Custom Link dimension using them.
Views
Replies
Total Likes
Not sure how familiar you are with the Adobe tracking architecture, so I will start with some basics.
s.t - as you probably know are "Page Views"
s.tl - are "clicks" or actions
What you may not realize, even though you see a pageName and pageURL value being sent on your s.tl calls, these are actually stripped from the tracking during the process... the reason being that Adobe uses the presence of "pageName" or "pageURL" to determine when to increment a page view metric, so in order to not inflate you PVs, those two fields are removed (basically when Adobe sees the linkName, and Page Event Vars (pev1 / pev2).
Now, if you aren't setting an explicit event on your calls, you will need to use the Custom Link Instance (you can use Occurrence, but depending on your correlation variables, this may cause issues). If you do have an explicit event being sent (like event1 or event27, etc) then use that.
Now, take a look in your debugging at the "Link Name", assuming you are using link type "o" for "other", the Link Name should appear in a dimension called "Custom Link" in your Workspace. (If it's "e" or "d" then the data will go into specific Exit Link or Download dimensions).
If you are sending any additional props or eVars on your s.tl calls, you can breakdown your Custom Link dimension using them.
Views
Replies
Total Likes
Views
Like
Replies