You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can we add analytics tracking for share functionality in ASC?
Since analytics we use on all websites to track the user-data. I would request if we can add a query parameter at the end of url that gets shared over the email.
Solution:
Can we create a new tab 'Analytics' in E-mail Share modal dialog which is under /content/asset-share-commons/en/light/actions/share.html. Under Analytics tab create a new field 'Query Param'. This value will be picked and appended in assetLinkHTML for every link.
assetLinkHTML is getting generated in EmailShareServiceImpl in getAssetLinkListHtml() line number 168 where url is appended. Here we can add the query param value that comes from dialog.
It would be helpful if this can be achieved and provided as a part of ServicePack.
The text was updated successfully, but these errors were encountered:
Hi @skumuda - if we set it at the Dialog level, this will set the same value for every share link -- is that what youre going for? You just want to know what Details page views are from shares vs navigating via search/bookmarks?
Hi,
Can we add analytics tracking for share functionality in ASC?
Since analytics we use on all websites to track the user-data. I would request if we can add a query parameter at the end of url that gets shared over the email.
Solution:
Can we create a new tab 'Analytics' in E-mail Share modal dialog which is under /content/asset-share-commons/en/light/actions/share.html. Under Analytics tab create a new field 'Query Param'. This value will be picked and appended in assetLinkHTML for every link.
assetLinkHTML is getting generated in EmailShareServiceImpl in getAssetLinkListHtml() line number 168 where url is appended. Here we can add the query param value that comes from dialog.
It would be helpful if this can be achieved and provided as a part of ServicePack.
The text was updated successfully, but these errors were encountered: