Data & Storage · Integration
Kochava
Add Kochava to your product for your customers, and give your AI agents governed access to it.
Embed a Kochava integration so your customers can bring their own attribution and campaign data into your product instead of exporting reports by hand. Every account is structured differently, so app, campaign and network mapping is configuration per customer rather than code. fastn handles per-customer credentials, pagination and API upkeep, and reads are throttled so a large backfill does not exhaust a customer's API allowance.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own Kochava account so your product reads their campaign and attribution data.
Pull install and in-app event data per tenant so your product reports on the campaigns each customer actually runs.
Read campaign and network breakdowns so your product groups results the way a customer already does.
Keep large historical reads paginated and throttled so a first import stays inside a customer's allowance.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent pulls attribution data before answering a performance question.
An agent compares campaign results across two periods and explains what moved.
Every read runs under the customer's own credentials and is logged per tenant.
Example prompt
Pull installs and post-install events by network for the last 30 days and show which campaigns declined.
Set up Kochava in 4 steps
- 01Open the Kochava connector from your fastn dashboard.
- 02Have each customer authenticate their own Kochava account.
- 03Map the apps, campaigns and metrics your product reports on, then enable actions.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Kochava integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Kochava integration without building it. Your customers connect their own Kochava 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 Kochava update is not your on-call problem.
- One integration serves your product and your agents. The same governed Kochava 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
Amplitude
SnowflakeWorks well with
Adobe AnalyticsOften used alongside
Tools the same teams tend to run next to Kochava, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceKochava integration FAQ
How do I add a Kochava integration to my product?
Enable the Kochava connector in your fastn dashboard, then let each customer authenticate their own Kochava account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Kochava client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Kochava account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Kochava 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 Kochava 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 pulls attribution data before answering a performance question.
Who maintains the Kochava integration?
fastn does. When Kochava 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 Kochava 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 Kochava 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 Kochava integration?
A common starting point: connect their own Kochava account so your product reads their campaign and attribution data. 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 Kochava integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Kochava does not change your per-connector cost. You can start free with 3 connected accounts.
Add Kochava to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.