Offerwall Analytics: The Dashboard Metrics That Matter for Publishers (2026)

You have integrated the SDK, configured your postback, and your users are starting to complete offers. But how do you know if your offerwall is actually performing well? Which metrics should you track? How do you spot problems before they impact revenue? The answer is analytics — and specifically, knowing which dashboard metrics matter and how to act on them.

This guide is a practical walkthrough of offerwall analytics for publishers. We cover the key metrics, how to read the Perkox dashboard, geo-level and offer-level analysis, A/B testing methodology, alerting, and the common mistakes that lead publishers to misread their data. Whether you are managing a single app or a portfolio, this guide will help you turn data into decisions.

If you are new to offerwalls generally, start with our introduction to what an offerwall is before diving into the analytics.

1. Why Analytics Matter for Offerwall Monetization

Offerwall monetization is not a “set it and forget it” channel. Unlike banner ads or interstitials, offerwall performance is highly sensitive to placement, offer mix, user segmentation, and timing. A 10% improvement in conversion rate or a 15% improvement in fill rate can translate to meaningful revenue at scale — but you cannot optimize what you do not measure.

Analytics serves three core purposes:

• Revenue optimization: Identify which offers, geos, and placements generate the most revenue per user. Double down on what works, cut what doesn’t.
• Problem detection: Spot drops in fill rate, conversion rate, or ARPDAU before they compound. A fill rate drop on Monday might indicate an offer provider issue that resolves by Wednesday — or it might be a permanent change in the ad market.
• Strategic decisions: Data on geo performance informs localization investment. A/B test results guide placement changes. Retention impact studies validate whether the offerwall is helping or hurting long-term user engagement.

For the broader dashboard experience, see our publisher dashboard guide.

2. Key Metrics: Impressions, Clicks, Conversions, Revenue, ARPDAU, Fill Rate

The Perkox dashboard tracks dozens of metrics, but six are foundational. Every other metric is derived from or contextual to these.

2.1 Impressions

An impression is counted each time the offerwall is displayed to a user. This is the top of your monetization funnel — without impressions, nothing else happens.

• What to track: Daily impressions, impressions per active user, impression rate (impressions / DAU).
• What it tells you: Whether your placement is visible and whether users are engaging with the entry point. Low impressions relative to DAU may indicate a poor placement or weak entry-point UX.
• Benchmark: A healthy offerwall integration sees 30–60% of DAU viewing the offerwall at least once per day. Below 20% suggests the entry point is not discoverable enough.

2.2 Clicks and Click-Through Rate (CTR)

A click is counted when a user taps on an offer to view its details or begin completion. CTR is clicks divided by impressions.

• What to track: Daily clicks, CTR, clicks per impression.
• What it tells you: Whether the offers shown are relevant and appealing to your users. Low CTR indicates offer mismatch — either the offers don’t match your audience’s interests, or the offer tiles are not visually compelling.
• Benchmark: CTR of 15–25% is typical. Below 10% suggests offer relevance issues. Above 35% may indicate misleading offer creatives (which leads to poor downstream conversion).

2.3 Conversions and Conversion Rate (CVR)

A conversion is counted when a user completes an offer and the postback is validated. CVR is conversions divided by clicks.

• What to track: Daily conversions, CVR, conversions per click, time-to-conversion.
• What it tells you: Whether the offers deliver on their promise. If users click but don’t convert, the offer instructions may be unclear, the completion criteria may be too difficult, or the reward may not be worth the effort.
• Benchmark: CVR of 30–50% is healthy for most offer types. Survey and download offers convert at higher rates; signup and purchase offers convert at lower rates. Compare CVR within offer categories, not across them.

2.4 Revenue

Revenue is the total real-money payout you earn from completed offers. This is the bottom line.

• What to track: Daily revenue, revenue per impression (RPM), revenue per conversion (RPC), revenue per active user.
• What it tells you: The direct financial output of your offerwall. Track it alongside ARPDAU to understand per-user value.
• Benchmark: Highly variable by geo and app category. Games in Tier 1 geos typically see $0.10–$0.50 ARPDAU from offerwalls. Use your own historical data as the primary benchmark.

2.5 ARPDAU (Average Revenue Per Daily Active User)

ARPDAU is revenue divided by DAU. It is the single most important metric for understanding per-user monetization efficiency.

ARPDAU = Total Daily Revenue / Daily Active Users

Example:
  Revenue on Aug 15: $340
  DAU on Aug 15: 12,000
  ARPDAU = $340 / 12,000 = $0.0283

• What to track: ARPDAU trend over time, ARPDAU by geo, ARPDAU by user cohort (new vs returning).
• What it tells you: Whether your monetization is improving or degrading per user. If DAU is growing but ARPDAU is declining, you may be acquiring users in lower-monetizing geos or your offer mix is degrading.
• Benchmark: Track against your own 30-day moving average. A week-over-week decline of more than 15% warrants investigation.

