Start free trial

Integration · Adjust

Connect Adjust and read confidence in revenue, not just CVR.

Adjust measures what your installs did. ASOLOOP will read that signal — ARPU, install-to-paid rate, and lifespan — for revenue denomination: the workspace revenue band on the Teams-tier stakeholder dashboard is computed from connected AppsFlyer revenue today, so the Adjust revenue path is in progress, as is translating each experiment's CVR posterior into a revenue range with every assumption disclosed. You connect Adjust; ASOLOOP pulls cohort data from it. The connector is live today.

Start 7-day free trial What ASOLOOP pulls from it
ARPU+ lifespan
Revenue path in progress
Range
Revenue, not a point
Live
Connector status

What ASOLOOP pulls from it

Feeds: Revenue range

Adjust feeds the loop.

ASOLOOP consumes your Adjust attribution as a revenue-denomination source, read from the MMP your stack already runs — the inputs behind deciding whether an experiment is worth running in dollars, once the Adjust revenue path is wired.

  • ARPU, install-to-paid rate, and lifespan

    ASOLOOP will read these Adjust-derived inputs to ground the revenue model in your own attribution data rather than a category benchmark — the Adjust revenue path, and feeding those inputs into every confidence surface, is in progress.

  • Per-hypothesis revenue ranges — in progress

    Today the revenue band renders only on the Teams-tier stakeholder dashboard, as a workspace-level figure computed from connected AppsFlyer revenue. Translating each hypothesis's CVR posterior into a revenue range on the card — using your Adjust inputs once that revenue path is wired — is in progress. No point estimates — a fabricated figure would fail claim-safety.

  • Connector parity today, revenue parity next

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

Source, not surface

Adjust 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 Adjust.

What does ASOLOOP pull from Adjust?

Cohort data today; ARPU, install-to-paid rate, and lifespan are the signal that will denominate experiment confidence in revenue once the Adjust revenue path is wired. ASOLOOP reads Adjust; it doesn't run anything inside it.

Is the Adjust connector live?

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

Do I get a single revenue number?

No. Revenue never renders as a point estimate — the workspace band is a range bucket today, and per-experiment ranges will ship with their assumptions disclosed; a single fabricated figure would fail ASOLOOP's claim-safety contract.

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.