SudheeshN
Khoros Alumni (Retired)
Joined 6 years ago
User Profile
User Widgets
Contributions
Re: Khoros Communities: Aurora 25.04 Release Notes
jecollins Analytics will stay true to the time range selected (reflecting the states, pre and post merge) and will not be updated retroactively. Explaining two scenarios below. Topic B merges with Topic A If the analytics user selects a time before the Merge: the page views (or any other metrics) of Topic B will be attributed to Topic B itself and not to Topic A. If the analytics user selects a time after the Merge: Since, after the merge, there's only Topic A, the page views (and all other metrics) will be attributed to Topic A. If the analytics user selects a time straddling pre and post-merge: In the reports, both Topics will be present and the page views (and all other metrics) garnered by Topic B, till the time of merge will be attributed to Topic B. For the first and third scenarios above, it's important to keep in mind that, Topic B doesn't exist in the community anymore and hence, the reports will show hyphen (-) in the place of the Topic name. Topic B moves from Board B1 to Board B2 The Page views (or any other metrics) garnered by Topic B, while it was under Board B1, will not be attributed to Board B2.219ViewsSign in to react to this post0CommentsRe: Khoros Communities: Aurora 25.04 Release Notes
Different communities have been impacted differently and this occurred around the time the communities moved to Aurora. While a dip in traffic metrics was expected because of the short term impact of SEO, the issue with duplicate visitor IDs also contributed to the underreporting of traffic metrics. We will be sharing a detailed RCA for this issue soon.ViewsSign in to react to this postCommentRe: Aurora Analytics Metric Definitions
'Engaging in the community' refers to viewing a page in the community, in the context of DAU/MAU. MAU or Monthly Active Users is the #unique members (both logged-in and not logged-in) in a month. In Classic, we don't have a like-to-like metric representing the #unique members visiting community in a month. One way to compute this metric in LSI (Classic Analytics) is to use to the Unique Visitors metric in the 'Traffic' tab for a period of 30 days, after excluding the anonymous visitor count. Anonymous visitors can be excluded by applying the filter 'User Name ≠ Anonymous'.ViewsSign in to react to this postCommentsEmail Metrics in Community Analytics
Email Metrics in Community Analytics delivers one of the most sought after enhancements in our Ideas board and customer feedback sessions - provide a means to measure the efficacy of emails in engaging and bringing traffic back to the community. With the insights provided by Email Metrics, Community Managers can take appropriate actions to increase member engagement. What are the available metrics? The following metrics are available to track the journey of an email from the moment it gets triggered in the community to the recipient opening and clicking on a community link in the email. Emails Requested Emails Delivered Unique Opens Unique Clicks Emails Bounced Emails Dropped Unsubscribe Clicks The metrics are also segmented by community actions that trigger these email notifications. This includes - Subscriptions, Accepted Solutions, Mentions, Kudos and Private Messages. Any other community event/action are grouped under Miscellaneous (example : user rank change) Below are the prerequisites for a community to benefit from the Email metrics feature: should be on AWS should be using SendGrid as the email platform on Community Release version 20.11 or above *Data presented here is for illustrative purposes only; not to be construed as benchmarking. You can infer the following from the above metrics: Email notifications triggered by community actions 63034 Emails delivered successfully 59161 Number of emails opened at least once by users 24140 (40.8% Open Rate) Number of emails where users clicked on the community link(s) 5169 (21.4% Click to Open Rate) Open Rate measures the percentage of unique opens of the mails by users as compared to the total number of mails delivered. For example: If 100 users receive one email each, and 50 of them opens the email, then the Open Rate is 50%. Similarly, if 50 users receive 2 emails each and 25 of them opens both of them, then the Open Rate is 50% Click To Open Rate measures the percentage of emails where the users clicked on the community link(s) in the email as compared to the total number of emails that were opened. From example 1 above, if out of 50 users who opened the emails, 30 users clicked the Community link(s) in those mails, then the Click To Open Rate is 60%. Why do emails get dropped? As per SendGrid, an email may get dropped due to a variety of reasons. These may include invalid SMTPAPI header, spam content in the mail (if Spam Checker app is enabled), unsubscribed address, etc. How to enable Email Metrics for a community? Email Metrics is currently enabled for all the communities that are on AWS, on community version 20.11 and using SendGrid as the email relay set-up. If your community is not on SendGrid and want to benefit from this feature, open a Support ticket and request to change the email platform to SendGrid. SendGrid is Khoros’ default email relay set-up. SendGrid provides the means to successfully track events like successful email delivery, email delivery failure, and email being opened. These events are transmitted to Khoros using registered web-hooks. Learn more about Khoros email options Who can access Email Metrics in Community Analytics? Any user who could access Community Analytics would be able to access Email metrics as well. To access Community Analytics, a user needs to have either an Administrator role or Analytics role assigned. Questions or Comments? We are working on benchmarks and trends for Email Metrics. Meanwhile, you can contact your Customer Success Manager to provide you with these details, based on your industry. We also welcome any feedback to make this feature better! Thanks for reading!ViewsSign in to react to this postCommentsBilling Metrics in Community Analytics
Khoros Community contracts offer a set of subscriptions to the customers. These subscriptions also include two metrics: Billable Application Calls (BAC) and Annual Total Visits (ATV). In the past, Community packages came with a different set of metrics - Page Views, Human Page Views, and Server Requests. The above five metrics are collectively referred to as Billing Metrics. Billing Metrics in Community Analytics will help customers track some of the key performance indicators in their community and be able to predict how their contract with Khoros can change or grow in the future. The information provided includes a graphical representation of the metrics’ usage against the contractual tiers as well as the timeline view of the usage. User Interaction & Design The summary view at the top of the screen shows the aggregate of the total usage for all subscribed metrics in the time period chosen by the user. The comparison of the current usage is shown against the contractual tier limits for the metrics subscribed to in the community contract. There is one widget for each metric. Billable Application Calls: Billable Application Calls are calls made on the Community API (v1 & v2) that originate from an external site outside of the hosted Khoros Community instance. It also includes REST calls made in ActiveCast/Community Syndication components. Annual Total Visits: The annual entitlement as part of Annual Total Visits resets at the end of every 12 months from the contract start date. The usage % indicates the percentage of the entitlement consumed as of the last completed month. The timeline view of usage of the metrics is available in four different granularities: hourly, daily, weekly, and monthly. The user can download the usage data in CSV format as well as schedule a report to be delivered by email. Are the usage % updated in real-time? Not completely; the usage % for all the Billing Metrics are computed and displayed for the last completed month. However, the actual usage data is updated daily. Who can access Billing Metrics in Community Analytics? No special permission is required to access Billing Metrics. Any user who could access Community Analytics would be able to access Billing Metrics as well. To access Community Analytics, a user needs to have either Administrator role or Analytics role assigned. Feature Enablement Billing Metrics was made available for General Adoption as part of the 21.1 Community release. The activation of the feature was done based on customer requests. You can contact the Support team to request for the feature activation.ViewsSign in to react to this postCommentsRe: Remove community tags
Hi Lief The tag dashboard could be scoped to a place in the community which will allow the user to remove the tag from all of the posts inside that scope. However, you can't selectively remove tags from a subset of posts inside that scope. For such a scenario, the tag will have to be removed from the post directly.ViewsSign in to react to this postCommentsRe: Searching on the community
akloepfer Boards and board posts can be excluded from search results by toggling on the corresponding options under Board Settings - Display Settings. Doing so will also ensure that the board posts don't show up in the Recent Content widget.ViewsSign in to react to this postComments
219Views
0Comments