2.6 Fill Rate

Fill rate is the percentage of offerwall sessions that show at least one relevant offer. If a user opens the offerwall and sees zero offers (because no campaigns target their geo, device, or demographics), that is an unfilled session.

Fill Rate = Filled Sessions / Total Sessions × 100

Example:
  Total sessions: 5,000
  Filled sessions (≥1 offer shown): 4,650
  Fill Rate = 4,650 / 5,000 = 93%

• What to track: Fill rate overall, fill rate by geo, fill rate by device type.
• What it tells you: Whether your users have offers available. Low fill rate in a specific geo means users there see an empty wall — a poor UX that trains users not to return. This is especially critical in emerging markets where offer inventory is thinner.
• Benchmark: 90%+ in Tier 1 geos (US, UK, DE, JP). 60–80% in Tier 2. Below 50% in any geo is a red flag — consider whether to show the offerwall entry point at all for that geo.

Metric Relationships

These metrics form a funnel. Understanding the relationships is key to diagnosis:

Impressions × CTR = Clicks
Clicks × CVR = Conversions
Conversions × RPC = Revenue
Revenue / DAU = ARPDAU

Example:
  10,000 impressions × 20% CTR = 2,000 clicks
  2,000 clicks × 40% CVR = 800 conversions
  800 × $0.42 RPC = $336 revenue
  $336 / 12,000 DAU = $0.028 ARPDAU

If ARPDAU drops, walk the funnel backward. Is revenue down because conversions dropped? Is CVR down because clicks dropped? Is CTR down because impressions dropped? Each stage has different root causes and fixes.

3. Understanding the Perkox Dashboard

The Perkox publisher dashboard is organized into several views, each serving a different analysis need.

3.1 Overview Dashboard

The default view shows high-level metrics for the selected date range: revenue, impressions, conversions, ARPDAU, and fill rate. Use this for daily health checks. Key features:

• Date range selector: Today, 7 days, 30 days, 90 days, or custom range. Compare two ranges to spot trends.
• Sparkline charts: Mini-trends next to each metric show direction at a glance.
• App selector: If you manage multiple apps, switch between them or view aggregate.
• Real-time counter: Live impression and conversion counts for the current day.

3.2 Revenue Report

Breaks down revenue by day, geo, offer category, and offer provider. Exportable as CSV. Use this for financial reconciliation and for identifying which offer categories or providers drive the most value.

3.3 Funnel Report

Visualizes the impression → click → conversion funnel with rates at each stage. You can filter by geo, user cohort, or date range. This is your primary diagnostic tool when ARPDAU drops.

3.4 Fraud Signals View

Shows flagged transactions, risk score distributions, and proxy/emulator traffic percentages. Review weekly. High fraud signal rates may indicate a targeted attack on your integration.

3.5 Offer Performance Report

Lists every offer shown to your users with impressions, clicks, conversions, CVR, and revenue. Sortable and filterable. Use this to identify top-performing offers and underperforming ones that waste impression slots.

For a full walkthrough of every dashboard section, see our publisher dashboard guide.

4. Geo-Level Performance Analysis

Geo analysis is where most publishers find their biggest optimization opportunities. Offer availability, payout rates, and user behavior vary dramatically by country.

4.1 What to Look For

• Revenue by geo: Which countries generate the most revenue? Typically, the US, UK, Germany, Japan, and Australia dominate. But long-tail geos can add up.
• ARPDAU by geo: Revenue divided by DAU for each country. This reveals efficiency, not just volume. A country with low DAU but high ARPDAU may be worth localization investment.
• Fill rate by geo: Countries with fill rate below 60% are wasting user attention. Consider hiding the offerwall entry point for those geos or offering an alternative monetization format.
• CVR by geo: Conversion rate varies by country due to offer availability and user behavior. A low CVR in a geo with high CTR suggests offers are appealing but completion criteria are too hard for that audience.

4.2 Geo Performance Table Example

Reading this table: the US and DE are clear winners with high ARPDAU and fill rate. BR has decent volume but low CVR — investigate whether the offer mix matches Brazilian users. IN has high impressions but low fill rate and CVR — the offerwall may not be worth showing to all Indian users. ID has a fill rate below 60%, suggesting the offerwall entry point should be conditionally hidden for that geo.

4.3 Acting on Geo Data

1. Conditional visibility: Only show the offerwall entry point to users in geos with fill rate above a threshold (e.g., 70%). For geos below the threshold, hide the entry point and use an alternative ad format.
2. Offer curation: Some offer providers specialize in specific geos. If a geo is underperforming, check whether additional providers can be enabled for that region.
3. Localization: If a high-ARPDAU geo has low CTR, translating offer tiles and instructions can lift engagement significantly.
4. Geo-targeted rewards: Adjust virtual currency payouts by geo to maintain consistent real-value perception. A 100-coin reward is meaningful in the US but trivial in a high-inflation economy.

