"-4% to 4% variation in Visits and Unique Visitor metrics." is meant to the variance expected(Due to LSI uses HLL) between Visits/Unique_Visitor shown in LSI(CA) Traffic Overview - top bar(Summary) and Visits/Unique_Visitor computed using Bulk API data.  Visits/Unique_Visitor shown in LSI(CA) Traffic Overview - top bar(Summary) and Visits/Unique_Visitor computed using Bulk API data are comparable.  Visits metrics query for Bulk API data: SELECT COUNT (DISTINCT visit.id) FROM <<bulkdata>> WHERE action.key="view" AND event.time.ms >= start_time_ms AND event.time.ms <= end_time_ms Unique Visitor metrics query for Bulk API data: SELECT COUNT (DISTINCT visitor.id) FROM <<bulkdata>> WHERE action.key="view" AND event.time.ms >= start_time_ms AND event.time.ms <= end_time_ms If you observe the above queries Visits/Unique_Visitor metrics are derived using page view records. If page views are matching than HLL approximation is the only reason for the difference for the metric shown LSI(CA) Traffic Overview - top bar(Summary) and Visits/Unique_Visitor computed using Bulk API data.  Once again we would like to repeat the data used to derive CA(LSI) metrics is the same as the data exposed via Bulk API. CA(LSI) stores this same data to elasticsearch and derive metrics with ES queries. LSI Traffic Overview - top bar: 155933 vs LSI Traffic Overview - graph "Visits":  153760  this difference due to HLL and overlapping for a visit across month/days/hours. Overlapping visits explained here ... View more

Hi, PageView : A page view is counted each time a browser requests a page.  Visits : A visit is one or more page views belong to one or more categories over time by a uniquely identified client (visitor) in a session over the specified time interval.  Unique Visitors:  The number of unique visitors over the specified time interval. A unique visit may contain multiple visits by a user. A pageview is a discrete event, but Visits and Unique visits are not discrete. A visit may contain multiple pageviews, these pages may belong to different categories/boards.  When you aggregated visits on category/board belongs to a visit, it is counted across multiple categories/boards. The same logic applies to Unique visitors. Adding up Visits and Unique visitors after category/board level aggregation like below is not a right metric. There is an overlap of a visit on different boards. Let's take an example, a user with user-id:1234  visits (visit-id:visit111) to the community and activities are as follows.  User Landed/login into community Home (Home does not belong any category) - 1st pageview - 1 visit - 1 Unique Visitor viewed a page let's call it page111 in category  Category-1/Boards-1 Community.               - 2nd pageview - 1 visit - 1 Unique Visitor viewed another page let's call it page222 in category Category-2/Boards-2   Community        - 3rd pageview - 1 visit - 1 Unique Visitor   For this user activity in a visit here is the metrics _______________________________________________________________________________ In  summary, metric counted a -  3 pageview - 1 visit - 1 Unique Visitor. ( 1 pageview  attributed to community Home Page that may not belong to any category)  _______________________________________________________________________________ When  aggregated on category/board level        Category-1/Board-1 Community.           - 1 pageview - 1 visit - 1 Unique Visitor      Category-2/Board-2  Community          - 1 pageview - 1 visit - 1 Unique Visitor ________________________________________________________________________________ If you do add up(like you did in CSV).         2 pageview - 2 visits - 2 Unique Visitor .  Adding up Visits and Unique visitors after category/board level aggregation is not the right metric. if need you more information, we request to you file a support case. So that we can provide more information and data to support.  ... View more

Hi if these are the queries raised by customer community.anaplan.com, there is an internal Jira ticket created for the same. We would like to discuss the metric by metric, queries in the Jira. The data used to derive community analytics is the same date exposed via Bulk API. All the metrics(except Visits and Unique Visitor) in Community Analytics should match Bulk API data. Visits and Unique Visitors won't exactly match you may see -4% to 4% variation. We are happy to take look at each query and help.    ... View more

  Please recheck your queries used for computing the above metrics. Make sure the timeline and Bulk API data is successfully download without any error.  Description of fields available in Bulk API https://developer.khoros.com/khoroscommunitydevdocs/reference/lithium-bulk-data-api   You find sample example queries to compute a few metrics from Bulk API https://community.khoros.com/t5/Community-Analytics/Mapping-Community-Bulk-Data-API-fields-to-Community-Analytics/ta-p/553946   Pageviews and all other metrics(except Visits and Unique Visitor) in Community Analytics should match Bulk API data.   To compute Visits and Unique Visitor Community Analytics leverages HLL, due to this approximation algorithm you may see -4% to 4% variation in Visits and Unique Visitor metrics. https://community.khoros.com/t5/Khoros-Communities/Regarding-calculation-of-VISITS-and-UNIQUE-VISITORS-in-LSI/m-p/455929 https://community.khoros.com/t5/Support-Forum/How-is-unique-visitors-calculated-in-LSI/m-p/195886   ... View more