CPI & CPE Revenue Models Explained
Learn how BitLabs calculates publisher payouts and user rewards across CPI, CPE, and hybrid campaigns, including margin management and how to identify install-based payouts.
Revenue Models
BitLabs provides game and offer campaigns using one or both of the following revenue models:
- CPI — Cost per Install
- CPE — Cost per Event
The revenue model determines when the publisher earns revenue and when the user receives rewards.
Prodege operates on a revenue-share model, meaning that you receive an agreed percentage of the revenue generated by Prodege. Your payout follows the same revenue model as Prodege’s: when Prodege is paid on an install through CPI, you also earn on the install; when Prodege is paid for completed events through CPE, you earn when those events are completed.
CPI Campaigns
With a CPI campaign, the publisher earns revenue when a user installs the advertised game or app.
The publisher receives the install payout upfront, while the user generally receives rewards later as they progress through the offer and complete specific events.
For example:
- The user installs a game.
- The publisher receives the CPI payout.
- The user continues playing the game.
- The user receives rewards for reaching levels, making progress, or completing other offer requirements.
For most CPI campaigns, the progression events do not include an additional publisher payout. These events are primarily used to grant rewards to the user.
CPE Campaigns
With a CPE campaign, neither the publisher nor the user earns anything from the initial install.
Instead, both the publisher and the user earn when the user completes individual events after installing the game or app.
These events may include:
- Reaching a specific level
- Completing a tutorial
- Making a purchase
- Playing for a certain number of days
- Completing another defined in-app action
Each completed event can include:
- A reward for the user
- A payout for the publisher
Hybrid CPI and CPE Campaigns
Some offers use both CPI and CPE.
For these campaigns:
- The publisher earns an initial payout when the user installs the app.
- The publisher may also earn additional revenue when the user completes certain progression events.
- The user receives rewards for completing the defined events.
The exact payout structure can differ between offers, so publishers should inspect the event data for each campaign.
Why Can User Rewards Be Higher Than the CPI Payout?
In most cases, the total value of all rewards shown to the user will be significantly higher than the revenue generated from a single install.
This is intentional and part of the CPI model.
Users progress through offers at different rates:
- Some users install the app but complete no additional events.
- Some users complete only the first few events.
- Some users progress much further.
- Only a small percentage of users complete every available event.
As a result, the maximum reward displayed for an offer is not paid to every user.
The difference between the upfront CPI revenue and the rewards actually distributed across all users allows the campaign to remain profitable. Based on current performance, this model typically results in an approximate gross margin of 40%.
Margin Management
The BitLabs team manages the publisher’s overall margin across the available CPI campaigns.
The standard target margin is generally 40%, but this target can be increased or decreased in coordination with the BitLabs team.
Margin may fluctuate over shorter periods because of factors such as:
- User progression behavior
- Campaign performance
- Changes in offer availability
- Differences between user cohorts
- Delayed event completions
Publishers should therefore evaluate margin over a longer period rather than based on an individual install, offer, or day.
Over time, BitLabs will optimize campaign delivery and reward values toward the agreed target margin.
Why Use CPI Campaigns?
The primary advantage of CPI campaigns is that publishers receive revenue much earlier in the user journey.
Instead of waiting for users to progress through multiple events, the publisher earns as soon as a qualifying install is completed.
This provides several benefits:
Faster revenue generation
Publishers receive a larger portion of the expected campaign revenue immediately after the install.
Faster return on investment
Publishers running user-acquisition campaigns can recover their acquisition costs more quickly because revenue is generated at the beginning of the offer journey.
Easier campaign planning
Upfront install revenue makes it easier to estimate:
- Revenue per acquired user
- Payback periods
- User-acquisition budgets
- Campaign profitability
- Cash flow
Reduced dependency on long-term user progression
With a pure CPE model, publisher revenue depends on users continuing to play and completing later events. CPI campaigns reduce this dependency by monetizing the initial install.
How to Identify a CPI Offer in the API
To determine whether an offer includes an install-based publisher payout, inspect the offer’s events.
1. Find the install event
Look for an event with:
type_id = 1A type_id of 1 represents the INSTALL event.
2. Check the payout
Inspect the payout field for the install event.
3. Determine whether the offer pays on install
- If
payout > 0, the publisher receives payment when the user installs the app. - If
payout = 0, the publisher does not receive an install-based payment.
In most CPI campaigns, the regular progression events will not contain an additional payout amount.
Understanding the Points and Payout Fields
The event data contains separate values for the user reward and the publisher payout.
points
pointsThe points field represents the amount earned by the user in the publisher’s configured reward currency.
Depending on the integration, this may be displayed as points, coins, credits, or another virtual currency.
payout
payoutThe payout field represents the amount earned by the publisher in USD.
These fields should not be interpreted as equivalent values. The user reward is based on the offer’s reward structure and the configured currency conversion, while the publisher payout is based on the campaign’s commercial payment model.
Summary
| Payment model | Publisher earns on install | User earns on install | Publisher earns on events | User earns on events |
|---|---|---|---|---|
| CPI | Yes | Usually no | Usually no | Yes |
| CPE | No | No | Yes | Yes |
| CPI + CPE | Yes | Usually no | Yes, for selected events | Yes |
CPI campaigns provide publishers with faster and more predictable revenue, while BitLabs manages reward distribution and long-term profitability toward the agreed margin target.
Updated about 12 hours ago

