Data & Storage · Integration
Localytics
Add Localytics to your product for your customers, and give your AI agents governed access to it.
Embed a Localytics integration so your customers can use the analytics they already collect inside your product, and so events that happen in your product reach their account without a nightly export. Each customer authorises their own Localytics account, so reads and writes are scoped per tenant and one customer's analytics never mixes with another's. Field and schema mapping is configuration, which matters because analytics implementations differ per customer and change without warning. fastn handles the credentials, pagination, throttling and API upkeep, and the same governed connection is what your AI agents query when they need usage data.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Localytics account so the analytics they already collect can be read inside your product.
Send events from your product into a customer's account so their reporting reflects what a user actually did.
Show a customer their own engagement data in your product instead of asking them to open a second analytics tool.
Keep every read and write scoped to the tenant that authorised it, so analytics stay with the customer they belong to.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent answers how a feature is being used by reading the customer's own analytics rather than a stale summary.
An agent pulls engagement figures for one account and explains what moved week over week, with each read audited.
An agent records a product event within scoped permissions, with the write attributed to the tenant that authorised it.
Example prompt
How has engagement moved for this account over the last month according to their Localytics data?
Set up Localytics in 4 steps
- 01Enable the Localytics connector in your fastn dashboard.
- 02Have each customer authorise their own Localytics account so calls run under their credentials.
- 03Map the events and fields your product reads and writes, per customer.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Localytics integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Localytics integration without building it. Your customers connect their own Localytics account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Localytics update is not your on-call problem.
- One integration serves your product and your agents. The same governed Localytics connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Compare with
AmplitudeWorks well with
Adobe Analytics
AirshipOften used alongside
Tools the same teams tend to run next to Localytics, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceLocalytics integration FAQ
How do I add a Localytics integration to my product?
Enable the Localytics connector in your fastn dashboard, then let each customer authenticate their own Localytics account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Localytics client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Localytics account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Localytics account and only ever sees their own records, datasets and fields. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Localytics integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent answers how a feature is being used by reading the customer's own analytics rather than a stale summary.
Who maintains the Localytics integration?
fastn does. When Localytics changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the Localytics integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large Localytics reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the Localytics integration?
A common starting point: let each customer connect their own Localytics account so the analytics they already collect can be read inside your product. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Localytics integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Localytics does not change your per-connector cost. You can start free with 3 connected accounts.
Add Localytics to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.