You can now connect AppsFlyer to Neuro
Connect AppsFlyer to your Neuro workspace and, in a single conversation, tell apart the campaigns that just racked up installs from the ones that actually brought in users who stick around.
You can’t judge app campaigns on installs alone
When you run app campaigns, the first things you check are CPI and install volume. But a campaign that drives a lot of installs isn’t necessarily a good one. To make sound budget calls, you have to know whether those installs turned into sign‑ups, whether purchase events fired, and whether users come back days later.
The catch is that this picture is split across multiple screens. You pull spend and clicks from the ad platform, then jump into AppsFlyer to check post‑install quality. Some campaigns look great on installs but have weak D7 retention, while some channels run a higher CPI yet deliver LTV that holds up far longer.
Connect AppsFlyer to Neuro to compare installs, in-app events, LTV, and retention alongside ad spend. You can examine which campaigns continue to perform after the install in the same conversation.
You only connect once
You only need to set up the connection once, in your workspace settings. Someone with AppsFlyer admin access issues the integration token, picks the apps to analyze in Neuro, and from then on you can use them straight from chat.
- In AppsFlyer, create or copy the integration key (V2 API Token).
- If you use AppsFlyer IP allowlisting, add the static IPs listed in the Neuro integration guide to your allowlist.
- On the Neuro workspace connections screen, select AppsFlyer and paste in the token.
- If the token is valid, you’ll see the list of apps registered to the AppsFlyer account. Select the apps you want to analyze and connect them.
- Once connected, you can query that app’s AppsFlyer data from Neuro chat right away.
You can compare apps on different platforms — say the iOS and Android versions of the same product — within a single workspace. But mixing several products or brands in one workspace makes performance harder to read, so it’s safer to keep a separate workspace per product.
Once connected, these calls get easier
A campaign with cheap installs may differ from one that brings in purchasers. Pair acquisition costs with post-install metrics to gather evidence for a budget decision.
| The question | How Neuro answers it | What to watch for |
|---|---|---|
| Which channels brought in high‑quality users this month? | See installs, cost, events, and revenue together by channel and campaign. | Don’t stop at install volume — always look at key events like purchases and sign‑ups too. |
| Should I put more budget into iOS or Android? | Compare app‑level CPI, revenue, ROAS, and retention side by side over the same period. | If the apps use different currencies or time zones, line those up before you read the results. |
| Which campaigns are delivering strong post‑install quality? | Look at D1/D7/D30 retention, LTV, and ROAS by campaign. | Compare D30 metrics only for cohorts that have reached 30 days after install. Do not treat immature observations as zero. |
| Is retargeting worth keeping always on? | Split performance between user acquisition and re‑engagement. | User acquisition and retargeting have different goals, so it’s best not to rank them together in one table. |
As a marketer, you don’t have to memorize app IDs or report settings every time. Neuro checks which apps are connected first: if there’s only one, it uses that app; if both iOS and Android are connected, it frames the answer as a comparison between the two.
Questions you can ask right away
Instead of reeling off a long list of metrics, just ask for the decision you’re trying to make right now. Whether you’re looking at cost per install, post‑install quality, or retargeting efficiency, Neuro will build a different table to match.
Heads‑up: AppsFlyer numbers follow different definitions
The AppsFlyer integration is built for querying and analysis. Neuro reads AppsFlyer data to inform your campaign decisions, but it doesn’t change event definitions inside AppsFlyer or adjust budgets directly in the ad platforms.
- AppsFlyer‑based performance and platform‑reported performance can differ because of attribution, time zone, currency, and event mapping.
- For comparison reports, lock down the date range and whether you’re looking at user acquisition or retargeting first.
- Check whether the observation period has ended for D7 and D30 metrics. You cannot yet assess D30 retention for users acquired last week.
- If a token expires, permissions fall short, or IP allowlisting is missing, Neuro will prompt you to reconnect AppsFlyer or check your permissions.
Budget changes and campaign pauses are separate actions requiring access to the relevant ad platform. Before acting on an AppsFlyer comparison, check the platform’s current state and the definitions used in each report.
Sources
- AppsFlyer Support: Managing AppsFlyer tokens
Official documentation on what the AppsFlyer API V2 Token is for, the admin permissions it requires, and how to create and rotate tokens.
- AppsFlyer Support: Set up your API allowlist
Official documentation on how the AppsFlyer API allowlist behaves at the account level and how to register IPs.
- AppsFlyer Support: App list API for app owners
Official documentation on using the V2 API Token to pull an account’s list of apps along with each app’s currency and time zone.
- AppsFlyer Developer Hub: Pull API aggregated overview
Official documentation on authentication and the supported report types for AppsFlyer Pull API aggregate reports.
- AppsFlyer Support: Cohort API
Official documentation on the definitions and parameters of the AppsFlyer Cohort API used for cohort, retention, and LTV analysis.
Related posts
Set the attribution window before comparing Criteo ROAS
Connect a Criteo advertiser to Neuro and you can review campaign and ad set performance next to your other channels, then start, pause, and adjust budgets from one screen when you need to.
Before you connect an ad account to Neuro
A guide to Neuro account connections, workspace access, default approvals and automatic execution, and AI API data policies.
How to ask AI when your ROAS numbers don’t match
Why attributed revenue can exceed actual sales, which dates and conversion definitions to align, and how to ask Neuro to investigate a ROAS discrepancy.
When AI groups campaigns incorrectly: check names and UTMs
Find campaigns whose names leave product groups or audiences unclear, then use settings, UTMs, and a mapping table to classify them.