/
Peppa CRM

Peppa CRM

Peppa CRM is a SaaS vendor specializing in sales and marketing automation, helping enterprises across all industries improve lead capture and sales process automation. In this example, we explore how Peppa CRM is aiming to boost its revenue growth by adopting usage-based pricing.

Peppa CRM currently faces several challenges, including:

  • Difficulty growing revenue from existing accounts

  • Lack of billing automation and poor data quality

  • An inflexible billing platform and large data volumes

  • Limited information sharing across departments

This example demonstrates a batch stream where funnel events are received from multiple sources. The data is validated, deduplicated, and enriched. Events from different systems are correlated and harmonized, while advanced session aggregation enables tracking of both overall and detailed (drill-down) metrics.

The stream highlights how Usage Engine enables Peppa CRM to:

  • Correlate data from multiple systems, even when they use different user or account ID formats, into unified golden record session objects using the Script aggregator function.

  • Produce a normalized data stream suitable for both billing and analytics

The primary value is Billing. Additional benefits include:

  • Analytics: Detailed breakdowns of usage by funnel event type and microservice ID

  • Data sync reconciliation: Alerts for accounts generating unrecognized events, along with custom audit events for improved data quality

Stream breakdown and functions used

Part 1: Collecting usage data from multiple sources

  • Trigger 1 & Trigger 2 (Count): Triggers the stream to run as many times as specified in the configuration. 

  • Core Sources & CPQ Sources (Script): Collecting customer lifecycle journey events or funnel events

Part 2: Validation of data

  • Validate Core events & CPQ events (Validate): Validating the data and filtering out invalid records

Part 3: Enriching data from CRM/CPQ systems

  • Enrich Core Accounts & CPQ Accounts, Enrich Core Funnel events & CPQ Funnel events (Script): Enrich the simulated data from Core & CPQ systems

Part 4: Deduplicating events

  • Deduplicate Core & CPQ events (Deduplicate): Removing duplicated records received from Core & CPQ systems

Part 5: Reconciliation

  • Account not found (Validate): Detecting incoming records that don't have an account ID registered in our CRM

  • Sum events per account (Data aggregator): Aggregating the events for unprovisioned accounts

  • Map for reconciliation (Field Organizer): Formatting and renaming data fields for reconciliation

  • Audit unprovisioned (Script): Generating a custom audit event for unprovisioned accounts

  • To reconciliation (No Operation): Pushing data for reconciliation

Part 6: Aggregation of events per account

  • Correlate and sum (Script aggregator): Aggregate the total number of events per account, but also differentiated by event type and source service ID

Part 7: Mapping for billing & analytics

  • Map billable items (Field Organizer): Formatting and renaming aggregated data for billing

  • Map funnel analytics (Field Organizer): Formatting and renaming aggregated funnel event(s) data for analytics

  • Map service analytics (Field Organizer): Formatting and renaming aggregated service data for analytics

  • To Billing (No Operation): Pushing data to billing systems

  • To analytics (No Operation): Pushing data to analytics