elog2cum

elog2inc

Event log, a <code>data.frame</code> with columns <code>cust</code> and
transaction time <code>t</code> or <code>date</code>.

elog

Only return every <code>by</code>-th count Defaults to 7, and thus
returns weekly numbers.

If TRUE, then the first transaction for each customer is being
counted as well

first

Aggregates an event log to either incremental or cumulative number of
transactions. If <code>first=TRUE</code> then the initial transactions of each
customer are included in the count as well.

Provides advanced statistical methods to describe and predict customers'
purchase behavior in a non-contractual setting. It uses historic transaction records to fit a
probabilistic model, which then allows to compute quantities of managerial interest on a cohort-
as well as on a customer level (Customer Lifetime Value, Customer Equity, P(alive), etc.). This
package complements the BTYD package by providing several additional buy-till-you-die models, that
have been published in the marketing literature, but whose implementation are complex and non-trivial.
These models are: NBD [Ehrenberg (1959) <doi:10.2307/2985810>], MBG/NBD [Batislam et al (2007)
<doi:10.1016/j.ijresmar.2006.12.005>], (M)BG/CNBD-k [Reutterer et al (2020)
<doi:10.1016/j.ijresmar.2020.09.002>], Pareto/NBD (HB) [Abe (2009) <doi:10.1287/mksc.1090.0502>]
and Pareto/GGG [Platzer and Reutterer (2016) <doi:10.1287/mksc.2015.0963>].

elog2cum: Convert Event Log to Transaction Counts

Description

Usage

Arguments

Value

Details

Examples