When a client taps "Deposit", is it good news? Promising, certainly, but tapping the button shows what the client wants to do. It does not exactly mean money has arrived.
The same goes for onboarding. Starting registration is not completing it as opening a questionnaire is not submitting it.
Yet when a client never deposits, those different journeys can end up under the same unhelpful label of “They lost interest”.
Did they, though? Or did something get in the way?
Before blaming the client’s attention span, let’s see how far they got. That’s where FXBO Mobile App analytics comes in: helping brokers follow recorded steps, spot drop-offs, and investigate the payment failures the app can observe.
The Distance Between “I’m Interested” and “I Deposited”
A registration gives the brokerage a starting point, but what happens next deserves just as much attention.
The FXBO mobile app records milestones that brokers can use to build a funnel in Google Analytics 4 (GA4). A funnel follows a series of steps and shows how many users progress through them.
For example, brokers can build a funnel around these recorded steps:
-
Registration completed
-
Verification started
-
Questionnaire tapped
-
Questionnaire completed
-
Document uploaded
-
Deposit completed
The last step counts only deposits whose outcome the app can see. Successful payments completed on a provider’s own page may be missing, making the drop-off look larger than it really is. Check those deposits against back-office data.
That gives our mobile app analytics a practical purpose: helping brokers locate drop-offs along the journey toward funding an account.
Where Exactly Are Clients Dropping Off?
The FXBO mobile app also tracks individual pages within the questionnaire and deposit form.
For example, if clients repeatedly leave at the same questionnaire page, the team has somewhere specific to investigate. “Review page three” is a workable task but “Fix onboarding” is how a meeting earns itself another meeting.
When checking where clients drop off, make sure the numbers tell the right story:
-
For questionnaires, count people rather than page visits. A client returning to correct an answer can have the same page recorded again. That is still one client progressing through the form.
-
For deposits, step numbers offer a rough signal. Forms differ by payment provider, but the recorded page visits do not yet identify which provider the client chose. GA4 therefore cannot separate these steps by payment system. Page three is not necessarily the same stage for everyone. We plan to add payment-system information to these events in a future update.
And how far does verification tracking go? It shows that clients uploaded their documents, not whether compliance approved them. To check approval, brokers need the back-office data.
What Can We Learn from a Failed Payment?
“The deposit failed” leaves a brokerage with several possible problems and very little direction.
For the deposit and withdrawal failures it can observe, the FXBO Mobile App records a broad failure category and the payment system, where identifiable.
Four Failure Categories to Guide the Investigation
-
Provider declined: The payment provider refused the operation. The team managing that provider relationship has somewhere to start investigating.
-
Back end rejected: The back end refused the request, for example because withdrawals were disabled for that account. This calls for a check with the back-office or back-end team.
-
Request never landed: A connection problem, timeout, or unreachable server prevented the request from arriving. The mobile or infrastructure team should investigate.
-
Malformed response: A response arrived without the information needed to continue. This may point to a back-end or integration issue.
“Technical problem” has finally become specific enough to forward to the right colleague.
The provider breakdown helps too. For example, a concentration of observed failures under one payment system gives the brokerage somewhere to look. It does not, however, reveal the provider’s exact decline reason, such as insufficient funds or a card limit.
What Payment Data Can FXBO Mobile App Analytics Miss?
The FXBO Mobile App reports payment outcomes it can observe. But some payment systems take clients to the provider’s own page to finish paying.
If a client completes, abandons, or is declined there, the outcome may never reach the app. When that happens, the app's analytics records neither a completed nor a failed deposit.
An “initiated” deposit means the client opened the deposit screen. If no completion is recorded afterward, the client may still have paid successfully on the provider’s page. Brokers should therefore check these deposits against back-office data rather than treating the gap as failed payments or clients who gave up.
Two other details matter when reading these reports:
-
Amounts and currencies are not included in the app’s payment analytics.
-
A “completed” withdrawal means an accepted request, not a confirmed payout. The event records that the withdrawal request was created and accepted, not that the client received the money.
The FXBO Mobile App reports payment outcomes it can observe. But some payment systems take clients to the provider’s own page to finish paying.
If a client abandons the payment or receives a decline there without the outcome reaching the app, neither result appears in the app’s analytics.
An “initiated” deposit means the client opened the deposit screen. If no completion is recorded afterward, that alone does not prove the payment failed. Brokers should not count the difference between initiated and completed deposits as failed payments. Some outcomes remain outside the app’s view.
Two other details matter when reading these reports:
-
Amounts and currencies are not included in the app’s payment analytics.
-
A “completed” withdrawal means an accepted request, not a confirmed payout. The event records that the withdrawal request was created and accepted, not that the client received the money.
Track Which Screens Are Clients are Using in the FXBO Mobile App
Onboarding and payment events show specific milestones. Screen tracking adds another layer: where clients go as they move through the app.
Brokers can use GA4 to explore:
-
Which screens get attention: View counts show how often a screen is visited, while unique-user counts show how many different users visited it.
-
What clients open next: Path explorations show the sequence of screens clients visit.
-
Where the journey stops: Those paths help brokers spot where clients leave a flow, including verification, questionnaires, and payments.
That gives brokers something concrete to investigate. Is an important screen rarely visited? Do clients reach it, then go no further? Having a feature in the app is one thing. Seeing whether clients reach it is another.
What Does Your Brokerage Need to Get Started?
The tracking is already built into every brand’s FXBO Mobile App. To use that tracking, the broker needs a connected Firebase project. And no, your team does not need to start coding.
The broker creates a Firebase project with Google Analytics enabled, grants the designated FXBO account Owner access through the project’s “Users and permissions” settings, and lets us know through a support ticket. We can then proceed with the Firebase-dependent features.
What identifies the client in that data? An internal client ID. Firebase receives that identifier, but not the client’s name, email address, or phone number.
What Will You Find in the Reports?
Once connected, the broker receives recorded actions, known as events, alongside GA4’s automatic reports. Brokers can then build funnels around the client journeys they want to examine. We do not currently provide ready-made dashboards. Give the standard reports a little time to catch up: they can lag by up to 24 hours. This delay does not apply to Realtime and DebugView.
There is one setup detail worth getting right early: information such as payment system and failure category must be registered in GA4 before it appears as a breakdown in reports.
That registration is not retroactive. Set it up from the beginning, because deciding next month that you wanted last month’s provider breakdown will not bring it back.
What FXBO Mobile App Analytics Reports Don’t Show
Before giving the numbers the final word, it helps to know who and what might be missing.
Some Actions Do Not Appear in These Reports
Completed internal transfers, logins, trading inside MT4/MT5, and push-notification opens are not currently tracked by this analytics capability.
So, an absent action does not necessarily mean an inactive client. Someone could be trading in MT5 without that activity appearing in the mobile app’s analytics. The report has a limited view, not an opinion about their enthusiasm.
Some Clients Use the App Without Appearing in Firebase
On Android devices without Google Play Services, the FXBO Mobile App disables Firebase tracking. Those clients can still use the app normally, but their activity does not reach these reports.
That matters when reading totals: the number of recorded users or actions may be lower than the actual number. Percentages within the captured data can still help brokers understand those users’ journeys, but should not be presented as representing every client.
The takeaway? Use the data to guide your questions, with a clear understanding of whose activity it includes.
You Have the FXBO App, What Will You Learn from It?
Putting brokerage services in a trader’s pocket is a good start but understanding how clients use them gives the broker something to work with.
Perhaps a questionnaire page needs attention.
Perhaps the payments team needs a conversation with a provider.
Perhaps that screen everyone loved in the meeting has yet to meet its audience.
The FXBO Mobile App helps brokers investigate those questions through recorded client behavior. It can't explain every unfinished journey, but it can give your next decision a clearer starting point.
Already using our mobile app? Speak with our team about connecting Firebase. Still exploring your options? Request a free FXBO demo.
Your clients sure are tapping, so there is something worth learning from what follows.
