Currently, in Baidu Analytics' Reporting platform, for Tracked Events, such as Clicks on file download, mailto or outbound links, the category of the event and the label would be displayed in different tabs.

We could have imagined the category of tracked events to be displayed in a table, on the same page as the labels, but it doesn't seem to be the case currently and tracked labels/messages and categories are displayed on separate pages, which doesn't necessarily seem practical at all, given that we would have to switch between a tab and another to check what each tracked message could be.

Maybe a simple and appropriate solution for the moment, would be to add tracked event's category in the label/message to be displayed in Baidu Analytics' backend.
In this case records for links tracked would then display in Baidu Analytics as for example:

Mails: example@example.com
Outbound links: http://www.example.com 
Downloads Link: example.zip.

still with each corresponding category: Mails, Outbound links and Downloads respectively.

This way, when checking tracked labels for the email addresses, downloaded files or clicked outbound links, it would be possible to quickly find out to which category it could correspond.

Please let me know if you would have any questions, objections, comments, suggestions, recommendations or concerns on any aspects of this feature request, I would be glad to provide more information or explain in more details.

Any questions, feedback, testing, changes, ideas or recommendations would be highly appreciated.
Thanks to all in advance.

Comments

dydave’s picture

dydave commented
Status: Active » Fixed

Quick follow-up on this feature request:

Modified the file baidu_analytics.js to add the tracked Events' category in the label to be recorded in Baidu Analytics' Reports, as suggested in the issue summary.
Message labels for the tracked events related with Mails, Outbound and Download links should all contain the category when displayed in Baidu Analytics platform.

I went ahead and committed the changes against the 7.x-1.x branch at 6f1e14a.

I allowed myself to mark this issue as fixed for now, but feel free to re-open it, or post a new ticket, at any time if you have any further objections with this issue or related commit 6f1e14a (we would surely be happy to hear your feedback).

Please let me know if you would have any further comments, feedback, questions, issues, objections, suggestions or concerns on the commit or this feature request in general, I would be glad to provide more information or explain in more details.

Special thanks to @xiukun.zhou for his great help testing and debugging this issue which was rather difficult to detect.
Thanks in advance to everyone for your testing, reviews, feedback and comments on this issue.
Cheers!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.