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 CBSplit is not just another tracking pixel ======

===== The misconception =====

Many people assume CBSplit is just another tracking pixel.

Something that fires on page load.
Something that records a click.
Something that sends data to a dashboard.

That assumption is wrong.

CBSplit was never designed to be a pixel-first system.

It was designed to be a **revenue truth system**.

===== What a traditional tracking pixel actually does =====

A traditional tracking pixel typically:  
  * Fires on page load or click
  * Runs entirely in the browser
  * Depends on cookies or local storage
  * Measures surface-level events

Its primary job is attribution, not understanding.

It answers questions like:  
  * Which page was viewed
  * Which button was clicked
  * Which variation was shown

It does **not** understand what happened after money was involved.

===== Pixels break where money starts =====

The moment a user enters checkout:  
  * Domains change
  * Sessions fragment
  * Cookies get blocked
  * Browser state becomes unreliable

Payment systems introduce:  
  * Redirects
  * Server-to-server callbacks
  * Delayed confirmations
  * Retry flows
  * Partial failures

A pixel cannot reason about these events.

It only sees fragments.

===== CBSplit does not rely on browser truth =====

CBSplit is not anchored to the browser.

It does not assume the browser knows what really happened.

Instead, CBSplit is built around:  
  * Server-side events
  * Order-level identifiers
  * Postback-confirmed outcomes
  * Payment-system truth

If the browser lies, CBSplit waits.

If the payment retries, CBSplit tracks.

If the transaction resolves later, CBSplit reconciles.

A pixel cannot do this.

===== Pixels track actions. CBSplit tracks outcomes =====

A pixel is action-oriented.

CBSplit is outcome-oriented.

Pixels answer:  
  * Did the user click?

CBSplit answers:  
  * Did the payment succeed?
  * Did it retry?
  * Did it downgrade?
  * Did it convert to subscription?
  * Did it churn later?

CBSplit follows the lifecycle of revenue, not the moment of interaction.

===== CBSplit operates at system level, not page level =====

Tracking pixels live at page level.

They care about DOM, JavaScript, and UI state.

CBSplit lives at system level.

It cares about:  
  * Offer logic
  * Routing decisions
  * Checkout paths
  * Decline handling
  * Retry sequencing
  * Subscription behavior

This is why CBSplit integrates with checkout systems directly, not cosmetically.

===== Pixels decorate funnels. CBSplit controls them =====

Most tracking tools decorate an existing funnel.

They observe.
They record.
They report.

CBSplit actively participates in the funnel.

It can:  
  * Decide which offer a user sees
  * Route traffic based on prior outcomes
  * Adjust flows based on failure states
  * Learn from revenue, not clicks

CBSplit is part of the decision-making loop.

Pixels are not.

===== Why CBSplit looks different from analytics tools =====

If CBSplit feels heavier than a pixel, that is intentional.

Revenue systems are heavy.

They involve:  
  * Money
  * Risk
  * Compliance
  * Accountability

CBSplit accepts this complexity instead of hiding it behind charts.