For data platform + CDP architects + customer-data leadership

Twelve channels emit behavioral signals. Heap and Mixpanel cover the first two cleanly. The other ten live in 200-franchisee systems nobody has connected.

Web visits and app sessions land in Heap or Mixpanel with auto-instrumentation. Email opens land in the ESP. SMS interactions land in the SMS provider. Push events land in the push channel. POS transactions land in 200 different franchisee POS instances. Foot traffic lands at the foot-traffic vendor. Booking events land in the booking system. Loyalty interactions land in the loyalty platform. Customer-service touchpoints land in the contact center. Ad clicks land in the paid-ad audience platforms. The behavioral-signal ingestion architecture that lands all 12 into one canonical customer record is operator-side wiring.

By Jay ChristopherMay 29, 202611 min read

What this gets you

Twelve-channel behavioral-signal coverage in one substrate — web + app + email + SMS + push + in-store walk-in + POS + booking + loyalty + customer service + foot-traffic + ad-click. The customer-graph Resolve axis stitches the streams to one identity; the customer-engagement-analytics surface reads from the unified substrate rather than 12 disconnected sources.
Per-channel adapter pattern for franchisee-owned systems — per-source adapters handle the long tail of franchisee-owned POS, booking, loyalty instances. The same adapter library extends to new franchisees and new source vendors without pipeline-core rewrites.
Per-event-type schema design tuned to downstream consumers — the cohort axis reads schema-A; the compute-LTV axis reads schema-B; the emit-change pipeline reads schema-C. Schema design at ingest satisfies every downstream consumer without per-consumer rewrites.
Per-jurisdiction PII tagging at ingest — GDPR + CCPA + HIPAA-PHI + cannabis-state + FERPA + PCI tags applied per-field per-event at ingest time. Downstream consumers receive events filtered to the PII they are authorized to see and the consent state covers.
Billions-of-events-per-month scaling— partition-aware ingest streams + sample- then-ingest at source for high-volume low-value signals + tiered storage hot-warm-cold split control cost growth sub-linearly with volume.

Twelve channels, twelve dashboards, twelve disconnected identities

A 200-location operator runs customer engagement across 12 channels. Web on operator-domain. Mobile app on iOS and Android. Email via the ESP. SMS via the SMS provider. Push notifications via the push channel. Walk-in foot traffic captured by the foot-traffic vendor at each location. POS transactions in 200 franchisee POS instances. Booking events in the booking system. Loyalty interactions in the loyalty platform. Customer-service touchpoints in the contact center. Paid-ad clicks in the Google + Meta + TikTok audience platforms. Review submissions on the review platforms.

The operator analytics team uses Heap for web and app behavioral analytics. Heap covers those two channels well with auto-instrumentation and dashboards. The team uses the ESP analytics for email metrics, the SMS-provider dashboard for SMS metrics, the GBP Insights dashboard for foot-traffic, the POS reports per franchisee for POS metrics, the booking-system reports for booking, the loyalty platform reports for loyalty, the contact-center dashboard for customer service, the ad-platform dashboards for paid traffic. Twelve channels, twelve dashboards.

The analytics team builds a master analytics spreadsheet that imports CSVs from each dashboard weekly. The customer behavioral journey across channels is approximated by manual joins on email address and customer ID where the systems share those fields. Where they do not share fields (the foot-traffic vendor sees a device ID that does not match the POS customer ID), the analytics team uses statistical proxies. The result is a 12-channel analytics view that approximates the actual customer journey to within 60-70 percent accuracy.

Behavioral-signal ingestion lands all 12 channels in one canonical substrate at the customer-graph agent. Per-channel adapters connect to each source. Per- event-type schema design tunes to downstream consumer requirements. Per-jurisdiction PII tagging applies at ingest. The Resolve axis (identity-resolution) stitches the streams to one identity using deterministic-plus-probabilistic resolution. The customer-engagement-analytics view reads from the unified substrate. The 12-dashboard manual-join workflow ends.

What is in market — and what each category leaves to you

The behavioral-analytics primitive is mature for web and app surfaces. The multi-channel ingestion across offline + multi-location channels at operator scale is architecture.

Product analytics — Heap, Mixpanel, Amplitude, Pendo, Userpilot, PostHog (open-source), Plausible, FullStory

Excellent at web and mobile app behavioral analytics with auto-instrumentation, funnel analysis, cohort analysis, and retention dashboards. The per-channel adapters for the offline-and-franchisee- owned signal sources (in-store POS, booking, loyalty, foot-traffic, contact center), the per-event-type schema design tuned to the customer-graph downstream consumers, and the integration with the broader 7-axis customer-graph pipeline are operator-side architecture above the product-analytics primitive.

Enterprise CDP — Adobe Experience Platform, Treasure Data, Tealium AudienceStream, Salesforce CDP, mParticle, Segment (Twilio), Lytics, BlueConic

Strong at multi-channel event-streaming infrastructure with pre-built source connectors and identity-graph storage. The per-franchisee-owned source-vendor diversity at 200-location scale, the per-jurisdiction PII policy at ingest, and the integration with the broader customer-graph 7-axis pipeline sit above the CDP layer.

