Advance Notice

[Tue 10 Dec 2019] Coming up: significant change to how the dashboards process data

  • 29 November 2019
  • 1 reply
  • 334 views

Userlevel 7
Badge +1

On Tuesday 10th December 2019, we’re going to start rolling out a significant change that will impact current and historical data for all three dashboards. 

  • You don’t need to take any action.

  • The change will take up to 24 hours to roll out across all customers.

  • You can continue to use the dashboards in the meantime.

​​​

Background

  • As we mentioned last week, we’re working on improvements to the dashboards to make them more transparent, reliable and a better fit with your expectations about how the data should be processed.

Why we’re making this change

  • One major point of feedback we heard from you is that it’s more important for the dashboard metrics/filters to reflect the current state of the community, rather than ‘what happened at the time’.

  • As a result, we’re changing the dashboards to process content data according to the current state of the community.

  • This will align the dashboards better with the data you see in the topic/post/user exports, and make the data easier to verify. 

Why this date?

  • We know that the majority of our customers generate reports at the start or end of each month (and some at the very start of the week).

  • We've picked Tuesday 10th December to minimize any disruption to your reporting workflows, as the majority of work involving Dashboards happens at the end and/or beginning of each month.

What is the impact?

  • All metrics & filters related to content will be affected (e.g. category, content type, count of # topics).

  • Metrics & filters related to users will not be affected, as they are already based on the current state (e.g. user role, user rank, # community members).

  • If your community was migrated from another vendor, then your all-time numbers related to content are likely to significantly increase. This is because we’ll be pulling in all content stored on the community (including content from your previous vendor), rather than just the content that we recorded the events for since you started with inSided.

Example scenarios to explain the change


Here are some example scenarios to explain the concept behind the change:

Scenario: trashed topic/reply.

  • After the change, if a topic or reply is trashed, the principle is that it will no longer be reflected in the dashboard data.

  • If you trash a topic, then the topic counter will go down. It won’t be reflected in metrics such as the average response time.

  • The same applies to replies.

Scenario: question converted to conversation

  • After the change, if a topic is converted to a different content type, this will be reflected when using the ‘Content Type’ filter and in widgets like ‘Created topic types’ on the content dashboard.

  • E.g. converting a question to a conversation will decrease the question counter, and increase the conversation counter.

Scenario: topic moved to a different category

  • After the change, if a topic’s category is changed, this will now be reflected in the dashboards.

  • This will be most noticeable when using the ‘Popular categories’ widget and when using category as a filter.

Scenario: conversation converted to a reply of another topic (and vice versa - if a reply is promoted to a new topic)

  • After the change, if you convert e.g. a question to become the reply of an article, the question counter will go down, and reply counters will go up.

Scenario: you migrated from another vendor.

  • After the change, some metrics will increase if you filter over a certain time period. E.g. the total # topics for all time will increase, since it’ll also include migrated content.

  • Some data will not be accessible (e.g. checking how many likes a topic got over a certain period on the popular topics details page), since we don’t have the events data from your previous vendor.

We believe this change will make the dashboards much more intuitive and give you more reliable and verifiable insights. 

Please let us know if you have any feedback or questions!

 


1 reply

Userlevel 7
Badge +1

Update:

  • We will also produce a migration guide to help you understand the differences between the old and the new way of processing data in order to equip you to explain the changes in data to others in your company.
  • Since the upcoming change will also affect historical data, you’ll also be able to take a look at stats from previous months (giving you a consistent point of comparison, rather than just comparing to data which was processed in the old way).

Reply