Page Comparison

...

Analytics: Breakdown of usage by funnel event type and by microservice ID.
Data sync reconciliation: Providing alerts about accounts generating events that don’t exist in the CRM and therefore cannot be processed correctly. This also generates custom audit events.

Stream Breakdown and Functions Used

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

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

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

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

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

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

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