In my previous posts, we built a serverless pipeline that captures Sitecore publishing lifecycle telemetry and handles asset state changes via an Azure Function middleware layer. The final step of our infrastructure calculates deltas on the fly and saves the active tracking footprint directly into a secured, custom JSON property (UsageTracking) on the M.Asset schema…

In my previous post, we looked at how to extend a Sitecore XP implementation to capture granular publishing events and fire off non-blocking telemetry signals. By adopting a fire-and-forget approach, we ensured that the CMS remains fast and unaffected by any potential downstream network latency. But once those publishing signals leave Sitecore, the real heavy…

In my previous post, I introduced a cloud-native architectural concept to track Sitecore asset usage within Content Hub in real time. The strategy is straightforward: rather than pulling data from Sitecore via heavy, on-demand crawls, we want the CMS to actively push usage signals to an external middleware layer the moment content goes live. However,…

Sitecore Content Hub does not provide built-in functionality to track asset usage in the Sitecore CMS. When using the Content Hub CDN to serve images directly to a Sitecore XP website, this creates the risk of deleting assets that are still in use, resulting in broken images. And as a result, content editors become hesitant…