EmCube
Home/Case Studies/Fintech · Pre-Launch Attribution Rebuild
CASE STUDY

How a fintech remittance app rebuilt its attribution stack and validated 4 ad channels before launch

AppsFlyer was live, but almost nothing was attributing correctly and paid campaigns across four channels hadn't launched yet. The stack got fixed first.

5,066
Clicks tracked before the fix and only 194 ever became an attributed install
4
Ad channels integrated and validated ahead of launch
2 weeks
for a fully validated, launch-ready stack
ENGAGEMENT:FintechAppsFlyerWeb + Mobile SDKSKAN 4.0Meta, Google, X, TikTok
THE SITUATION

AppsFlyer was live but almost nothing about it was attributing correctly

This remittance app had real traffic already. Organic, referral, email, content partnerships and AppsFlyer installed to measure it. But the implementation was incomplete on both web and app, so most of that traffic wasn't converting into anything the team could act on. In the period before the engagement, close to 5,000 clicks were tracked; only 194 ever got attributed to an install.

The bigger risk was still ahead. Paid campaigns across Meta, Google, X, and TikTok hadn't launched yet. Whatever was broken in the existing setup was about to get a lot more expensive to leave broken.

WHAT THEY CAME WITH
AppsFlyer installed on both web and app, but not correctly implemented on either
No structured event tracking plan. Core actions like KYC and completed transfers weren't reliably captured
No SKAN 4.0 schema, and none of four planned ad channels integrated yet, ahead of a multi-channel launch
THE GOAL

Fix the measurement layer completely, web and app, iOS and Android before the first paid campaign went live.

WHAT WE FOUND

Four gaps, discovered before they got expensive.

None of this was visible from the dashboard. It only showed up once someone checked what was actually being measured.

FINDING 01
THOUSANDS OF CLICKS, A FRACTION OF ATTRIBUTIONS

In the period before the engagement, the app tracked close to 5,000 clicks across its existing channels. Only 194 of them ever resolved into a tracked, attributed install.

IMPACT: The vast majority of real traffic was producing no usable signal at all
FINDING 02
NO WEB-TO-APP HANDOFF

There was no structured way to connect a user's activity on the website to what they did once they moved into the app, so cross-platform behavior was invisible.

IMPACT: No way to see the full user journey from first touch to converted user
FINDING 03
NO EVENT TRACKING PLAN

The events that actually matter to a remittance business, KYC started, registration completed, first transfer sent, weren't defined or mapped anywhere, so the dev team had no source of truth for what to implement.

IMPACT: Core business actions weren't being reliably captured at all
FINDING 04
NO SKAN 4.0, AND NO PAID CHANNELS INTEGRATED YET

No SKAN conversion schema existed, and none of the four ad channels planned for launch, Meta, Google, X, TikTok, were integrated yet. Whatever was broken in the existing setup would carry straight into paid spend.

IMPACT: Paid budget was about to go live on top of measurement that couldn't be trusted
SCREENSHOTBefore · AppsFlyer dashboard. Totals, pre-engagement
hq.appsflyer.com · Campaign performance by media source
APP NAME + SOURCE DETAIL CROPPED
Before · AppsFlyer dashboard. Totals, pre-engagement
Fig. 1, 5,066 clicks tracked before the fix. Only 194 ever attributed.
HOW WE FIXED IT

A full rebuild, across every layer, before a dollar of paid spend went out.

Not a patch on top of what existed. Every layer, SDK, events, deep linking, SKAN, ad channels, rebuilt and validated ahead of launch.

01
WEB + APP SDK REBUILD
Both implementations rebuilt from the ground up, with the dev team.

Worked directly alongside the client's developers to rebuild the SDK implementation on web and app from scratch, rather than patch what was already misfiring.

02
WEB-TO-APP SETUP VIA GTM
The cross-platform journey connected end to end.

Configured web-to-app tracking through Google Tag Manager, so a user's activity on the website ties back to the same user once they move into the app.

03
EVENT TRACKING PLAN + DEV GUIDE
Every core action defined, documented, and tested.

Built a full event tracking plan around the actions that matter to a remittance business, KYC, registration, transfers, then guided the dev team through implementation and tested every event once it shipped.

04
AD CHANNEL INTEGRATION. AHEAD OF LAUNCH
Meta, Google, X, and TikTok connected and validated before a dollar went out.

Integrated all four planned ad channels with correct attribution settings and validated each connection was live and passing data correctly ahead of campaigns going live.

05
ONELINK REVIEW & SETUP
Deep linking reviewed and rebuilt for accurate routing.

Audited the existing OneLink configuration and rebuilt it so every link routes users correctly across web, iOS, and Android.

06
SKAN 4.0 + REVENUE TRACKING
Non-consented iOS users made measurable. Revenue tied to source.

Configured the SKAN 4.0 conversion schema across the measurement windows, mapping real business events, KYC start, registration, purchase, and connected revenue tracking so every transfer will tie back to the channel that drove it.

SCREENSHOTAfter · SKAN 4.0 Conversion Studio. Window 1 configuration
hq.appsflyer.com · SKAN Conversion Studio
APP NAME CROPPED
After · SKAN 4.0 Conversion Studio. Window 1 configuration
Fig. 2. SKAN 4.0 setup with the events that actually matter for a remittance app.
SCREENSHOTAfter · AppsFlyer Partner Integrations. Active ad network connections
hq.appsflyer.com · Partner Integrations
APP NAME CROPPED
After · AppsFlyer Partner Integrations. Active ad network connections
Fig. 3. Ad network integrations live and validated across web and app, including Meta, Google, X, and TikTok, ready ahead of launch.
THE OUTCOME

What changed. Measured.

PLATFORMS COVERED
Web + App
iOS and Android, fully validated
AD CHANNELS READY
4
Meta, Google, X, TikTok. Integrated and validated pre-launch
SKAN 4.0 COVERAGE
3 windows
mapped to key events to ad optimization
TIME TO REBUILD
2 weeks
fully validated, launch-ready stack
THE REAL IMPACT

The app was about to spend real budget on top of measurement it couldn't trust. Two weeks in, every channel was validated and ready, so when paid campaigns go live, they'll be measurable from the first click, not discovered broken three months in.

Launch-ready
every planned channel validated before a single dollar goes out
ABOUT TO LAUNCH PAID?

If you're about to turn on paid spend and you're not fully sure the measurement underneath it is right, that's exactly the moment to check.

No commitment. Just a clear read on what's broken and what it would take to fix it before spend goes out. Because it's far cheaper to fix the measurement before spend goes out than to discover it was broken after.

Verify My Setup Before Launch