Views and Interactions
Once a post is live, UmbSocial asks each network for its own figures about it: views, likes, reposts, replies and so on. They’re shown with the post under the network’s own names for them, so a Mastodon post has Boosts and Favourites while a Bluesky post has Reposts and Likes. UmbSocial shows only what the network gives. It never estimates a figure, and it never adds one network’s figures to another’s.
Where they’re shown
Section titled “Where they’re shown”- Published: open a post, and each channel it went out on has a row of figures under the post’s heading, with when they were last read (Updated 2 hours ago; hover over it for the full date and time).
- The History tab: a Views and interactions box above the history, for any post with a channel that has published.
- The calendar: hover over a published post and its tooltip has a line for each channel, with its first four figures (Bluesky: 12 likes, 3 reposts).
The queue doesn’t show them. A channel has figures only once the post has published on it, so a draft, a post waiting for its page, and a channel that failed or hasn’t gone out yet have none. Anyone who can read the post can see its figures.
A figure the network normally gives but didn’t send for this post shows as —. A name the network sends that isn’t one of its known figures is never shown.
Each network
Section titled “Each network”| Network | Figures (the network’s own name) | Edition | What the network needs, and the switch | Cost | First 48 hours | How long they’re kept |
|---|---|---|---|---|---|---|
| Bluesky | Likes (likeCount), Reposts (repostCount), Replies (replyCount), Quotes (quoteCount), Bookmarks (bookmarkCount) |
Free | Nothing. The figures are public and read without signing in. | Free | Hourly | As history, with the post |
| Mastodon | Favourites (favourites_count), Boosts (reblogs_count), Replies (replies_count), Quotes (quotes_count, Mastodon 4.5 and later) |
Free | Nothing. Public and unlisted posts are read without signing in. A channel that posts as private or direct isn’t read at all. | Free | Hourly | As history, with the post |
| X | Impressions (impression_count), Likes (like_count), Reposts (retweet_count), Replies (reply_count), Quotes (quote_count), Bookmarks (bookmark_count), Link clicks (url_link_clicks) and Profile clicks (user_profile_clicks). X gives the two kinds of click for 30 days only. |
Pro | No approval, but two switches, both off until you turn them on: Read views and interactions from X in UmbSocial’s settings, and the X provider’s Insights setting. See X. |
Paid: $0.005 for each post read, according to the X provider’s notes on X’s pricing. A post read again on the same UTC day isn’t charged again (X calls this a soft guarantee), and reads are capped at 3 million posts a month. | Daily | As history, with the post. Cleared if the post is deleted on X. |
Impressions (impressionCount), Unique impressions (uniqueImpressionsCount), Clicks (clickCount), Reactions (likeCount), Comments (commentCount), Reposts (shareCount), Engagement rate (engagement, a ratio shown as a percentage) |
Pro | The rw_organization_admin permission (Community Management API, approved by LinkedIn’s review), connected by an Administrator of the page; then the LinkedIn provider’s Insights setting. See LinkedIn. |
Free | Daily | One year from when they were read (LinkedIn’s terms) | |
Views (post_media_view), Reactions (reactions), Comments (comments), Shares (shares) |
Pro | Meta’s App Review for read_insights, pages_read_engagement and pages_read_user_content, on the Page token; then the Meta provider’s Insights setting, shared with Instagram. See Facebook and Instagram. |
Free | Hourly | Until the channel is removed or its connection deleted | |
Views (views), Reach (reach), Likes (likes), Comments (comments), Shares (shares), Saves (saved), Reposts (reposts) |
Pro | Meta’s App Review for instagram_manage_insights (with instagram_basic, and ads_management and ads_read if you have a Business Manager role on the Page) and pages_read_engagement; then the Meta provider’s Insights setting. |
Free | Every 6 hours (Instagram’s figures can lag by up to 48 hours) | Until the channel is removed or its connection deleted | |
| Threads | Views (views), Likes (likes), Replies (replies), Reposts (reposts), Quotes (quotes), Shares (shares), for the first post of a thread only |
Pro | Meta’s App Review for threads_manage_insights (business apps only); then the Threads provider’s Insights setting. See Threads. |
Free | Hourly | Until the channel is removed or its connection deleted |
Impressions (impression), Saves (save), Pin clicks (pin_click), Outbound clicks (clickthrough), Reactions (reaction), Comments (comment) |
Pro | Nothing new: the connection’s pins:read and boards:read. |
Free, but each Pin is one request, and an app on Pinterest’s Trial tier has 1,000 requests a day in all | Daily | Until the channel is removed or its connection deleted. Never kept as a trend. | |
| Google Business Profile | None. UmbSocial reads no figures for Google Business Profile updates, and shows Not available on Google Business Profile. | — | — | — | — | — |
On the free edition, Bluesky’s and Mastodon’s figures are shown and the other networks’ channels say Views and interactions from X come with UmbSocial Pro (or whichever network it is). Their figures aren’t read and no values are sent.
The permissions, limits and costs above are what each provider package documents (see each provider’s README). The networks change them, so check the network’s own documentation before you apply for a review or switch on paid reads.
How often they’re read
Section titled “How often they’re read”Each published post is read on its own timetable, counted from when it went out:
| Age of the post | Read |
|---|---|
| First 48 hours | Hourly; every 6 hours for Instagram; daily for X, LinkedIn and Pinterest (paid, rate-limited, or not updated in real time) |
| Up to 30 days | Daily |
| Up to 90 days | Weekly, with a last read at 90 days exactly |
| After 90 days | Never again: the last figures stay |
So the first figures appear about an hour after a post goes out (six hours on Instagram, a day on X, LinkedIn and Pinterest).
UmbSocial looks for posts that are due every 15 minutes (UmbSocial:MetricsInterval, see Configuration) and sends each channel’s due posts, up to 100 at a time, to that channel’s views-and-interactions automation in Umbraco Automate (see Automate integration).
A channel’s posts aren’t read while:
- publishing is switched off on this environment, so a staging copy of the live site doesn’t read the live accounts either;
- the channel is disabled, removed, or beyond the free edition’s 3 channels;
- the network comes with Pro and UmbSocial isn’t licensed;
- it is X, and Read views and interactions from X is off.
While publishing is off nothing is read, and posts that came due are read once it’s on again. In the other cases, UmbSocial checks those posts again once a day. When figures can’t be read (a permission is missing, a switch is off, the network refused), UmbSocial asks again at most once a day, whatever the network’s own timetable. A post the network says is gone, or that it has no figures for at all (an Instagram album, a Threads repost, a Pin Pinterest keeps no figures for), isn’t asked about again.
UmbSocial keeps the figures only for a post it has the network’s own id for. A post published by an earlier version of UmbSocial, which didn’t record that id, says Not available for this post. Only posts published in the last 90 days are read at all.
What each message means
Section titled “What each message means”| Message | Why |
|---|---|
| Waiting for the first figures | The post hasn’t been read yet. |
| Reconnect (channel) to allow insights | The connection lacks a permission the read needs, or the network refused the connection’s sign-in. Reconnect it. People who can manage settings get a link to the channel. |
| Insights for (network) need the network’s approval | The provider’s Insights setting is off (LinkedIn, Facebook, Instagram, Threads). See Turning on insights after app review. |
| Reads from X are paid, and they’re switched off in the X provider’s settings | UmbSocial’s X switch is on but the X provider’s Insights setting isn’t. |
| Switched off in Settings | UmbSocial’s Read views and interactions from X is off. The figures read before it was switched off are still shown, with their date. |
| Not a public post, so Mastodon doesn’t share its figures | The channel’s visibility is private or direct. Mastodon shares figures only for public and unlisted posts, so UmbSocial doesn’t ask for them. Change the channel’s visibility to see figures for the posts it publishes from then on. |
| This Mastodon server doesn’t share figures without signing in | The Mastodon server requires signing in to read a post (Mastodon calls this authorized fetch, or secure mode). UmbSocial reads Mastodon without signing in, because the connection only has permission to post, so reconnecting doesn’t help. |
| Post removed on (network) | The network no longer has the post. |
| Removed after a year, under LinkedIn’s terms | LinkedIn’s figures are kept for one year. |
| Not available for this post | The network has no figures for this post, refused or redirected the read, or answered with none of its figures; or UmbSocial has no id for the post on the network. |
| Update the (network) provider to see views and interactions | The network’s provider package is installed, but in a version without the action that reads figures. |
| Views and interactions from (network) come with UmbSocial Pro | See Editions and licensing. |
| Not available on (network) | The network gives no figures UmbSocial shows (Google Business Profile, or a network you added). As the tooltip on a —, it means the network didn’t send that one figure. |
Clicks: ours and the network’s
Section titled “Clicks: ours and the network’s”Two different things are called clicks, and UmbSocial keeps them apart.
- The network’s own clicks are counted by the network on its own site or app: X’s Link clicks and Profile clicks, LinkedIn’s Clicks, Pinterest’s Pin clicks and Outbound clicks. Each network decides what counts. LinkedIn’s Clicks count clicks anywhere on the post, for example, and X stops giving its clicks after 30 days.
- UmbSocial’s clicks (Pro) are counted by your own site, each time someone opens one of the post’s short links, wherever the link was opened: from the post, from a copy pasted elsewhere, or by a chat app fetching a preview. They are shown as Link clicks (UmbSocial).
They measure different things in different places, so the numbers differ, and UmbSocial never adds them together or puts one in place of the other. Where a channel shows the network’s own clicks, a note says so.
Turning on insights after app review
Section titled “Turning on insights after app review”Bluesky, Mastodon and Pinterest need nothing turned on. For the others, the network has to approve your app first (except X), and then a setting in the network’s provider package for Umbraco Automate turns the reads on. Only the value true turns a provider’s setting on; anything else, or no value, leaves it off. While it’s off, the provider sends nothing to the network and UmbSocial shows the message for it.
The settings are under Umbraco:Automate:Providers in the site’s configuration, for example in appsettings.json:
{ "Umbraco": { "Automate": { "Providers": { "LinkedIn": { "Insights": true } } } }}or as an environment variable: Umbraco__Automate__Providers__LinkedIn__Insights=true.
Once a network’s reads are on, UmbSocial asks for that channel’s figures again within a day. To have it ask straight away, save the channel in Settings › UmbSocial › Connections, or reconnect (save) its connection in Automate: either one asks again at once for the channel’s posts from the last 90 days that were waiting on a permission, a switch or a refusal.
- Ask LinkedIn for the
rw_organization_adminpermission. It’s part of the Community Management API, which you already need to post. The Standard tier review asks for a screencast of each use you request: include Page Analytics showing how posts perform. - Once it’s approved, set
Umbraco:Automate:Providers:LinkedIn:Insightstotrue. - Re-authorise the channel’s connection in Automate, signed in as an Administrator of the page. Turning the setting on adds the permission to what the connection asks for, and until it’s re-authorised LinkedIn refuses and the channel says Reconnect … to allow insights.
LinkedIn’s figures are organic only, and LinkedIn leaves out a post nobody has seen or acted on: UmbSocial then shows zeroes. A deleted LinkedIn post can’t be told apart from that, so it shows zeroes too rather than Post removed.
Facebook and Instagram
Section titled “Facebook and Instagram”- Ask Meta’s App Review for the permissions in the table. Each needs a screencast of the figures shown in your site, and Advanced Access needs Business Verification.
- Once they’re approved, set
Umbraco:Automate:Providers:Meta:Insightstotrue. The one setting covers both networks. - Generate a new Page token with the permissions and paste it into the connection. A Page token carries what was granted when it was made. While the setting is on, the connection’s Validate lists any of the permissions the token lacks, as a warning.
If Facebook’s views come back empty, Meta has left out read_insights, and the channel says Reconnect … to allow insights.
Threads
Section titled “Threads”- Add
threads_manage_insightsto your app’s use case and get it approved by Meta’s App Review (business apps only, with a screencast of the figures in your site). - Set
Umbraco:Automate:Providers:Threads:Insightstotrue. - Re-authorise the channel’s connection in Automate. A connection authorised before the setting was on doesn’t have the permission.
Threads counts the first post of a thread only, and Meta marks views and shares as still in development.
X needs no review, but every read is paid (see the table), so it takes both switches:
- Set
Umbraco:Automate:Providers:Twitter:Insightstotrue. - In Settings › UmbSocial › Schedule & writing, switch on Read views and interactions from X in the Views and interactions box, and save. The box is there while UmbSocial is licensed, for people who can manage settings.
There’s nothing to reconnect: the connection’s existing permissions read your own posts. With UmbSocial’s switch off, UmbSocial doesn’t run X’s reads at all. With the provider’s off, they run but send nothing to X.
How long figures are kept
Section titled “How long figures are kept”Each network’s terms set how long UmbSocial may keep its figures:
- LinkedIn: one year from when they were read. They are then cleared, and the channel says Removed after a year, under LinkedIn’s terms.
- Pinterest, Facebook, Instagram and Threads: deleted when the channel is removed or its Automate connection is deleted. Meta’s terms say to delete them when they’re no longer needed, and Pinterest’s on disconnecting.
- X: cleared when X reports the post deleted.
- Bluesky, Mastodon and X, and LinkedIn within its year: kept as history, with the post. Removing a channel or deleting its connection doesn’t delete them.
Removing a channel or deleting a connection deletes the figures it should at once, and the year’s limit is applied every 15 minutes, with the reads. Both happen even where publishing is switched off, and whatever the licence. Deleting a post deletes its figures.
Trends (UmbSocial Pro)
Section titled “Trends (UmbSocial Pro)”With UmbSocial Pro licensed, each reading is kept, so you can see how a post did over time. Beside a channel’s figures, in Published and on the History tab, a small line chart shows the network’s headline figure over time (Impressions over time), with its first and latest readings as text. The headline figure is the first in the network’s order, as in the table, that has been read at least twice. The calendar doesn’t show trends.
- A reading is kept only when the network gave figures. Pinterest’s are never kept as a trend.
- After 48 hours, only a post’s last reading of each day (UTC) is kept. This is done hourly, while the readings are 48 to 96 hours old.
- LinkedIn’s readings are kept for one year and Facebook’s, Instagram’s and Threads’ for 90 days. Facebook’s, Instagram’s and Threads’ also go when the channel is removed or its connection deleted, and X’s when the post is deleted on X.
- A post’s readings go when the post is deleted or its history is sealed.
- A trend shows the latest 500 readings.
While UmbSocial isn’t licensed, no new readings are kept and trends aren’t shown. The clean-up above still runs.
What happens when history is sealed
Section titled “What happens when history is sealed”On the free edition, a post’s history is sealed once it’s 90 days old.
- The post’s last figures for each channel go into the sealed, encrypted copy of the post, with when they were read, and UmbSocial’s readable copy is deleted. Like the rest of the post, they can’t be read until a licence restores it.
- LinkedIn: figures read more than a year before the post is sealed aren’t kept: the sealed copy says only that they were removed under LinkedIn’s terms.
- Pinterest: the figures themselves aren’t kept, because Pinterest’s must be deleted on disconnecting and a sealed copy can’t be changed. The sealed copy keeps only the state and when it was read.
- Pro’s trend readings for the post are deleted.
When UmbSocial Pro restores a sealed post:
- the last figures come back as they were sealed, and they’re never read again (the post is past its 90 days);
- Pinterest’s come back without figures, since the sealed copy kept only the state: the channel says Not available for this post;
- LinkedIn’s figures that have passed a year by then don’t come back: the channel says Removed after a year, under LinkedIn’s terms;
- Pinterest’s, Facebook’s, Instagram’s and Threads’ figures don’t come back if the channel has been removed;
- the trend doesn’t come back.
Sealing only happens on the free edition, which doesn’t read the Pro networks, so in practice the Pro networks’ figures are sealed only after a licence has lapsed.
For developers
Section titled “For developers”- Each channel reads its figures through a second managed automation in Umbraco Automate: see Automate integration.
- A network you add can have figures too.
SocialTargetMetricsRecordedNotification(inUmbSocial.Core.Notifications) is published once for each channel of a post whose figures were just recorded, with the target’s id, the channel, the network, the state, the figures under the network’s own names, and when they were read.- The
umbSocialTargetMetricsDetailextension type adds your own element beside a channel’s figures: see Backoffice extensions. POST metricsin the management API reads the figures for a page of posts.