{"id":7820,"date":"2024-08-20T08:01:06","date_gmt":"2024-08-19T23:01:06","guid":{"rendered":"https:\/\/m365jp.net\/?p=7820"},"modified":"2024-08-20T08:05:50","modified_gmt":"2024-08-19T23:05:50","slug":"mc866446-viva-amplify-reports-displaying-count-and-percentage","status":"publish","type":"post","link":"https:\/\/m365jp.net\/index.php\/2024-08-20-mc866446-viva-amplify-reports-displaying-count-and-percentage","title":{"rendered":"MC866446 | Viva Amplify: Reports displaying count and percentage"},"content":{"rendered":"
\n
\n
\n\n\n\n
MC866446 | Viva Amplify: Reports displaying count and percentage<\/th>\n<\/tr>\n<\/tbody>\n<\/table>\n
\n\n\n\n\n\n\n\n
Classification<\/th>\nstayInformed<\/td>\n<\/tr>\n
Last Updated<\/th>\n08\/19\/2024 22:53:15<\/td>\n<\/tr>\n
Start Time<\/th>\n08\/19\/2024 22:53:07<\/td>\n<\/tr>\n
End Time<\/th>\n10\/31\/2024 07:00:00<\/td>\n<\/tr>\n
Message Content<\/th>\n\n

The default calculation of the audience size, both in the aggregate campaign report and for individual publication reports, has been updated to account for scenarios in which a publication has been sent to an endpoint that is open to all members of an organization. Such publishing scenarios often result in very large audiences, which in turn may cause the denominator in the percentage of Unique Viewers calculation to be confusing to users, even though correct.<\/p>\n

In cases where an audience is not explicitly defined and is simply \u201copen to all\u201d, the new Amplify reports will show the count rather than the percentage to provide the user a more comprehensible data point at first glance. <\/p>\n

Example: The total audience is calculated by summing up the members of the groups with rights to see the published item. The user count is obtained by adding the Microsoft Entra ID users with permissions to the published item. This can result in a very large audience which in turn may cause the percentage of unique viewers to appear a very small tenth or hundredth of a percentage point. If 2.4K or 7.3K people of the impacted organization have viewed the publication, a campaign owner or author might naturally expect to see a report indicating they have reached ~30% of their audience. But because the publication was shared beyond the impacted business group, as a general interest story to the company\u2019s intranet, the actual potential audience (everyone with permission to see the publication) is now 521,000 employees worldwide, resulting in the report displaying 0.5% unique viewers. This is not incorrect, but also not particularly meaningful.   <\/p>\n

This message is associated with Microsoft 365 Roadmap ID 407862<\/a><\/p>\n

<\/p>\n

[When this will happen:]<\/p>\n

General Availability (Worldwide): Gradually rolling out to everyone from 8\/28. <\/p>\n

[How this will affect your organization:] <\/p>\n

When one or more publications are published to an \u201call company audience\u201d the default view of any report will not show percentages. This will impact certain components on the report pages. <\/p>\n

<\/p>\n

In the image above you see that the Campaign Goals control is disabled as a result of not being able to calculate the percentage needed to measure the goal. You also see that the unique views are displayed as a number (2.4K), and each endpoint accounts for the \u201call company\u201d versus discrete audience scenarios. A percentage is displayed when possible and a number with an information icon when a denominator is not available. <\/p>\n

<\/p>\n

It is possible that in certain business scenarios the calculation across the entire available audience is precisely what the campaign members are interested in. In those scenarios you can open the \u201cEdit View\u201d button and toggle the \u201cInclude whole organization\u201d switch <\/p>\n

<\/p>\n

After the switch is toggled, the Campaign Goal is now visible as well as a percentage of unique viewers of the available target audience which is equal to all ADD users with permissions to the publication. <\/p>\n

<\/p>\n

[What you can do to prepare:]<\/p>\n

For admins: you might want to inform users and\/or update existing internal user training materials and documentation.<\/p>\n

<\/p>\n

<\/p>\n

Use reporting signals in Microsoft Viva Amplify to understand campaign performance<\/a> <\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

MC866446 | Viva Amplify: Reports displaying count and percentage Classification stayInformed Last Updated 08\/1 […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-7820","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/posts\/7820","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/comments?post=7820"}],"version-history":[{"count":0,"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/posts\/7820\/revisions"}],"wp:attachment":[{"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/media?parent=7820"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/categories?post=7820"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/tags?post=7820"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}