An app-to-web campaign is a performance advertising setup where users are served ads inside mobile apps and, upon clicking the ad, are redirected to a mobile browser to complete the rest of the funnel.
A typical flow looks like this:
A video, display, or native ad is shown within an app
The user clicks the ad
The user lands on a browser-based landing page
The user proceeds to the offer page
The user completes an action such as signup or purchase
This model is widely used for e-commerce, lead generation, and direct-response offers.
During an app-to-web journey, multiple trackable events can occur. Common examples include:
Ad View – Impression
Ad Click – Click
Landing Page Visit
Landing Page → Offer Page Click
Form Fill / Partial Signup
Successful Purchase
GSM360 directly tracks impressions and clicks.
All downstream events are tracked via third-party trackers such as Voluum, RedTrack, or Keitaro and can optionally be sent back to GSM360 for optimization and reporting.
GSM360 supports multiple optimization types for app-to-web campaigns:
CPM – Cost per 1,000 impressions
CPC – Cost per Click
CPI – Cost per Install
CPA – Cost per Action (currently in development)
Each model serves different campaign goals.
With CPM optimization, the platform focuses on buying impressions at the most efficient cost possible.
Best suited for scale and testing
No conversion event is mandatory
Ideal when paired with manual or rule-based optimization
In CPC optimization, you define:
A target CPC
A maximum CPM bid
Although billing remains on a CPM basis, GSM360’s algorithm optimizes delivery to achieve clicks within your CPC target.

Best practices:
Allow the campaign to reach at least 500 clicks before evaluating performance
Use CPC when click quality is a strong predictor of downstream conversions
Native and Banner Campaigns work best with CPC optimization type
Passing conversion events back to GSM360 is optional for CPM and CPC campaigns.
However, sending events from your tracker allows you to:
Monitor earnings and ROAS
Identify high-performing placements
Manually optimize campaigns more effectively
For CPM campaigns, GSM360 offers a Rule Engine that enables:
Automated blacklisting of underperforming placements or app bundles
Performance-based conditions aligned with your KPIs
The Rule Engine is available only for CPM campaigns, not for CPC or CPI.In CPI optimization, you define:
A target CPI
A maximum CPM bid
Although billing remains on a CPM basis, GSM360’s algorithm optimizes delivery to achieve installs within your CPI target.

Best practices:
Allow the campaign to reach at least 200–300 installs to allow the algorithm sufficient learning
To use CPI optimization, sending an install event to GSM360 is mandatory.
Install Postback URL Format:
Example:
Key requirements:
Other trackers such as RedTrack and Keitaro follow a similar setup with minor variations.
You can send up to 10 additional post-install events to GSM360 for deeper visibility and manual optimization. In order to do that, just follow the steps below.
Typical ExamplesSome typical examples of how these postbacks look like using the events that we took as an example at the beginning of this article -
Once configured:
Event counts appear in GSM360 reporting
If payout values are sent, Earnings and ROAS are automatically calculated
(ROAS = Earnings ÷ Cost)
GSM360 is actively working on CPA-based optimization, where delivery will be optimized against two advertiser-defined post-install events.
More details will be shared as this feature approaches release.
GSM360’s app-to-web framework gives advertisers flexibility to:
Start with CPM or CPC for scale and learning
Move to CPI for algorithmic performance
Use post-install events and rule engine for manual optimization
Choosing the right optimization model - and passing the right signals - can significantly improve efficiency, ROAS, and scalability.