![](https://cdn.prod.website-files.com/65c0b8763c04cd15daa89ad3/65d87119e8c480a86b772549_65a7da2ce99e6fede2b395aa_Frequency-Based%2520Strategy%2520in%2520Bucket_V2-min.png)
Adding frequency-based strategy capabilities to the STARS configuration
We’ve just made the STARS configuration more customizable by adding frequency-based strategy capabilities. This lets you factor in the frequency of interactions for the Adopted criteria.
But wait, what is a frequency-based strategy?
It’s where you track feature usage frequency, not event count. Let’s say you deploy a new feature. You see that a company has logged 30 events with the feature over the past four weeks. They would be considered Adopted. However, if you look closer, those 30 events all took place on a single day. Then, the feature was never used again. In reality, they didn’t adopt the feature.
A frequency-based approach requires consistent interaction with a feature over a certain time period. For example, a company would need to use a feature on 10 separate days within a 4-week period to be considered as Adopted. This allows you to get real insights into feature adoption rates.
With the previous count-based strategy, companies were deemed Adopted once they had interacted with a feature a certain number of times (e.g. 5 times). Companies could reach this threshold when several company users each interacted with the feature a few times - without any of them truly adopting it. Before this change, the solution was to bump up the event count threshold.
With the new frequency-based strategy, you can define how many days (say 5) in a given period (say 4 weeks) the company needs to have interacted with the feature for them to be counted as Adopted.
![STARS configuration screen](https://cdn.prod.website-files.com/65c0b8763c04cd15daa89ad3/65d87119e8c480a86b772573_65a7da79288961a08ac79761_STARS%2520Configuration%2520Screen_V2-min.png)
Once Adopted, if the company stops fulfilling the criteria during your set period parameters (using our previous example, the past 4 weeks), they will be deemed as Churned from the feature.
Here’s an example:
![Feature-based frequency analytics](https://cdn.prod.website-files.com/65c0b8763c04cd15daa89ad3/65d87119e8c480a86b77256c_65a7bb1548cf741c8a897d5f_Frequency-Based%2520Sceenshot.png)
The frequency-based strategy is now the default on new features while all existing features have been automatically migrated.
Happy shipping!