This message was deleted.

I know we have a project in the works to make this conversion window a bit more logical - @future-teacher-7046 should be able to explain what you’re seeing

The SQL is a little confusing. There could be a long sequence of events before the actual goal metric you care about. Viewed Experiment -> Activation Metric -> Denominator Metric -> Goal Metric. Each of those metrics have their own conversion windows. The conversion start/end columns are actually meant for the next metric in the sequence. So your example is looking at the Denominator Metric. The start/end columns are defining the valid range for the next metric, your Goal Metric. In other words, the Goal Metric must happen within 72 hours of the Denominator Metric.

I see, the logic gets quite complicated with those steps. Now I think I understand it. Basically, my denominator metrics is a binomial, using the same event timestamp than my goal metric. And my Activation Metric is the same as the Viewed Experiment (as I’m not setting any conversion delay). Therefore, what GrowthBook is actually doing is just calculating that the goal metric timestamp (which is the same as the denominator) falls within the 72h after the experiment event datetime. Is this reasoning correct? Thanks for the answer and sorry for the misunderstanding

yes, I think that sounds correct.