Read your program's results

InfluTo measures one thing end to end: which creators bring you installs and paying users, and what they earned. Every number has one definition, and every screen, the creator dashboard and the agent API use it (see How we count). Only production data counts: sandbox purchases, simulated purchases and test data never show up in your numbers.

Where to find each number

Pick the period at the top of each page: 7d, 30d, 90d or Custom. Days follow your browser's time zone.

Overview

The six figures at the top read as the funnel, left to right. Their captions add context: typed codes next to Clicks, the share of clicks next to Installs, how many are in trial and paying now, and the refunds next to Revenue.

Daily results shows installs, trials and new paying subscribers per day, with revenue below. Click a day to see who drove it, then See this day's activity to open that day in Activity.

Needs attention lists what's waiting for you: bonuses to review, creators who haven't picked a code, a low wallet, campaigns paused at a limit, an integration that isn't verified yet, and purchases whose code matched nothing.

Activity

Activity is a chronological feed of what happened in the app: installs, trials, first payments, renewals, one-time purchases, refunds, cancellations, milestone bonuses, free-code redemptions, commission rate changes, creators joining or leaving, payouts, and purchases whose code matched no campaign.

Each row names the creator, the code and the campaign, how the install was credited, a pseudonymous subscriber key (sub_…) and the amount, such as the commission earned or reversed.

• Filter by Campaign, Creator or Code, or pick event groups under Show. Search a subscriber takes a subscriber key or an app user ID.
• Test data is hidden. Turn on Include test data to see sandbox and simulated purchases too.
• An install on the creator's own device is labelled "Creator's own device". It is shown, but left out of install counts and bonuses.
• Export CSV downloads the events loaded on the page.

A creator's page, a code's page and each campaign also show their own activity, with Open in Activity for the full feed.

Creators

Creators has one row per person, with their codes nested under them: Clicks, Installs, Trials, Paid, Paying now, Revenue, Commission and Last activity. Search by name, email, handle or code. Your own channel codes are hidden; turn on Show channel codes to include them.

Open a creator to see:

• their daily results, and every code they hold in this app with its rate and results — Manage changes the rate or ends the partnership (see Invite creators);
• their activity, how their installs were credited, and the free codes that credit them;
• their milestone bonuses, to approve or void;
• everyone they brought in, all time;
• Money for this app, all time: commission earned, reversed by refunds, bonuses approved and to review, paid out, waiting for payout, and reserved in your wallet.

Codes

Codes lists Creator codes and your own Channel codes (from tracking campaigns) with their results, a Copy link button and a QR code you can download as a PNG.

Open a code for its daily results, Results per link tag, Link clicks by platform, Countries, how installs were credited, its free codes, its activity and its subscribers.

The By tag tab shows results per code or link tag — see Results per group or post.

Subscribers

Subscribers has one row per user a creator brought in: the subscriber key, the creator and code, the status, when they installed, started a trial or paid, how many times they renewed, what they paid and the commission it earned.

Filter by status, campaign, creator or code. Search takes the full subscriber key (sub_…) or the exact app user ID.

Open a subscriber for the creator, code and campaign, how they were credited (Credited by), payments, renewals, refunds, commission, the Commission terms locked when they subscribed, and a timeline.

Lists only show the pseudonymous key. The raw App user ID appears only on the subscriber's details, and only to organization owners and admins — use it to find the user in RevenueCat or in a support ticket. Creators never see it.

How we count

The rates follow from these: Click → install is installs as a share of link clicks, Install → trial is trials as a share of installs, and Paid per click is new paying subscribers as a share of link clicks.

• Dates. Installs count on the day they were credited, trials and paid on the day they started, and revenue and refunds on the day of the payment or refund.
• "Now" figures. Paying now and In trial now describe today, whatever period you pick.
• Organic. Installs and purchases no creator brought in don't count toward any creator. The Overview shows how much in-app revenue came without a code.

Raw, flagged and clean clicks

The click number is always the cleaned one. To see what was removed, InfluTo also keeps:

• raw — every tap on the link that was recorded,
• flagged — taps marked as suspicious,
• canonical — the cleaned number shown everywhere.

A campaign's Overview tab shows this under All time ("Clicks leave out repeats and flagged traffic: … raw link hits, … flagged"). Agents get it as clicks.decomposition (raw, flagged, canonical).

Why a click gets flagged

InfluTo screens every tap for automated and abusive traffic — bots, link-preview fetchers, scripted or repeated tapping — before it counts. Flagged clicks stay on record but are excluded from click and install counts and from milestone bonus progress, so a creator can't inflate their numbers. The exact rules aren't published, so they can't be gamed.

How installs were credited

Every credited install records how it was matched. The Overview, each creator, each code and each subscriber show it. Exact methods come first; link-click matching is the fallback.

