Thanks Otto for responding.

We have suggested to go with a View or to write SQL query using "fromJSON" functions from their end when reporting.

I strongly agree with you Otto, by adding location as a context key it creates different model rules. Our existing models already has location as its predictors from long time.

As part of the experimentation, business wants us to do a POC by creating a new instance with Location as new model identifier. The goal of this analysis is to select a list of Proposition-location combinations where the location level ADMs could potentially exert great positive impact on the outcome rate.

We are doing this POC with few propositions which have high volume of interactions & positive response and active at multiple locations. The goal here is to choose propositions of which the corresponding channel level ADMs perform well at channel level but under-perform at location level. We believe such propositions will benefit the most from the location level ADMs because

•Proposition performance are more likely to vary significantly between locations for these types of propositions;

•Location-specific ADM models could better predict the proposition performance at each location level.