Ad impressions: count the ads your app displays

RevenueDot counts rc_ads_ad_displayed events. An impression is an ad that was shown, not an ad that was requested or loaded. Your SDK ad tracking sends the events to RevenueDot's /v1/events endpoint, either from an ad network adapter or by manual capture, and RevenueDot drops a repeated event id so one event counts once.

Sandbox and TestFlight builds are stored as sandbox and left out. The count is a flow: it adds up the events that happened in each period, in UTC. The current period is incomplete until it ends.

Filter or segment by app, country, platform and app version. The default resolution is day, and week, month, quarter and year are available. For impressions by network, format and placement, use the Ads page in the dashboard.

Find the chart in the dashboard under Analytics > Charts, or call GET /v2/projects/{project_id}/charts/ad_impressions. The response has the same shape as RevenueCat's Charts API.

Illustrative numbers for three days.

Impressions for the three days = 4,200 + 3,900 + 4,400 = 12,500.

Impressions are the volume side of ad income. Revenue is impressions times the price per impression, so when ad revenue moves, impressions tell you whether you showed more or fewer ads.

They also show how heavy your ad load is. If impressions grow faster than your active users, each user sees more ads, which can hurt reviews and subscription conversion. Check it after you add a placement, and read it with Clicks and eCPM.

How to read it

• A jump after a release can be a new placement or an event that fires twice. Compare it with clicks and revenue.
• Impressions count displayed ads. An ad that loaded but never appeared is not counted. Fill Rate counts loads.
• Divide impressions by days and by active customers to estimate ads per user.
• Segment by app version to see which release changed the ad load.
• Zero impressions with real traffic usually means the SDK is not sending ad events.