For a deep dive on geo strategy, see our geo-targeting strategy guide.

5. Offer-Level Performance Analysis

Not all offers are created equal. Some convert at 60% and pay $0.05; others convert at 10% and pay $2.00. Offer-level analysis helps you understand which offers are worth their impression slots.

5.1 Key Offer-Level Metrics

• Impressions: How often the offer is shown. High impressions with low clicks = the offer tile isn’t compelling.
• CTR: Click-through rate for this specific offer. Compare to the app-wide average.
• CVR: Conversion rate for this specific offer. Low CVR with high CTR = the offer is attractive but the completion criteria are too hard or misleading.
• Revenue per impression (RPI): Revenue / impressions. This is the most useful single metric for ranking offers. An offer with high CVR but low payout may have lower RPI than an offer with moderate CVR and high payout.
• Drop-off rate: Percentage of users who click but abandon before completing. High drop-off may indicate confusing instructions or excessive completion requirements.

5.2 Offer Ranking Example

Offer C has the highest RPI despite low CTR and CVR — the high payout compensates. Offer A has high engagement but low RPI because of the low payout. Offer B is a balanced performer. Offer D has moderate RPI but low volume — it’s not wasting slots, but it’s not a top performer either.

5.3 Acting on Offer Data

• Block underperformers: Offers with RPI below $0.005 and high impression counts are wasting valuable real estate. Block them in the dashboard.
• Promote top offers: Some offerwalls support “featured offer” placement. Pin your top RPI offers to the top of the wall.
• Category analysis: Group offers by category (survey, download, signup, trial, purchase) and compare category-level RPI. This tells you which categories to prioritize.
• Refresh frequency: Offer inventory changes daily. Review the offer performance report weekly to catch new high-performing offers and retire stale ones.

6. A/B Testing with Analytics

A/B testing is how you move from guesswork to evidence. Common offerwall A/B tests include placement changes, entry-point UX variations, reward multiplier events, and offer sorting algorithms.

6.1 Test Design

1. Define the hypothesis: “Moving the offerwall entry point from the home screen to the shop screen will increase ARPDAU by 10%.”
2. Define the metric: ARPDAU over a 14-day window. Use a composite metric — don’t optimize for CTR alone if it hurts CVR.
3. Split users randomly: Assign 50% of users to control (current placement) and 50% to variant (new placement). Use a stable hash of the user ID for consistent assignment across sessions.
4. Run for statistical significance: Depending on your traffic, you need 7–21 days. The Perkox dashboard’s A/B test view calculates significance automatically. Do not call a test before significance is reached (p < 0.05).
5. Guard against novelty effects: A placement change may boost engagement temporarily because it’s new. Run the test for at least 2 weeks to see if the effect persists.

6.2 Common Offerwall A/B Tests

For a complete methodology on placement testing, see our A/B testing and placement guide.

6.3 Reading A/B Test Results

• Uplift: The percentage difference between variant and control. A 10% uplift in ARPDAU on $0.03 baseline is $0.003 per user — meaningful at scale.
• Confidence interval: The range within which the true uplift lies. A narrow interval means the result is reliable. A wide interval means you need more data.
• p-value: Below 0.05 means the result is statistically significant. Above 0.05 means the difference could be noise.
• Secondary metrics: Always check secondary metrics. A placement change that boosts ARPDAU but reduces D1 retention is a net negative. See our retention impact study for methodology.

7. Setting Up Alerts and Reports

Manual dashboard checking does not scale. Set up automated alerts and scheduled reports so you are notified of issues without constantly monitoring the dashboard.

7.1 Alerts

The Perkox dashboard supports configurable alerts via email, Slack, and webhook. Recommended alert configurations:

7.2 Scheduled Reports

Set up the following recurring reports to be emailed automatically:

• Daily summary: Yesterday’s key metrics (impressions, clicks, conversions, revenue, ARPDAU, fill rate) with comparison to the previous day and the 7-day average.
• Weekly geo report: Revenue and ARPDAU by country, with week-over-week change. Sent every Monday.
• Weekly offer report: Top 20 and bottom 20 offers by RPI. Sent every Monday.
• Monthly reconciliation report: Full revenue breakdown by day, geo, and offer category. Sent on the 1st of each month. Used for financial reconciliation.

7.3 Webhook Integration

For teams with internal monitoring (Datadog, Grafana, PagerDuty), configure the Perkox webhook alert to feed into your existing incident pipeline. This ensures offerwall issues are treated with the same urgency as other infrastructure alerts.

