Kochava + Amplitude
Connect Kochava and Amplitude to Unify Mobile Attribution with Product Analytics
Automatically sync Kochava attribution data into Amplitude to see exactly which campaigns drive your highest-value users.
Why integrate Kochava and Amplitude?
Kochava and Amplitude do complementary jobs in your mobile growth stack. Kochava tracks where users come from and how they were acquired. Amplitude shows what those users do once they're inside your product. Together, they answer the full user journey question: which channels bring users in, and which experiences keep them around. Integrating the two removes the blind spots you get when attribution and behavioral analytics live in separate silos.
Automate & integrate Kochava & Amplitude
Use case
Enrich Amplitude User Profiles with Kochava Attribution Data
When a new user is first attributed in Kochava — whether from a paid social ad, an influencer link, or an app store search — tray.ai automatically sends that attribution metadata as user properties into Amplitude. Every Amplitude cohort, funnel, and retention chart can then be segmented by install source, campaign name, ad group, creative, and media partner. Your product team gets instant visibility into acquisition context without ever leaving Amplitude.
Use case
Send Amplitude Behavioral Events Back to Kochava for LTV Modeling
High-value in-app behaviors tracked in Amplitude — subscription upgrades, feature adoption milestones, repeat purchases — can be automatically forwarded to Kochava as postback events. This enriches Kochava's lifetime value (LTV) models and helps media partners optimize toward users who actually convert, not just users who install. The result is smarter bidding and a lower effective cost per high-quality user.
Use case
Automate Cohort Syncing for Re-Engagement Campaigns
Amplitude behavioral cohorts — users who completed onboarding but never purchased, or users who were active 30 days ago but have since lapsed — can be automatically synced to Kochava to power re-engagement campaigns. Tray.ai monitors Amplitude cohort membership on a schedule and updates Kochava audience lists in real time, so your retargeting efforts are always aimed at the right users.
Use case
Attribute Revenue Events to Acquisition Channels in Real Time
When a purchase or subscription event fires in your app and Amplitude captures it, tray.ai immediately relays that revenue event back to Kochava with full attribution context. This closes the revenue attribution loop so your marketing dashboards in Kochava reflect actual downstream revenue rather than just installs or sessions. Finance and marketing teams can reconcile campaign spend against attributable revenue without waiting for batch pipelines.
Use case
Trigger Onboarding Workflows Based on Attribution Source
Different acquisition channels often signal different user intent. A user who installed via a paid brand campaign may need a different onboarding experience than one who came through a referral program. By pulling Kochava attribution data into Amplitude, tray.ai can trigger downstream workflows that personalize onboarding sequences, in-app messaging, or push notification campaigns based on the user's original install source.
Use case
Monitor Campaign Quality with Automated Anomaly Alerts
By combining Kochava's install volume data with Amplitude's engagement and retention metrics in a single automated workflow, tray.ai can detect when a campaign is driving high install volume but unusually low engagement — a classic sign of low-quality or fraudulent traffic. Automated alerts can notify your growth team in Slack the moment quality metrics fall below defined thresholds, so you can pause campaigns or adjust bids before more budget is wasted.
Use case
Build Cross-Channel Attribution Reports in Your Data Warehouse
Tray.ai can orchestrate the extraction of raw attribution events from Kochava and behavioral event streams from Amplitude, then transform and load them into a shared data warehouse like Snowflake or BigQuery. The result is a unified user-level dataset that supports advanced attribution modeling, cohort analysis, and LTV forecasting across every channel and product surface. It stays current automatically, with no manual data engineering needed.
Get started with Kochava & Amplitude integration today
Kochava & Amplitude Challenges
What challenges are there when working with Kochava & Amplitude and how will using Tray.ai help?
Challenge
Identity Resolution Across Kochava Device IDs and Amplitude User IDs
Kochava primarily identifies users by mobile device identifiers (IDFV, GAID, or Kochava Device ID), while Amplitude uses a combination of Amplitude User IDs and Device IDs set by your app's SDK. Bridging these identity spaces is technically complex. A mismatch means attribution data lands on the wrong user profile or fails to match entirely, which corrupts cohort analysis.
How Tray.ai Can Help:
Tray.ai's workflow logic lets you build a custom identity resolution layer that maps Kochava device identifiers to Amplitude user IDs using a shared lookup store or your existing identity graph. Conditional branching handles edge cases like anonymous pre-login events, so attribution data lands on the correct Amplitude profile even across login state changes.
Challenge
Handling High-Volume Event Streams Without Data Loss
Mobile apps at scale generate millions of attribution and behavioral events per day. Pushing all of this data between Kochava and Amplitude in real time through a poorly designed integration creates bottlenecks, API rate limit errors, and data loss — particularly during campaign launch spikes when install volumes can surge 10x above baseline.
How Tray.ai Can Help:
Tray.ai is built for high-throughput workflows with native support for batching, retry logic, and rate limit handling. You can configure batch sizes and scheduling intervals to stay within Amplitude's Identify API and Kochava's postback rate limits, and tray.ai's automatic retry mechanism makes sure no events are lost during temporary API outages or throttling windows.
Challenge
Schema Drift Between Kochava Campaign Taxonomy and Amplitude Event Schema
Kochava's attribution parameters — campaign names, ad group labels, creative IDs, media partner slugs — are defined by your marketing team and change frequently with each new campaign launch. When these values change without corresponding updates to the Amplitude property mapping, dashboards break, cohorts become inconsistent, and historical analysis loses continuity.
How Tray.ai Can Help:
Tray.ai workflows include a transformation layer where you can normalize and standardize Kochava attribution fields before they reach Amplitude. Regex-based cleaning, value mapping tables, and fallback defaults mean that even when your marketing team introduces new campaign naming conventions, the data arriving in Amplitude stays consistent and queryable.
Challenge
Keeping Both Directions Fresh Without Engineering Overhead
A useful Kochava-Amplitude integration runs in both directions — attribution enriches product analytics, and behavioral signals flow back to improve acquisition. Building and maintaining two separate pipelines in custom code requires ongoing engineering effort, and any breakage in one direction silently degrades both your product insights and your campaign performance.
How Tray.ai Can Help:
Tray.ai lets you manage both the Kochava-to-Amplitude and Amplitude-to-Kochava pipelines from a single visual workflow builder without writing custom code. Built-in monitoring, alerting, and workflow versioning mean your team gets notified immediately if either direction fails, and rolling back to a prior version takes one click.
Challenge
Compliance and Data Privacy Across Attribution and Analytics Pipelines
Moving user-level data between Kochava and Amplitude introduces compliance obligations under GDPR, CCPA, and Apple's App Tracking Transparency framework. Device identifiers must be handled carefully, consent signals must be respected, and certain user data must be deletable on request. Custom integration scripts frequently fail to enforce these requirements consistently.
How Tray.ai Can Help:
Tray.ai workflows can be configured to check consent flags before syncing user-level data, exclude opted-out users from attribution postbacks, and trigger deletion workflows across both Kochava and Amplitude when a right-to-erasure request comes in. Centralizing this logic in tray.ai means your compliance rules are enforced uniformly across every data flow rather than scattered across individual scripts.
Start using our pre-built Kochava & Amplitude templates today
Start from scratch or use one of our pre-built Kochava & Amplitude templates to quickly solve your most common use cases.
Kochava & Amplitude Templates
Find pre-built Kochava & Amplitude solutions for common use cases
Template
Kochava Install Attribution → Amplitude User Properties Sync
Whenever Kochava records a new attributed install, this template automatically finds the corresponding Amplitude user and sets their user properties to include campaign name, media partner, ad group, creative ID, and install type. Every Amplitude user profile stays enriched with full acquisition context from the moment they first appear in your product analytics.
Steps:
- Trigger: Kochava receives a new attributed install event via webhook or scheduled pull
- Lookup: Match the Kochava device ID or IDFV/GAID to the corresponding Amplitude user ID
- Transform: Map Kochava attribution fields to Amplitude user property schema
- Action: Call Amplitude Identify API to set attribution properties on the matched user profile
Connectors Used: Kochava, Amplitude
Template
Amplitude Revenue Events → Kochava Postback Forwarding
This template listens for purchase or subscription events logged in Amplitude and automatically forwards them to Kochava as postback events with the original attribution data intact. Media partners and internal dashboards in Kochava receive accurate downstream revenue signals, enabling LTV-based optimization across all acquisition channels.
Steps:
- Trigger: Amplitude event stream detects a revenue or purchase event
- Enrich: Retrieve original Kochava attribution data for the user from a shared data store or prior sync
- Transform: Format the event payload to meet Kochava's postback API specification
- Action: POST the enriched revenue event to Kochava's postback endpoint
Connectors Used: Amplitude, Kochava
Template
Amplitude Lapsed-User Cohort → Kochava Re-Engagement Audience Sync
On a configurable schedule, this template queries Amplitude for users who match a defined lapse or churn-risk cohort, then updates a corresponding Kochava audience list to enable retargeting across connected media partners. The audience refreshes automatically so your re-engagement campaigns always reflect current behavioral data.
Steps:
- Trigger: Scheduled run (e.g., every 6 hours or daily)
- Fetch: Query Amplitude Cohorts API for current members of the lapsed-user cohort
- Diff: Compare against previous audience list to identify additions and removals
- Action: Add new members and remove exited members from the target Kochava audience segment
Connectors Used: Amplitude, Kochava
Template
Kochava + Amplitude Data → Snowflake Attribution Data Mart
This template runs a recurring ETL pipeline that extracts install and attribution events from Kochava and behavioral events from Amplitude, joins them on a shared user or device identifier, and loads the unified dataset into a Snowflake schema built for attribution analysis and LTV reporting.
Steps:
- Extract: Pull attribution event logs from Kochava's reporting API on a scheduled basis
- Extract: Pull event export data from Amplitude's Export API for the same time window
- Transform: Normalize schemas, resolve identity across device IDs, and join datasets on shared user key
- Load: Upsert unified records into a Snowflake attribution fact table for BI consumption
Connectors Used: Kochava, Amplitude
Template
Campaign Quality Monitor — Kochava Installs vs. Amplitude Engagement Alert
This template continuously compares install volume from Kochava campaigns against early engagement metrics in Amplitude. When a campaign exceeds an install threshold but falls below a minimum engagement rate within the first 24 hours, an automated alert goes to the growth team via Slack, prompting immediate review of creative, targeting, or media partner quality.
Steps:
- Trigger: Scheduled run every 4 hours
- Fetch: Pull install counts by campaign from Kochava reporting API
- Fetch: Query Amplitude for D1 engagement or retention rate for the same campaign cohort
- Evaluate: Compare install volume against engagement rate thresholds using tray.ai logic operators
- Action: Send Slack alert with campaign name, install count, and engagement rate if thresholds are breached
Connectors Used: Kochava, Amplitude
Template
New Kochava Attribution → Personalized Amplitude Onboarding Event Trigger
When Kochava attributes a new install to a specific campaign or channel segment, this template sends a custom Amplitude event that triggers a personalized onboarding experience matched to that acquisition context. Users from paid social campaigns, referral programs, and organic search each enter a distinct onboarding funnel, improving activation rates across all channels.
Steps:
- Trigger: Kochava webhook fires on new attributed install
- Classify: Determine onboarding variant based on Kochava campaign type or media partner
- Action: Log a custom Amplitude event (e.g., 'onboarding_variant_assigned') with variant name as an event property
- Downstream: Amplitude experiment or messaging tool reads the event property to serve the correct onboarding flow
Connectors Used: Kochava, Amplitude