Identity-resolution + customer-graph specialists — LiveRamp, Acxiom, Habu, Hightouch

Strong at third-party identity graphs that link identifiers across the broader consumer-data ecosystem. The first-party multi-channel ingestion that produces the operator-owned behavioral substrate the identity layer reads from is upstream of the third-party graph layer.

Open-source behavioral analytics + event streaming — PostHog, Snowplow, Jitsu, RudderStack, Apache Druid + Pinot

Capable of building the full multi-channel ingestion pipeline for operators with in-house data- engineering capacity. The per-channel adapter library, the per-event-type schema design, the per-jurisdiction PII tagging policy engine, and the integration with the 7-axis customer-graph pipeline are operator-side architecture above the open-source layer.

The 12-channel analytics spreadsheet the team rebuilds every Monday

The status quo at most multi-location operators below the enterprise tier. The analytics team imports CSVs from 12 dashboards weekly and manually joins on email address and customer ID where the systems share fields. Where they do not share fields the team uses statistical proxies. Result: 60-70 percent accuracy approximation of the actual customer journey.

The pipeline, end to end

Position in the 7-axis customer-graph pipeline. Ingest (this skill) + Resolve (identity-resolution) + Version (versioned-customer-history) + Compute-LTV (ltv-math-primitives) + Cohort (behavioral-cohort- computation) + Subscription-Ingest + Emit-Change (customer-change-event-emission). The Ingest axis is the substrate every other axis reads from.
Twelve-channel signal-source inventory. Web, mobile app (iOS + Android), email, SMS, push, walk-in foot traffic, POS, booking system, loyalty platform, customer-service touchpoints, paid-ad clicks, review submissions. Each channel has its own ingest pattern (SDK auto-instrumentation, API pull, webhook push, file-drop import, change-data-capture).
Per-channel adapter library. One versioned adapter per source vendor handles the vendor-specific quirks (auth + pagination + rate limits + schema variants + delivery cadence). The pipeline core stays vendor-agnostic. The same adapter library extends to new franchisees and new source vendors without pipeline-core rewrites.
Per-event-type schema design. Each event type lands in a canonical schema tuned to the downstream consumer set. The cohort axis reads event-type-A schema; the compute-LTV axis reads event-type-B schema; the emit-change axis reads event-type-C schema. Schema design at ingest avoids per-consumer rewrites later.
Per-jurisdiction PII tagging at ingest. Every event payload tags PII fields with the relevant regulatory regime (GDPR, CCPA, HIPAA-PHI, cannabis- state, FERPA, PCI). Consent state of the customer encoded on every event. PII policy engine shares substrate with the marketing-compliance cross-agent overlay.
Real-time vs batch routing per signal business value. Web and app events stream real-time to power next- best-action decisioning. Email open events stream near-real-time. POS transactions stream real-time for receipt-and-loyalty linkage. Lower-value clickstream samples at source and ingests at higher batch cadence.
Partition-aware ingest streams. Events partition on customer ID or session ID depending on the resolution stage. Partition-aware streams scale horizontally without disrupting per-customer event ordering. Per-customer event- ordering preservation matters for downstream cohort and LTV computation.
Sample-then-ingest at source for high-volume low-value signals. Clickstream events sample at the source (typically 10 percent) rather than ingest in full. Sample rate tunes per source per cycle against downstream analytics-accuracy impact. The sampling pattern produces sub-linear cost growth as volume scales.
Tiered storage hot-warm-cold split. Last 30 days hot in the real-time substrate for operational queries. 30-365 days warm in the analytical substrate for historical analytics. Beyond 365 days cold in the archive for compliance retention. Storage cost grows sub-linearly because the bulk of the volume lives in cheaper cold storage.
Handoff to the Resolve axis. Ingested events flow to the identity-resolution Resolve axis for cross-channel identity stitching. Resolve outputs flow to the version-history Archive axis and the cohort + compute-LTV axes. Emit-change broadcasts customer updates to downstream consumers.
Per-vertical regulatory handling. Healthcare locations under HIPAA cannot ingest cross- channel behavioral signals tied to PHI without explicit BAA-covered consent. Cannabis state-by-state rules apply at ingest. The per-jurisdiction PII tagging policy engine filters or quarantines events that fail the regulatory check.
Right-to-deletion propagation. When a customer exercises right-to-deletion under CCPA or GDPR or per-state law, the deletion event propagates through the customer-data-orchestration emit-change pipeline and tombstones affected identities in the version store. Ingest stream continues but skips the tombstoned identity.
Behavioral-signal-completeness measurement. Per-channel ingest health (events ingested per cycle vs expected baseline), per-event-type completeness (events with all required fields vs total), per- jurisdiction PII-tagging coverage, partition skew (events per partition distribution), end-to-end latency. Signal feeds adapter-tuning and schema- evolution per cycle.

Frequently asked

What is customer engagement analytics?

