Hi everyone! To simplify our experiment settings, we have decided to use the custom SQL Filter feature to see results only from users exposed to the new feature. Do you know if there is any downside to this process, and if so, what would you suggest instead? Thanks in advance!

I'm not really sure why you want to do this. Is it a feature flag, or are you serving the variation in another way? If it's specifically that they've seen the feature would mean (in my mind) that it would only be users in the variation? 😅 If you want to only have users that are applicable to see the new feature, then the feature evaluation would handle it, meaning that you don't need to do any extra SQL query. Or is it a scenario where the change is for example further down on the page and you want to ensure that the users scrolled down?

You can use the activation metric for exactly this purpose - it will filter users to just those who have that other metric event

We encountered an issue where we fire experiment event for users who are not actually exposed to the feature. Therefore a simpler solution would be to limit the results by the SQL filter using the assignment query values and include only results from those users. @fresh-football-47124 the activation metric can be built on top of a

page_view

event with certain properties? Or has it to be an numeric value? Thanks for the help!