dario-liberman commented on issue #10866:
URL: https://github.com/apache/pinot/issues/10866#issuecomment-1583319291

   > I am not sure what the following means. 
   
   It means any temporal order will be accepted as converted.
   
   For a funnel measuring conversion of A->B->C
   1. we will count users as entering the funnel if they performed A,  
   2. converted to step 2 whenever they performed A and B, 
   3. and converted fully whenever they performed A and B and C. 
   
   A user who only performed A and C, or who performed B and C but not A, would 
not count as converted. 
   However, we will not require a strict temporal order between the events, so 
if we registered events with this temporal sequence: A,C,B - then the user 
would still count as converted as the user performed all the steps in the 
funnel.
   
   What I was saying is that in many real-life systems it happens that clocks 
are not synchronised, specially if having multiple sources (eg. mobile and 
backend events), so the simplification of counting in any order can also be a 
plus. 
   I was also pointing out that in most real-life scenarios there is no way to 
do C without doing B, for example there is no way to complete a checkout 
without starting a checkout in the firsts place, or without adding first an 
item to the cart.
   
   > Can you give an example or is this idea from some well known source (then 
can you add a reference to it?)
   
   Many funnel analytics solutions support "any order" conversion criteria. For 
example:
   - [Mixpanel Any 
Order](https://docs.mixpanel.com/docs/analysis/reports/funnels#ordering)
   - [Amplitude Any 
Order](https://help.amplitude.com/hc/en-us/articles/360052745632#h_6b432e9f-a491-439e-a2c6-005bc16bc6f6)
   
   I believe we can expand in future iterations on supporting temporal order 
constraints.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to