We’ve made it easier for your team to stay on top of important customer activities - and track which administrators are taking action when it matters most.
What's New
Key customer actions such as Skip a Payment, Recurring Purchase Recovery, card updates, and fund changes are now captured in the customer_event table. With this data you can:
- Join customer_event data to administrator data in the Metrics Database.
- Track administrators who perform certain actions.
- Gain greater visibility and audit capability across the board.
Previously, recurring purchase events were stored only in the recurring_purchase_event table. By adding these to the customer_event table, data teams can identify who did what, when.
Clearer Tracking
The following events are now tracked:
- Card and Fund Changes:
- credit_card_removed
- credit_card_deleted
- card_added
- card_edited
- default_fund_changed
- customer_fund_updated
- Recurring Purchases:
- recurring_purchase_created
- recurring_purchase_activated
- recurring_purchase_paused
- recurring_purchase_timed_pause
- recurring_purchase_cancelled
- failed_recurring_purchase_processed
- recurring_purchase_payment_option_updated
- recurring_purchase_active_lottery_keys
Why It Matters
This update means your team can identify actions taken by administrators, supporting transparency and accountability. This also provides greater visibility on the quality of interventions for recurring purchase issues in order to minimise disruptions and provide greater tactical insight.