Hello,
I'd like to learn more about an example of a Page Name parameter fired along with Action. There are couple of things which look suspicious:
a. pageName is usually set for trackState and not an action, in this case it's attached to Action
b. pageName is always named in a way which can be easily interpreted by a human, in this case it's just numbers
Please have a look below:
Does anyone of you know can it have an impact on inflation of Page Views for example?
Regards
Rafal
Solved! Go to Solution.
Views
Replies
Total Likes
Pagename is set for both trackState and trackAction but the Page View is only counted for a trackState call. It is same like s.t and s.tl calls.
Within s.tl calls you will see pagename variable getting fired but it never makes to the Pages report.
pageName is something which is defined by the client. If you are using Launch whatever you mention in State under rule will be send as pageName. If the pageName has already been set on the page via trackState call and then you do some action, the action call will have the same pageName as the trackState call but it will not increment the page view.
Views
Replies
Total Likes
Pagename is set for both trackState and trackAction but the Page View is only counted for a trackState call. It is same like s.t and s.tl calls.
Within s.tl calls you will see pagename variable getting fired but it never makes to the Pages report.
pageName is something which is defined by the client. If you are using Launch whatever you mention in State under rule will be send as pageName. If the pageName has already been set on the page via trackState call and then you do some action, the action call will have the same pageName as the trackState call but it will not increment the page view.
Views
Replies
Total Likes