Hi! Is there a parameter for the conversion window similar to

'{{ startDate }}'

and

'{{ endDate }}'

? I am asking because for now, in use cases where conversion window should be infinity, the

'{{ endDate }}'

parameter gets filled by (

real end date taken from experiment configuration + conversion window

) and this leads to changing results after an experiment is stopped. Thus: 1. Having

'{{ conversionWindow }}'

parameter would allow to nicely edit metrics. 2. Also, it is not obvious that

'{{ endDate }}'

is actually experiment end date + conversion window 🙂 It gets clear after looking an rendered queries only.

Yeah, that makes sense. The original idea behind the

{{startDate}}

and

{{endDate}}

variables was for query optimization by decreasing the number of scanned rows. It was just meant as a rough filtering pass. It's clear now that it's useful for other things so we might rethink our approach a bit

Sounds good! There is a bit more I find confusing about

{{endDate}}

parameter: 1.

{{startDate}}

always corresponds to the start time of the experiment, very clear, very nice. Therefore, it is rational to assume that

{{endDate}}

corresponds to the end time of the experiment as defined in experiment configurations, but this is not the case as I understood; 2. Definition of

endDate

is different for stopped and running experiments although the parameter is the same: a. For running ones, it is `experiment end time + conversion window`; b. For stopped ones, it is

current_date + 2 days

. Can you please explain why 2 days? So, I am wondering whether it can be possible to explain this a bit better in documentation? Also, I think the name

endDate

might be misleading and maybe replacing it with

endDateAndConversionWindow

(for stopped experiments) together with

currentDatePlus2Days

(for running ones) would be more clear.