// Example webhook payload
{
  "alert": "revenue_drop",
  "severity": "high",
  "app_id": "app_12345",
  "metric": "daily_revenue",
  "current_value": 238.50,
  "threshold": 294.00,
  "comparison": "7d_average",
  "timestamp": "2026-08-22T08:00:00Z"
}

8. Common Analytics Mistakes

Even experienced publishers make analytical errors. Here are the most common ones and how to avoid them.

8.1 Optimizing for CTR Alone

High CTR looks great, but if CVR drops correspondingly, you are showing attractive-but-unsatisfiable offers. Always optimize for a downstream metric (revenue, ARPDAU, or RPI), not an intermediate one. A/B test winners should be determined by the metric closest to your business goal, not the metric easiest to move.

8.2 Ignoring Fill Rate

Many publishers focus on conversion metrics and ignore fill rate. But if 40% of your users in a key geo see an empty offerwall, you are training them not to check it again. Fill rate is a leading indicator of engagement — track it before it becomes a retention problem.

8.3 Comparing Geos Without Normalizing

Comparing raw revenue across geos is misleading. The US will always generate more revenue than Argentina because of DAU and payout differences. Always compare ARPDAU and fill rate, not absolute revenue, when evaluating geo performance.

8.4 Calling A/B Tests Too Early

Day 3 of an A/B test shows the variant winning by 20%. You ship it. By day 14, the control has caught up and the variant is actually 2% worse. This is a novelty effect combined with insufficient statistical power. Always wait for the dashboard’s significance indicator before acting.

8.5 Not Segmenting New vs Returning Users

New users interact with the offerwall differently than returning users. New users may not know what it is; returning users may have already completed the easy offers. Track ARPDAU separately for new and returning cohorts. If new-user ARPDAU is declining, your onboarding may not be introducing the offerwall effectively.

8.6 Ignoring Time-to-Conversion

Some offers convert in minutes (surveys); others take days (game level offers). If you evaluate a 7-day window but your top offers have 14-day completion cycles, you are undercounting their value. Use a 14-day or 30-day attribution window for revenue reporting, and a 1-day or 3-day window for funnel diagnostics.

8.7 Trusting Day-of-Week Averages

Offerwall performance varies by day of week. Weekends often show higher engagement for games. A Monday-to-Sunday average hides this. When comparing periods, align by day of week (e.g., compare this Monday to last Monday, not this Monday to the 7-day average).

9. FAQ

What is ARPDAU and why is it the most important offerwall metric?

ARPDAU (Average Revenue Per Daily Active User) is your total daily offerwall revenue divided by your daily active users. It is the most important metric because it normalizes revenue by audience size, letting you compare performance across apps, geos, and time periods regardless of traffic fluctuations. A rising ARPDAU means your monetization is getting more efficient; a falling ARPDAU means you need to investigate the funnel.

How do I track offerwall revenue separately from other ad revenue?

The Perkox dashboard tracks offerwall revenue independently. For your internal analytics, tag offerwall postbacks with a distinct revenue source in your server-side logging. If you use an ad mediation platform, configure a separate waterfall entry for offerwall revenue. Never mix offerwall revenue with banner or interstitial revenue in reporting — they have different economics and require separate optimization.

What is a good fill rate for an offerwall?

90%+ in Tier 1 geos (US, UK, DE, JP, AU) is healthy. 70–90% in Tier 2 geos is acceptable. Below 60% in any geo means users are seeing an empty wall too often, which damages long-term engagement. For geos below 60%, consider hiding the offerwall entry point or enabling additional offer providers that serve that region.

How long should I run an offerwall A/B test?

Minimum 14 days for most tests, and until the dashboard reports statistical significance (p < 0.05). Tests involving retention or long-cycle offers may need 30 days. Never call a test before significance is reached — early results are dominated by novelty effects and noise. Always check secondary metrics (retention, session length) alongside the primary metric to avoid shipping a change that boosts revenue but hurts engagement.

How do I set up revenue drop alerts?

In the Perkox dashboard, navigate to Alerts > Create Alert. Select “Revenue drop” as the alert type, set the threshold (e.g., daily revenue below 70% of the 7-day moving average), choose your notification channel (email, Slack, or webhook), and save. The alert fires automatically when the condition is met. Pair it with a fill rate alert and a postback failure alert for comprehensive coverage.

Turn Data into Revenue

Analytics is the bridge between integration and optimization. You have the metrics, the dashboard, and the methodology — now put them to work.

• Start tracking: Log in to the Perkox publisher dashboard
• Full metrics reference: Perkox developer documentation
• Dashboard walkthrough: Publisher dashboard guide
• Optimize with A/B testing: A/B testing and placement guide
• Retention impact: Offerwall retention impact study

Measure what matters, act on what you measure, and your offerwall revenue will compound over time.