Activities are events automatically created by Bigdelta when important changes happen in your customer data. They capture moments like account creation, trial transitions, revenue movements, payment issues, and product usage changes. Activities power Moments triggers and end rules, and appear on account timelines to give you a full picture of what is happening with each customer.
Activities are generated automatically by Bigdelta’s automation engine when it detects relevant changes in your data. Each activity is linked to an account and includes a category label and contextual properties.
When a payment event is recorded with a failed status.
Payment Recovered
When a successful payment event is recorded and the most recent prior payment for the same account had failed. This indicates the customer recovered from a failed payment.
These activities track changes in product usage and are subject to a 7-day cooldown — if the same activity type was already created for the same record in the last 7 days, it is skipped. Each includes a change percentage property.
Activity
When it is created
Product Usage Dropped
When a record’s weekly event count decreased compared to the previous week.
Product Usage Increased
When a record’s weekly event count increased compared to the previous week.
These activities are created when a feature record’s adoption status changes. The feature name in the activity comes from the object’s display name. Only changes to Tried, Adopted, or Dropped trigger activities — the Never status is ignored, and no activity is created if the status did not actually change.
Activity
When it is created
Tried feature feature
When a feature’s adoption status changes to Tried.
Adopted feature feature
When a feature’s adoption status changes to Adopted.
Dropped feature feature
When a feature’s adoption status changes to Dropped.
These activities are created when entitlement records change. The entitlement name in each activity comes from the object’s display name. The behavior depends on the entitlement type.
When a feedback record is linked to an account. The feedback type value comes from the record’s feedback type property. One activity is created for each newly associated account.
Activities are the primary triggers for Moments. When configuring a moment’s start rule or end rules, you select from the available activity types. For example:
Start a moment when Trial Ending Soon fires, then end it successfully when New Business is recorded
Start a moment when Payment Failed fires, then end it successfully when Payment Recovered is recorded
Start a moment when Product Usage Dropped fires to proactively engage at-risk accounts