How each method works: How attribution works.

How to read the funnel

Clicks  →  Installs  →  Trials  →  Paid
        install rate  trial rate   trial-to-paid

Look for the step where most people drop out:

• Lots of clicks, few installs. People tap but don't install. Check the store listing they land on, and whether the creator's audience matches your app. Remember that link-click matching only connects installs to taps from the last 72 hours (see Attribution), and that people who install later from a store search show up as organic. A code field in your app catches more of them — see Referral codes.
• Installs, but few trials or purchases. Onboarding or the paywall is losing people. Consider a better offer for referred users — see Referral offers.
• Trials, but few become paid. Look at pricing and what the trial shows. Commission is only earned once a trial converts.

The steps aren't strictly nested: a user who buys without a trial counts as paid but not as a trial, so Paid can be higher than Trials.

Results per group or post

One creator code is often posted in many places — several Facebook groups, a TikTok bio, a newsletter. Tag the link once per place and InfluTo shows clicks, installs, trials and paid subscriptions for each place separately.

Tag the links

Add a tag to the creator's referral link. Use a short name per place; the code stays the same:

https://influ.to/{app_slug}/{CODE}?s=fb-hu-keto
https://influ.to/{app_slug}/{CODE}?s=fb-hu-vegan
https://influ.to/{app_slug}/{CODE}?s=tiktok-bio

Creators can build these links themselves with the link builder under Codes & links in their dashboard.

Tags are saved with each tap, so they work whether the person installs from the App Store or Google Play. They don't change who gets credited or what anyone earns. Values are kept as written (up to 255 characters): FB-hu-keto and fb-hu-keto are two different rows, so agree on one spelling with your creators. Taps from before a link was tagged stay untagged.

Read the breakdown

The breakdown is in three places:

• Codes → By tag — every code in the app. It starts per code.
• A campaign's Codes tab — that campaign's codes. It also starts per code; switch to a link tag (?s=, utm_*) to see which group or post worked.
• A code's page → Results per link tag — one code. It starts per ?s= tag.

Choose what to group by. Each row shows clicks, installs, trials, paid, Revenue (what those subscribers have paid so far, in USD, refunds deducted) and the Click → install and Click → paid rates. Below the rows:

• Untagged — clicks without the chosen tag. A code typed into your app has no link and no tag, so when you group by a tag, its trials and purchases count here. Group by Code to see them under their code.
• Total — every link click on those codes in the period: the same click number as the rest of the dashboard.

How the numbers are counted:

• By click date. A row counts the clicks made in the period and everything they led to, even if the install or purchase came later. The daily figures count trials and purchases by the date they happened, so the two don't always match.
• Clicks are cleaned the same way as everywhere else, per row: someone who opens two differently tagged links within 5 minutes counts once in each row. That's why the rows can add up to more than Total.
• Trials and paid count under a tag only when the purchase is tied to that person's own click. A purchase credited to the creator that can't be tied to one person's click isn't credited to any tag: it is listed as "not tied to a tag" under the table and included in Total. A purchase with no click on the link at all — for example a code your app set through RevenueCat — isn't in this breakdown, so trials and paid here can be lower than the daily figures.

The dashboard lists the 100 busiest values; agents can ask for up to 500.

Agents and the API

influto_get_funnel_breakdown returns the same table: pass appId and groupBy (code, sub1, sub2, utm_source, utm_medium, utm_campaign, utm_content, utm_term or referrer_host, or up to three of them separated by commas, such as code,sub1 — rows then also carry values per dimension), optionally days (1–3650, default 30), campaignId, referralCode and limit. Over REST it is GET /api/agent/apps/{app_id}/analytics/breakdown?group_by=sub1&days=30 with an agent key or OAuth token (scope analytics:read). The response has rows, untagged, unmatched (the purchases not tied to a tag), totals and notes that restate the counting rules above. Rows and totals carry clicks (link clicks) and code_entries (codes typed in the app) separately. Every row, unmatched and totals include revenue.

What creators see

Creators read the same numbers, for their own codes only, in their dashboard:

• Results — a breakdown by campaign, code and link tag (also platform, source and website), a timeline, and their referrals, shown as "Referral #1", "#2"… They never see a subscriber key or an app user ID.
• Codes & links — their codes and links, with a link builder that adds ?s= tags.
• Campaigns — what they earn in each campaign.
• Money — their balance per developer, ledger, payouts and a statement with a CSV download.

Creators see their commission, not your revenue.

With an AI agent

Agents see referred users only by their subscriber key. An agent can look up an app user ID it already has, but no tool returns one. A creator's email is included only when the agent also has the creators:read scope.

In the overview, conversions.total means paid conversions; conversions.acquired_users counts every referred user, including trials that never paid. The REST endpoints behind these tools are listed in the HTTP API. See Agent tools.

Next