morning, I wanted to check whether with the latest...
# give-feedback
w
morning, I wanted to check whether with the latest version there is a way to do 'all exposures' experiments? I see from the docs that this feature seems to have gone away, however we've got users at our org who would like the option to do this. Is there a workaround, or is this functionality not possible to reproduce?
h
Hi Matthew, there is not currently a way to do that kind of analysis. It was becoming complex to maintain and the performance of the query it requires does not scale well at all. There isn't a way to directly reproduce it, but I wonder if the Experiment Duration model would suffice for those users? The main difference is that if there is a gap between a users exposures that is not covered by a conversion window, the Experiment Duration will count conversions in that gap.
w
Thanks Luke, useful to understand where we're at with this type of functionality as well as the rationale. Out of interest is this to do with the queries generating very large tables as a result of the joins in the generated code? Just to check I understand, under the old 'All Exposures' functionality with say conversion window of 2 hours, event data would only be included for the timestamp of each exposure + 2 hours, so you could focus in on 2 hour windows immediately after the exposure. Under the new 'Experiment Duration' model, does it basically include all event data between first exposure and end of experiment/phase? So its not possible to focus in on those 2 hours windows as before? Thanks again
h
Under the new 'Experiment Duration' model, does it basically include all event data between first exposure and end of experiment/phase? So its not possible to focus in on those 2 hours windows as before?
Yes, that's correct. You can focus in on the first 2 hours after the first exposure only, but not after each exposure.
Out of interest is this to do with the queries generating very large tables as a result of the joins in the generated code?
Yeah, essentially you need to build non-overlapping conversion windows (e.g. if a user gets exposed at hour 1 and at hour 2, and you have a 2 hour conversion window, you need to build a window from hour 1 through to hour 3), and all the solutions to this are pretty expensive and work really poorly with large experiments.
w
OK good to understand. Yeah we'd certainly found that you could inadvertently produce some super big queries (if of interest we also saw that you could trip into large queries if you used an a high volume metric as the activation metric and also had some high volume metrics within your experiment)