CBSplit CMS Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Why backend data is invisible to most tools ======

===== The frontend bias =====

Most analytics and optimization tools are built from a frontend perspective.

They see what happens in the browser.
They react to clicks and page loads.
They depend on scripts and pixels.

This creates a dangerous illusion.

That what you can see is all that matters.

CBSplit was built to operate where this illusion breaks.

===== Backend systems do not speak JavaScript =====

Backend systems communicate differently.

They rely on:  
  * Server-to-server callbacks
  * Asynchronous webhooks
  * Internal state machines
  * Delayed confirmations

These events do not pass through the browser.

As a result, frontend tools never see them.

===== Money moves on the backend =====

Critical revenue events happen after the frontend is gone.

Examples include:  
  * Payment authorization and capture
  * Retry attempts and fallback logic
  * Partial approvals
  * Refund processing
  * Chargeback resolution
  * Subscription rebills

Frontend tools stop observing long before these outcomes occur.

CBSplit starts here.

===== Timing breaks visibility =====

Backend data often arrives:  
  * Minutes later
  * Hours later
  * Days later
  * Out of sequence

Frontend tools expect immediate events tied to a session.

Backend truth ignores sessions entirely.

CBSplit is designed to tolerate delayed and unordered data.

===== Security and compliance block access =====

Backend systems are protected by design.

They enforce:  
  * PCI compliance
  * Access control
  * Limited external exposure
  * Audit constraints

For good reason, they do not allow arbitrary scripts or pixels.

Most tools cannot legally or safely operate at this layer.

CBSplit respects these boundaries and integrates correctly.

===== Backend data is fragmented across systems =====

Revenue data rarely lives in one place.

It is spread across:  
  * Checkout platforms
  * Payment processors
  * Subscription engines
  * Support systems

Frontend tools expect a single stream.

Backend reality is distributed.

CBSplit reconciles data across systems instead of flattening it.

===== Why most tools avoid backend truth =====

Backend data is avoided because:  
  * It is complex
  * It is delayed
  * It requires reconciliation
  * It breaks real-time dashboards

Most tools choose simplicity over truth.

CBSplit chooses truth over convenience.

===== Outcome visibility requires backend ownership =====

To understand outcomes, a system must:  
  * Track orders beyond the browser
  * Wait for financial resolution
  * Connect retries, refunds, and rebills
  * Accept incomplete data temporarily

Frontend-only tools cannot do this reliably.

CBSplit was built for backend ownership.