Analytics

Analytics show what your campaigns are doing — impressions, clicks, installs and CTR — broken down by app, campaign or day. All numbers come from real events reported by the SDK. This page explains each metric and how to read the breakdowns.

#Metrics

CTR is derived, not stored: it's clicks / impressions, rounded to four decimals, and 0 when there are no impressions. In the portal it's shown as a percentage.

#Breakdowns

The same metrics are available across four dimensions:

#Date filters

Filter by Today, 7 days, 30 days, or a custom range. The default range is the last 30 days.

curl "https://api.appylar.com/v1/reports?dimension=campaign&from=2026-07-01&to=2026-07-15" \
  -H "Authorization: Bearer <token>" -H "Accept: application/json"

{
  "dimension": "campaign", "from": "2026-07-01", "to": "2026-07-15",
  "rows": [
    { "campaign_id": 1, "label": "Summer promo", "impressions": 12250, "clicks": 396, "installs": 59, "ctr": 0.0323 }
  ]
}

#Interpreting the numbers

• No data yet? Numbers only appear once a campaign is serving. That requires an approved creative, an active campaign, and — for network reach — credits. A brand-new campaign shows zeros until it serves.
• CTR is a signal of creative relevance. A very low CTR usually means the creative isn't compelling or isn't well matched; try a different image.
• Installs vs clicks. Not every click installs — the gap reflects store-page drop-off. Compare installs to clicks to gauge how well the promoted app's store listing converts.
• Per-day is best for spotting trends and the effect of activating or pausing a campaign. Per-campaign and per-app are best for comparing what's working.

#Related

• Campaigns
• Billing
• REST API