# Cost per install: formula and what it measures

> Calculate app cost per install and distinguish that event from an activation or a customer.


**In app marketing, CPI usually means cost per install: advertising spend divided by the installs attributed to a campaign by a chosen source.** The acronym depends on context; here it refers to user acquisition for an app. Use spend and attributed events from the same source, campaign, and measurement window.

## Calculate CPI for a campaign

Suppose an app campaign records **CLP 1,200,000** in spend and its report attributes **300 completed installation events** to the campaign during the same window. These are attributed events, not necessarily 300 new or unique people. Effective CPI is:

> Effective CPI = advertising spend ÷ attributed installs
> CLP 1,200,000 ÷ 300 installs = CLP 4,000 per attributed install

This is a hypothetical example. Google Ads describes CPI as payment per app installation and a maximum average bid for CPI bidding campaigns in [its official definition](https://support.google.com/google-ads/answer/13278731?hl=en). In a post-campaign analysis, divide spend recorded by the report by the attributed events you define; do not assume the bid, invoice, and effective cost are always the same amount.

## Define what counts as an install

The app store, ad platform, or measurement provider may report different events: an initial download, a redownload, or a first open, among others. Apple distinguishes these metrics in its [App Store Connect definitions](https://developer.apple.com/help/app-store-connect-analytics/reference/metrics-definitions/). In that usage report, completed installations include redownloads on the same device, installations on multiple devices sharing an account, and Family Sharing installations. Usage totals are based on users who opt in to share their data. This is Apple’s specific definition, not a universal denominator that always represents a new person who started using the app.

Before comparing CPI, record the report name, counted event, attribution source, window, campaign, and included spend. If one provider reports first opens and another completed downloads, label each cost with its event. Do not add installs from reports that may attribute the same event to different sources.

## CPI is not activation or customer cost

Imagine that, among the same 300 attributed installs, the report records **45 initial in-app activations** during that window. In this example, each activation is linked to an installation identifier in that group and counted at most once per identifier; this is not a count of unique people. Spend per activation would be **CLP 1,200,000 ÷ 45 = CLP 26,666.67 per activation**. This uses a different denominator and answers a different question. It does not turn the CLP 4,000 CPI into cost per active user or customer; those outcomes and their associated costs would need their own definitions.

In this case, compare the approximately CLP 26,667 per activation with the activation cost goal set before the campaign. If you had not set that criterion, the 45 activations describe the result but do not yet justify increasing the budget because CPI appears low.

If the report counts zero installs, CPI is undefined because division by zero is not possible. Record spend and zero events separately. When comparing campaigns, keep the event definition, attribution, window, and cost scope consistent, then check which installs go on to activate or purchase. CPI describes the cost of the selected event; by itself it does not establish acquisition quality or business performance.

The cover is an AI-generated illustration.

## Plan your next post in HeyMark.

Keep the idea, review the draft with your team, and see how it performed in the accounts you connected.

[Start free](https://app.heymark.ai) · [See how it works](https://heymark.ai/en/#product)

## Developer and agent resources

- [HeyMark MCP documentation](https://heymark.ai/en/mcp/)
- [llms.txt](https://heymark.ai/llms.txt)
- [Full site content for language models](https://heymark.ai/llms-full.txt)
- MCP protocol endpoint: `POST https://mcp.heymark.ai`
- OAuth protected-resource metadata: [/.well-known/oauth-protected-resource](https://mcp.heymark.ai/.well-known/oauth-protected-resource)
- MCP server card: [/server-card](https://mcp.heymark.ai/server-card)
