Skip to content

Usage Data (Telemetry)

Once a day, UmbSocial sends an anonymous usage report to https://telemetry.umb.social. It tells us which versions are in use, which networks and features people rely on, and which networks’ posts fail most often, so we know what to fix and support first.

It is anonymous: it holds counts and version numbers, never your content, your domain or anything about your users. It is on by default, and one setting turns it off.

appsettings.json
"UmbSocial": {
"Telemetry": {
"Enabled": false
}
}

As an environment variable: UmbSocial__Telemetry__Enabled=false. Nothing is sent while it is off, and nothing about the site is stored for it.

This setting is UmbSocial’s own. It is separate from Umbraco’s telemetry setting (Settings › Telemetry in the backoffice): changing one doesn’t change the other, and UmbSocial’s report never goes to Umbraco.

Item Example Notes
Install id 3f2b1c4d-… A random id UmbSocial makes the first time it reports, kept in the site’s database. Not Umbraco’s site id.
Site hash 9c1e… (64 characters) A one-way hash of the install id and the site’s host name and port. It tells two sites apart when one was copied from the other’s database. Your domain can’t be recovered from it.
Versions UmbSocial, Umbraco, Umbraco Automate, .NET
Platform Linux, SqlServer The operating system and the database type.
Environment Production Production, Staging or Development. Any other environment name is sent as Other.
Edition licensed, development licence Whether the site is licensed, and whether it is a development licence. Never the licence key or its domains.
Publishing on or off Whether this environment sends posts (see Configuration).
Packages UmbSocial Pro 1.0.0 The names and versions of the UmbSocial packages installed. No other packages.
Counts see below Numbers only.

The counts:

  • Channels for each network: how many there are, how many are connected and switched on, and how many read views and interactions. A network added by a package is counted as custom, without its name.
  • Posts: how many are in each status (draft, scheduled, published and so on), and how many were made in the last 30 days by hand, with AI or by an automation.
  • Sends in the last 30 days for each network: how many were published, failed, or ended with an unknown outcome.
  • Features: how many posts are linked to a page or wait for their page, how many campaigns there are, how many people wrote posts in the last 30 days (a number, not who), and how many days ago the first post was made.
  • With UmbSocial Pro: how many templates, hashtag groups, tags, short links, posts with UTM tags, page opt-outs and posts made from pages there are.
  • With Umbraco Engage: how many landing pages, goals and markers there are.
  • The site’s domain or address. Like any web request, the report arrives from your server’s IP address, but the IP address isn’t saved with the report.
  • Umbraco’s site id.
  • Post text, links, images, channel names, campaign names, tags or anything else written in UmbSocial.
  • User names, email addresses or user ids.
  • Account details, connections, tokens or keys of any kind, including the licence key.
  • Once a day, starting about 5 minutes after the site starts. It waits until the site has served its first request, because the site hash needs the site’s address.
  • From one server only on a load-balanced site. It is one of Umbraco’s recurring background jobs, run on the server that runs scheduled work.
  • It never slows the site down or shows an error. If the service can’t be reached, the report is dropped and tried again the next day. The failure is only logged at Debug level.
  • Each report replaces the site’s previous one: the service keeps the latest report for each site, with the dates it was first and last seen.