Customer engagement analytics captures behavioral signals across every channel a customer interacts with the operator brand and turns those signals into a single sequenced customer record. The category includes product analytics (Heap, Mixpanel, Amplitude, Pendo, Userpilot, PostHog, Plausible, FullStory) focused on web and app behavior, enterprise CDPs (Adobe Experience Platform, Treasure Data, Tealium AudienceStream, Salesforce CDP, mParticle, Segment, Lytics, BlueConic) that ingest event streams from multiple sources, and identity-resolution specialists (LiveRamp, Acxiom, Habu, Hightouch) that link cross-channel identifiers. The multi-channel ingestion architecture that lands all 12-plus signal streams into a single canonical customer-graph record at multi-location scale is operator-side architecture.

Why does single-channel behavioral analytics fail multi-location operators?

A multi-location operator generates customer engagement signals across 12-plus channels — web visits, mobile app sessions, email opens and clicks, SMS interactions, push notifications, in-store walk-in foot traffic, POS transactions, booking-system events, loyalty platform interactions, customer-service touchpoints, paid-ad clicks, and review submissions. Heap and Mixpanel cover the web and app subset well. The behavioral substrate that connects to the offline POS plus call-tracking plus walk-in foot-traffic plus loyalty signals and lands all of them in one canonical customer record is operator-side wiring. Single-channel analytics produces 12 disconnected datasets that the operator analytics team manually joins; the multi-channel ingestion architecture lands one unified substrate.

How is this different from Heap, Mixpanel, Amplitude, Pendo, Userpilot, FullStory, Segment, or mParticle?

Those platforms ship the behavioral-analytics or event-streaming primitive. Heap, Mixpanel, Amplitude, Pendo, Userpilot, FullStory are excellent at web and app event capture with auto-instrumentation and product-analytics dashboards. Segment, mParticle ship cross-channel event-streaming infrastructure. The per-channel adapter pattern that connects to the offline-and-multi-location-specific signal sources (in-store POS, call-tracking providers, foot-traffic-measurement vendors, per-banner loyalty platforms), the per-event-type schema design tuned to the customer-graph downstream consumers, the per-jurisdiction PII tagging at ingest, the real-time vs batch routing per signal business value, and the integration with the broader 7-axis customer-graph pipeline are operator-side architecture on top of the primitive.

How does this fit into the 7-axis customer-graph pipeline?

The customer-data-graph agent owns seven axes — Ingest (this skill — behavioral-signal-ingestion), Resolve (identity-resolution-deterministic-probabilistic), Version (versioned-customer-history), Compute-LTV (ltv-math-primitives), Cohort (behavioral-cohort-computation), Subscription-Ingest (subscription-billing-ingestion), and Emit-Change (customer-change-event-emission). The Ingest axis is the substrate every other axis reads from. Behavioral signals flow in, identity resolution links them to the customer graph, the versioned-history axis tracks state over time, the compute-LTV and cohort axes derive customer attributes, the emit-change axis broadcasts updates to downstream consumers. The seven axes together form the densest published agent surface in arc.

How do you handle billions of events per month at multi-location scale?

A 200-location operator with web + app + 10-plus additional channels generates 1-5 billion behavioral events per month. The ingestion architecture handles the volume through three patterns. First, partition-aware ingest streams that scale horizontally on the partition key (customer ID or session ID). Second, sample-then-ingest at the source for high-volume low-business-value signals (clickstream sampled at 10 percent rather than ingested in full). Third, tiered storage with hot-warm-cold split (last 30 days hot in the real-time substrate, 30-365 days warm in the analytical substrate, beyond 365 days cold in the archive). Cost grows sub-linearly with volume because the sample-then-ingest and tiered-storage patterns absorb the bulk of the volume growth.

How do you handle PII in behavioral signals under GDPR, CCPA, HIPAA, and cannabis-state law?

Per-jurisdiction PII tagging applies at ingest. Every event payload carries per-field regulatory tags (GDPR, CCPA, HIPAA-PHI, cannabis-state, FERPA, PCI). The consent-state of the customer is encoded on every event. Downstream consumers receive events filtered to the PII they are authorized to see and the consent state covers. Healthcare locations under HIPAA cannot ingest cross-channel behavioral signals tied to PHI without explicit BAA-covered consent. Right-to-deletion events propagate through the customer-data-orchestration emit-change pipeline and tombstone affected identities in the version store. The PII policy engine shares substrate with the broader marketing-compliance overlay.

Hire the agent that owns the ingest substrate

The customer-data-graph agent owns the 7-axis pipeline — Ingest + Resolve + Version + Compute-LTV + Cohort + Subscription-Ingest + Emit-Change — sitting on top of whichever product-analytics platform (Heap, Mixpanel, Amplitude, Pendo, Userpilot, PostHog, FullStory), enterprise CDP (Adobe Experience Platform, Treasure Data, Tealium AudienceStream, Salesforce CDP, Segment, mParticle), or open-source pipeline (PostHog, Snowplow, Jitsu, RudderStack, Druid + Pinot) you license downstream. Twelve-channel coverage, per- channel adapter library, per-event-type schema design, per-jurisdiction PII tagging, real-time vs batch routing, billions-of-events scaling.

Hire the customer-graph agent

We scope on the call and send a private checkout link after.