A23 Rummy: deep-link success needs a destination-level acceptance test

Head Digital's public A23 Rummy case identifies broken transitions between marketing and the app. The useful operating unit is the intended destination, not merely whether a link opens something.

What the public case establishes

AppsFlyer says Head Digital used OneLink, Smart Banners and Smart Scripts to improve contextual journeys for A23 Rummy, alongside attribution and conversion-value work. The source describes earlier journeys reaching generic app screens instead of relevant destinations. Its outcome statements cover multiple simultaneous changes. AppsFlyer case study.

This debrief analyses a public customer case published by a commercial supplier. It is not an original UA Ledger interview. The chronology below follows the supplier’s account; we did not inspect the advertiser’s dashboards or interview its staff.

The decision worth examining

A successful redirect can still fail the user's task. The app may open at the wrong screen, discard context during installation or route an existing player differently from a new one. A measurement event saying opened does not prove that the promised destination was reached. The acceptance test should follow the user-visible task through the entire allowed path.

Our proposed journey matrix separates installed and uninstalled states, supported operating systems, source placements and eligibility conditions. It records the expected destination and the fallback when that destination is unavailable. This is a test structure for authorised teams, not a recommendation to promote real-money gaming or a finding that the named app currently has these defects.

A usable next check

Create non-production test links with harmless parameters and exercise each supported journey. Capture the destination reached and whether the intended context survives, then reconcile that observation with the attributed event. Review failed cells before judging conversion performance. A correctly logged click followed by a generic landing screen is a product-flow failure even if attribution itself works.

Download the populated case worksheet. Its control, variant and decision rules are a proposed experiment, not an account of results already measured. Keep the source URL with the worksheet when circulating it so reported findings cannot become unattributed team benchmarks.

Evidence boundary

We did not submit forms, make deposits or test A23's live app. The vendor case cannot isolate the contribution of deep linking from its other measurement changes or establish current market eligibility.

For background, see reading an mmp dashboard without fooling yourself and cohort quality checklist ua spend. These are existing archive discussions, not independent certification of this case. No first-hand campaign result is asserted.