Hi @safikhan,
visit_duration field won’t present when a visit contains just one user activity (like just a pageview). To deliver visit_duration we need at least two user activities in a session.
The absence of visit_duration is equivalent to visit_duration = 0; let’s take an example: a user searches for something in google and clicks on a community link shows google search results and landed on a community page and just closed the browser tab to exit from the community. In this case, a one-page view is recorded. There is no followed user activity after this page view to calculate user duration when generating ‘visits.visit-summary’ for this user session visit_duration won’t present.
Hello MohammedF
I was searching for a similar solution, I am glad that I found your thread. We are looking for the visits duration of users who have accessed the portal and accepted a solution from any thread. Can you please help me with this data?
Nayaz-S By portal, if you mean the community, you will have to make something custom using the Bulk Data API to track the user and whether the person accepting the solution is the same as the tracked user:
visits.member-entrance
Visit login event
action.duration
Visit duration in seconds
solutions.accept
The message is marked as an accepted solution
MohammedF Thank you for the guidance. We did look at your recommended metrics and found some inconsistencies.The action duration is mostly blank for users with more than one activity. Any thoughts on this?
Fyi.. We are looking for the visit duration of users who have accessed the community and viewed an accepted solution.
Nayaz-S visit duration is unavailable for users who have accessed the community and viewed an accepted solution, so I recommended the custom way to achieve what you want. As you see inconsistencies in the metrics, I recommend creating a support ticket with the date ranges where you find this discrepancy to investigate this.
