Get ROAS for your ads

If your Revenue column shows a dash, money is going out but your site isn't wired in yet. Nothing is broken; Affiliateo just has no way to see your sales.

When a tracked visitor buys, the sale is matched to the exact campaign that brought them. That match is your verified ROAS, and it works for any number of campaigns pointing at any number of sites.

Running ads for more than one website? Add each one (up to 10). Every campaign is matched to whichever site its clicks actually land on, automatically.

Tracked sites added this way are not affiliate apps: they cannot be joined, never appear on Discover, and pay no commissions to anyone. If you already run affiliate apps on Affiliateo, their sites are counted automatically and you don't need to add anything.

Sending those sales to the affiliate's own ad account

The pixel in each ads app's settings does not affect your Affiliateo numbers. It reports the sales Affiliateo already tracked back to the ad network, so the network's own dashboard shows purchases and its bidding can optimize. Turn it on or off any time; your verified ROAS is unaffected.

In any ad network's settings, open Track your sales and pick Track a mobile app. Choose how your app takes payments (RevenueCat, Apple In-App Purchase, Google Play, Adapty or Stripe) and add the Affiliateo SDK to the app. Your app's sales then count as revenue here, with no affiliate program. Apple Search Ads gets the full picture: the SDK ties installs and sales to the campaign, so you see real ROAS. For Google, Meta, TikTok and Snapchat ads, the app store doesn't tell Affiliateo which ad led to an install, so those sales add to your total revenue but can't be tied to one campaign here. Those networks measure their own app campaigns through their own SDK or a measurement partner, as the next section explains.

For a campaign that sends people to one of your apps, the Campaigns table also shows what happened inside the app in the dates you picked: Downloads (phones that opened the app for the first time after the ad, counted by Affiliateo, so it can differ from the network's own Installs), Trials, Cost per trial, Trial rate, Paying (people who paid you for the first time, after a free trial or straight away), Cost per paying customer and Paid rate. A row of cards above the table adds them up.

The ROAS day column takes the people who downloaded in those dates and divides what they paid within 1, 2, 4, 7 or 30 days of downloading by what the ads cost. Pick the day in the ROAS day box beside the date range: it changes both the ROAS day card above the table and the column. The column is on the Campaign tab, and on Apple Ads on the Ad group and Keyword tabs too, because Apple names the ad group and keyword of each install. The number can still go up while some of those people have not had that many days yet. Payback is how many days after downloading they had paid back the spend, or how much has come back until then. Trial rate and Paid rate follow the same people: of those downloads, the share that started a free trial within 7 days of first opening the app, and the share that paid for the first time within 30 days.

Renewal off is the share of those trials whose person turned off renewal before the first charge. Every row also shows Click to install (Tap to install on Apple Ads, Click to conversion on the networks whose conversion column is not installs): the network's installs or conversions divided by its clicks, both as the network counts them.

A campaign belongs to the apps its downloads and sales went to (an Apple Ads campaign also to the app it promotes). With more than one app, the App buttons above the table show one app's campaigns and numbers at a time. The same numbers are on the API (GET …/ads, with ?app=) and the MCP's get_ad_stats.

On the Apple Ads page, the Keyword tab has one table: each keyword with its on and off switch and bid, Apple's spend, installs and cost per install, and what the people it brought did in your app in the same dates. Trials are free trials started within 7 days of the install, and Paying is the people who paid for the first time within 30 days. CAC, LTV and LTV:CAC are on the same row. The Country box shows one country's figures on their own. A Search Match row per ad group holds the installs Apple gives no keyword, so the rows add up to the ad group. Est. CAC is spend divided by paying customers.

Est. LTV is what a paying customer is expected to bring in over 12 months: what they paid so far, plus their price times the renewals still to come at their plan's renewal rate (how often first payments of that plan renewed, mixed with a typical rate while there is little data). A one-time purchase is worth what was paid. Amounts are what the buyer paid, before the store's cut, like the Revenue page. LTV:CAC is green from 3x, amber from 1x and red below 1x.

The trend compares the dates you picked with the same number of days just before (yesterday with the day before, the last 7 days with the 7 before), with the earlier installs counted at the same age. All time has nothing before it, so it shows a dash. Installs younger than 30 days are still counting.

On the Search terms tab, the + beside a term adds it as a keyword: pick the ad group, the match type and a bid. It starts paused unless you turn it on. The same numbers are on the API (GET .../ads/keywords-economics) and the MCP tool get_apple_keyword_economics.

App campaigns get better when the ad network knows who pays, not only who installs. In the Meta, TikTok or Snapchat settings here, open Send app sales and paste the network's ID for your app: the Meta dataset ID, the TikTok App ID or the Snap App ID. Each first payment in that app then goes to the network: a subscription's first charge, or a one-time purchase. If your app's payments come through RevenueCat, Apple, Google Play or Adapty connected here, you're done: they're sent on their own. You can also add one line to your paywall, right after a purchase succeeds. It sends the phone's network address too, which helps the network match. Either way, each payment is sent once.

// RevenueCat
let result = try await Purchases.shared.purchase(package: package)
if !result.userCancelled, let transaction = result.transaction {
    Affiliateo.purchase(
        transactionId: transaction.transactionIdentifier,
        productId: transaction.productIdentifier,
        price: package.storeProduct.price,
        currency: package.storeProduct.currencyCode ?? "USD"
    )
}

// StoreKit 2
if case .success(.verified(let transaction)) = try await product.purchase() {
    Affiliateo.purchase(transaction)
    await transaction.finish()
}

Affiliateo sends payments, not installs. App campaigns count installs through the network's own SDK in your app or a measurement partner (AppsFlyer, Adjust, Branch, Singular or Kochava). So an app that runs ads on Meta, TikTok or Snapchat adds that network's SDK, or a partner, for installs, and keeps Send app sales on for payments.

In Send app sales, choose what each app sends to each network: Sales, Trial starts or Both. Sales sends each customer's first payment as a purchase, and a free trial's first real charge counts as one. Trial starts sends only the start of each free trial, as the network's trial event: StartTrial on Meta and TikTok, START_TRIAL on Snapchat. It's never sent as a purchase. Both sends the two as separate events.

Pick Sales for most apps, so the campaign learns who pays. Pick Trial starts if your app has a free trial and only a few sales a week: trial starts come days sooner and more often, so the campaign learns faster. With Both, pick one of the two as the campaign's goal in the network's ads manager.

A trial start is sent only after the store confirms it, so it needs your payment provider connected here: RevenueCat, Apple, Google Play or Adapty. It's sent with a value of 0, because nobody has paid yet. On Meta and Snapchat, the plan's price goes with it as its predicted value. Renewals and refunds are never sent.

Why let Affiliateo send the payments rather than each network's SDK: a payment is sent only after the store confirms it was really paid, each sale goes out once, a first payment still counts when it happens while the app is closed (a free trial turning paid days later, for example), one setup here covers Meta, TikTok and Snapchat, and you switch a network on or off without an app update. A network's SDK mostly sees what happens while the app is open.

A payment your payment provider reports by itself carries no details about the phone. Affiliateo matches it to the phone that bought, using the network address the phone last used in your app. That address is kept for up to 35 days, and only while Send app sales is on for the app. The paywall line above still matches best.

TikTok only accepts app sales from a server after it switches the feature on for your ad account, so ask your TikTok rep. Google gets app sales from Google Play or Firebase instead, so it isn't listed. Renewals and refunds aren't sent, and your revenue here still subtracts refunds.