Install guide / Authenticated channel
Install FXMacroData on Mobile app
Your meter
Mobile app is measured by the backend audience endpoint.
There is no browser here, so your own server reports the audience: one scrambled reference per unique person per billing period. Repeats are free, so retries and replays never move the count.
You do not use the browser pixel. There is no page to put it in, and the pixel cannot see this surface at all.
Mobile app specifics
Hash your account id, not the device identifier. One person with your app on a phone and a tablet is one measured user, and a device id would bill you twice for them.
Setting it up
-
01
Register the Mobile app surface
Add it in API Management and copy the redistribution key. Registering enables access immediately; there is no review queue.
-
02
Derive the user reference
For Mobile app, use your own account id for the signed-in user. Hash it with a secret only you hold, so the value we store cannot be reversed and cannot be correlated with anyone else's report.
user_ref = hmac_sha256( key=YOUR_SECRET, message=account_id, ).hexdigest() -
03
Report once per person per billing period
Send the reference the first time you serve that person in the period, then mark them done. Repeats are free, so a retry or a replay is never a problem.
POST https://fxmacrodata.com/partner-meter/v1/audience Authorization: Bearer <your redistribution key> Content-Type: application/json { "surface_id": "Mobile app", "user_ref": "<hmac of account_id>" } -
04
Show the attribution
The FXMacroData credit has to be visible wherever the data appears, in the same view as the data itself.
The rule that matters
The redistribution key must never ship inside a binary, a bundle, or anything a user can unpack. Your backend fetches FXMacroData and serves your own client.
Confirming it works
- 1 Send one report for a test user and confirm a 202 response.
- 2 Send the same reference again and confirm the billable count does not move.
- 3 Open API Management and confirm the measured user appears against this surface.
Reference
Shared detail that applies to every authenticated channel, kept in one place rather than restated here.
Endpoint reference
Request shape, every status code, and every error string.
Building the user reference
How to derive a reference that is stable, scrambled, and yours alone.
When to call
Once per person per period, and how to remember you already did.
Backend recipes
Node, Python, Go, PHP, Ruby, Java, and .NET.
Other channels using the backend audience endpoint
Same meter, different setup detail.
AI Answer-Ready
Key Facts
- Page
- Mobile App
- Section
- Documentation
- Canonical URL
- https://fxmacrodata.com/documentation/redistribution/mobile-app
- Source
- FXMacroData editorial and official publisher references
- Last Updated
- See page metadata
Provenance And Trust
Cite the canonical URL and source field above. Where available, this page maps to official publisher releases and timestamped updates.
Quick Q&A
What is this page about? This page explains Mobile App with directly usable context for trading, research, and API workflows.
What source should be cited? Use the canonical URL and the listed source field; cite official publisher references when available.
How fresh is this content? The last updated value above reflects the page metadata or latest available data timestamp.
Can this be used in AI assistants? Yes. This section is intentionally structured for retrieval and citation in chat assistants.
Prompt Packs
Use these in ChatGPT, Claude, Gemini, Mistral, Perplexity, or Grok for consistent source-aware outputs.