Skip to main content
Solved

Audience Dashboard vs Login Export CSV data comparison inquiry


genells
  • Contributor ⭐️⭐️⭐️
  • 19 replies

Hi Community Members!

 

Hoping someone can help me with with a confirmation on my logic when reviewing two separate data points from my Gainsight Community CONTROL Analytics view.

 

Screen capture Audience dashboard and Registered unique visitors

 

I pulled two data sets:

  • Under - Analytics - Audience dashboard and Registered unique visitors

  • Export CSV for Login

Same date range for both items. 

 

My question is: should these two data points match? Ex: If my registered unique visitors show 100 should the export csv showcase (with the appropriate calculations) 100 unique logins?

 

Trying to verify if these two data points are one and the same with simply different terminology (login vs registered unique visitors). 

 

Using my Audience dashboard can sometimes get confusing as we have a private community so other data points like guests don’t really equate into our scenario so any help understanding this dashboard is greatly appreciated!

 

Thank you!
 

Best answer by DannyPancratz

This stuff is super confusing, but they likely will not match. 

The analytics are measuring Users with two different events: 

  1. Login - date & time when they actually log-in
  2. Visit - closer to a page view, but not a page view.
    Show content

    Definition from insight on the Salesforce integration (whether you use it or not, that’s the event they’re capturing and using here)


    Community visited (recorded when a logged-in user starts or resumes a new session on the community. This is capped at maximum 1 community visit recorded every 30 minutes. In that way, it''s pretty similar to how a ''session'' is defined in tools like Google Analytics).

     

     

     

Login cookies keep users logged in for many days/weeks. By tracking the actual visit, it allows better data when you filter down to a single day. (Whereas if you export the login info, you don’t know if someone who logged in yesterday also visited today)

Visit is much better for tracking active users, especially if you use the Salesforce integration or the Data Lake Beta. (Unfortunately, there’s no way to get that via CSV exports, just Salesforce or data lake).

Using Visits, I can identify Daily, Weekly, Monthly active users. Each visit is an event data point passed to Salesforce (or in the data lake) and I look at them retroactively. Login data usually changes in exports to show the last login. Or on the Login export, you don’t know if someone was active (by visiting) on days they didn’t have a login event. 

View original
Did you find this topic helpful?

2 replies

DannyPancratz
Forum|alt.badge.img+7
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • 963 replies
  • Answer
  • August 29, 2024

This stuff is super confusing, but they likely will not match. 

The analytics are measuring Users with two different events: 

  1. Login - date & time when they actually log-in
  2. Visit - closer to a page view, but not a page view.
    Show content

    Definition from insight on the Salesforce integration (whether you use it or not, that’s the event they’re capturing and using here)


    Community visited (recorded when a logged-in user starts or resumes a new session on the community. This is capped at maximum 1 community visit recorded every 30 minutes. In that way, it''s pretty similar to how a ''session'' is defined in tools like Google Analytics).

     

     

     

Login cookies keep users logged in for many days/weeks. By tracking the actual visit, it allows better data when you filter down to a single day. (Whereas if you export the login info, you don’t know if someone who logged in yesterday also visited today)

Visit is much better for tracking active users, especially if you use the Salesforce integration or the Data Lake Beta. (Unfortunately, there’s no way to get that via CSV exports, just Salesforce or data lake).

Using Visits, I can identify Daily, Weekly, Monthly active users. Each visit is an event data point passed to Salesforce (or in the data lake) and I look at them retroactively. Login data usually changes in exports to show the last login. Or on the Login export, you don’t know if someone was active (by visiting) on days they didn’t have a login event. 


genells
  • Author
  • Contributor ⭐️⭐️⭐️
  • 19 replies
  • August 30, 2024

Thank you @DannyPancratz appreciate the detail response and suggestion.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings