Track customer journeys throughout your SaaS about ksqldb-recipes HOT 2 CLOSED

@ybyzek two thoughts on this one:

• Minor obsevation, but just for clarity. The title says "your SaaS", however, the description seems to describe a web retailer as opposed to what I traditionally think of software as a service.
• I'm trying to understand the meaningful difference between this recipe idea and the existing https://confluentinc.github.io/ksqldb-recipes/customer-360/clickstream/ which has user information, clicks, sessions, and other seemingly similar concepts.

Maybe this could be described slightly differently to capture the ksqlDB behaviors we want to highlight that are different than the existing clickstream recipe?

from ksqldb-recipes.

@rspurgeon

I'm trying to understand the meaningful difference between this recipe idea and the existing https://confluentinc.github.io/ksqldb-recipes/customer-360/clickstream/ which has user information, clicks, sessions, and other seemingly similar concepts.

I made the same comment in the XLS to which @MichaelDrogalis response was "Yeah that seems fine. Let's keep the framing on the idea of a customer journey and actually collect the page history with collect_list, but the bulk of that seems fine." @MichaelDrogalis , please elaborate if you'd like, but my interpretation is that this new recipe should focus on a new use case of a customer journey of specific pages they visited (versus sessions, errors, etc as shown in clickstream) and should showcase the ksqlDB function collect_list

from ksqldb-recipes.