# How does Thales Sentinel collect and use product-usage data for licensing, product decisions, and customer lifecycle management?

Thales Sentinel doesn't just enforce licenses; it can also capture product usage data that feeds into billing accuracy, product decisions, and customer lifecycle workflows such as renewals or expansion. Turning raw usage events into something usable for those three different purposes (licensing enforcement, product analytics, and customer success) likely requires different aggregation, timing, and integration paths; we're trying to understand how Sentinel actually structures this data flow in practice, so if you've used Sentinel's usage data beyond basic enforcement, what worked for feeding it into product or customer-lifecycle decisions, and where did it fall short?

##### Post Metadata
- Posted at: 4 months ago
- Author title: Program Manager
- Net upvotes: 1


## Comments
### Comment 1

Sentinel can capture technical events related to licenses, entitlements, activations, devices, users, features, and product consumption. The event model depends on how the product is instrumented. Developers identify the events and metrics relevant to the commercial model or product experience, such as feature activation, session duration, transaction count, API calls, processing volume, or consumption of tokens and credits.
For usage-based licensing, the product records consumption events and associates them with the appropriate customer, entitlement, product, and feature. Depending on the deployment architecture, usage can be transmitted directly, aggregated by a local service, or temporarily stored in an offline environment and synchronized later.  In addition to generating usage data through Sentinel’s own license enforcement solutions, we can ingest usage streams from third-party instrumentation tools. This flexibility enables customers to take a holistic approach to usage tracking across the Sentinel monetization stack.

The implementation must account for issues such as duplicate events, interrupted connections, delayed reporting, clock differences, and reconciliation between local and centralized counters.
Usage data can also be analyzed independently of enforcement. For example, a product manager may want to determine whether a licensed feature is actively used even when that feature has no consumption limit. This can reveal adoption patterns, underused modules, common feature combinations, and differences between purchased capacity and actual usage.
The resulting mediated and metered data can be integrated with CRM, billing, customer-success, or analytics systems. Sales and customer-success teams can identify customers approaching contractual limits, accounts with low adoption, or opportunities to expand into additional capabilities.
From an engineering perspective, entitlement data describes what a customer is allowed to use, while usage data describes what the customer actually uses. Combining the two provides the technical foundation for consumption models, enforcement, adoption analysis, entitlement reconciliation, and lifecycle management


##### Comment Metadata
- Posted at: 4 months ago
- Author title: Program Manager




## Related Product
[Thales Sentinel Software Monetization Platform](https://www.g2.com/products/thales-sentinel-software-monetization-platform/reviews)

## Related Category
[Software Monetization Platform](https://www.g2.com/categories/software-monetization-platform)

## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: over 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: over 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: over 13 years ago
  - Comments: 4


