Start free trial

Integration · Branch

Connect Branch for revenue confidence — and deterministic owned-channel routing.

Branch is deep-link plumbing and MMP attribution. ASOLOOP reads it two ways: it pulls revenue inputs to denominate confidence in a range, and it routes owned-channel experiments through Branch / OneLink identifiers so those installs assign deterministically. You connect Branch; ASOLOOP consumes it. Live today.

Start 7-day free trial What ASOLOOP pulls from it
Range
Revenue, not a point
OneLink
Deterministic routing
Live
Connector status

What ASOLOOP pulls from it

Feeds: Revenue range

Branch feeds the loop.

ASOLOOP uses Branch on two fronts: as a revenue-denomination source for confidence, and as the routing layer that makes owned-channel experiments deterministic — OneLink identifiers tag the traffic so install assignment isn't a guess.

  • Revenue inputs for confidence denomination

    ASOLOOP will read Branch-derived ARPU, install-to-paid rate, and lifespan for revenue denomination — the Branch revenue path is in progress: the workspace revenue band on the Teams-tier stakeholder dashboard is computed from connected AppsFlyer revenue today, and translating each hypothesis's CVR posterior into a revenue range on the card, with assumptions disclosed, is in progress too.

  • Deterministic owned-channel routing

    OneLink identifiers route owned-channel experiments at the per-variant deterministic precision tier — install assignment is deterministic via the Branch identifier, not modeled.

  • Connector parity today, revenue parity next

    Branch connects and syncs cohort data at the same precision as AppsFlyer, Adjust, and Firebase. Revenue denomination is AppsFlyer-derived today — the Branch revenue path is not yet wired. The deep-link routing is the Branch-specific bonus and is live.

Source, not surface

Branch is something ASOLOOP pulls signal from— not a place ASOLOOP runs experiments. ASOLOOP runs the loop on the stores and measures the paid surfaces; integrations like this one feed the brain behind those moves.

Common questions

Questions about Branch.

What does ASOLOOP pull from Branch?

Revenue inputs (ARPU, install-to-paid rate, lifespan) for confidence denomination, plus OneLink identifiers used to route owned-channel experiments deterministically. ASOLOOP reads and routes through Branch; it doesn't reconfigure it.

How does Branch help with routed experiments?

OneLink identifiers let owned-channel experiments fire at the per-variant deterministic tier — install assignment is deterministic via the Branch identifier rather than approximated.

Is the Branch connector live?

Yes — Branch is one of four live MMP connectors. Connect + cohort sync are at parity with AppsFlyer, Adjust, and Firebase; revenue inputs (ARPU, install-to-paid, lifespan) are AppsFlyer-derived today, so the Branch revenue path is not yet wired.

Other integrations

Other tools advise · ASOLOOP operates

Stop running ASO by hand.

Point ASOLOOP at your app, set your autonomy level, and read the receipts. Seven days, your apps, real experiments running on both stores.

Start 7-day free trial

Credit card required to start · Not billed during the trial · Cancel anytime

Your store credentials and your own AI-model keys — inspectable, revocable any time.