Package: eventchain
eventchainWhat is an event chain ?Anevent chainis basically like a series of dominoes, where
knocking over the first one triggers the next one, and so on. In
processes or systems, an “event” is something that happens—a trigger, an
action, a message, etc. Once this first event occurs, it sets off a
chain reaction of other events.Imagine you’re at home and your doorbell rings. That’s the first event.
The ringing doorbell could trigger a series of other events:Your dog starts barking because of the doorbell.You get up from your chair to see who it is.You open the door and greet your friend.You invite your friend inside.You both sit down and start talking.Each of these actions is an event, and they’re all connected. The
doorbell ringing set off a “chain” of events, one leading to the next.In business or computer systems, understanding event chains can be
crucial for analyzing how actions and reactions are interconnected.
Knowing how one event affects the next helps you design better
processes, make systems more efficient, or find out where things might
go wrong.InstallpipinstalleventchainHow to useFill me in please! Don’t forget code examples:importpandasaspdfromeventchain.coreimport*Building a new event chain is super simple:You create a newEventChainobject with the following parameters:chain=EventChain(df1=shoppingcard,df2=purchases,user_col="user_id",timestamp_col="date",suffix=["added_to_shoppingcard","purchased"])Once done you have access to all event chains calculated for you.As an example let’s have a look at the event chainfirst_before_firstwhich can be interpreted in our example as
the first date a user added an item to their shopping card before the
first date they purchased.chain.first_before_first<style scoped>
    .dataframe tbody tr th:only-of-type {
        vertical-align: middle;
    }

    .dataframe tbody tr th {
        vertical-align: top;
    }

    .dataframe thead th {
        text-align: right;
    }
</style>user_iddate_added_to_shoppingcarddate_purchasedgap012018-07-012018-07-021 days352018-07-102018-07-111 days462018-07-072018-07-103 days582018-08-012018-08-021 daysIn addition (and for illustration purposes ignoring the fact that a
shopping cart would have its own ID), we can now check the last date a
user created a shopping cart before their first purchase.chain.last_before_first<style scoped>
    .dataframe tbody tr th:only-of-type {
        vertical-align: middle;
    }

    .dataframe tbody tr th {
        vertical-align: top;
    }

    .dataframe thead th {
        text-align: right;
    }
</style>user_iddate_added_to_shoppingcarddate_purchasedgap012018-07-012018-07-021 days462018-07-082018-07-102 daysFor user_1 the first date and last date for shpping cart creation is the
same, however user_6 had two shopping carts created (here our
interpretation would be she dropped out one time).Please note that - in these first iterations of the package - not much
tooling has been added to do such comparisons in a convenient way, so
you would have to implement your own downstream analysis.Event Chain StatsThe first data frame is used to calculate some distribution statistics
of the gap betwenn event A (first time shopping card creation) and event
B (first time purchasing),the second is used as a baseline and to
calculate the percentage of occurrence of event A compared to event B.stats=get_stats(chain.first_before_first,chain.any_event_A,user_col="user_id",gap_column="gap")==================================================
Metric                         Value     
==================================================
no_events_of_interest          4         
all_events                     7         
pct                            57.14285714285714
mean_gap                       1.5       
median_gap                     1.0       
std_dev                        1.0       
min_gap                        1         
max_gap                        3         
25th_percentile                1.0       
50th_percentile                1.0       
75th_percentile                1.5       
skewness                       1.9999999999999998
kurtosis                       4.0       
conf_interval_lower            0.520018007729973
conf_interval_upper            2.479981992270027
==================================================Some areas where event chain analysis can be used:These easy to build event chains enables lots of ways to analyse your
data and to answer interesting questions about your processes or
customer behaviour.Time AnalyisCost AnalysisDependency MappingSensitivity AnalysisSimulation ModelsError Impact AssessmentSuccess MetricsUser Experience JourneyFeedback LoopsComparative Analysis