Campaign overview
This anonymized customer campaign focused on mobile game installs and engaged user acquisition in Italy. The buyer used In-Page Push Ads through FroggyAds and reported 101,102 generated clicks, 3,096 reported conversions, $63,919 in gross revenue and $39,889 in net profit. The resulting 166% ROI is calculated as net profit divided by media spend.
The headline result came from a campaign that had to operate across 839 active publishers with a reported average bid win rate of 60.6%. Those delivery figures describe market access, not automatic quality. The customer still needed to identify which combinations of source, device, creative and landing experience produced commercially accepted outcomes.
An install can be inexpensive while retention and in-game value remain weak. The campaign needed events after first launch.
Italian messaging was aligned across the ad and destination, with source-level reporting used to distinguish traffic scale from accepted customer value.
The buyer kept enough separation between creative, source and device variables to understand why performance changed rather than reacting to one blended dashboard average.
What the record demonstrates
A controlled combination of offer fit, localization, tracking, creative testing and source-level optimization produced a profitable historical result. It does not guarantee the same outcome for another advertiser.
The acquisition challenge
The implied cost per verified conversion was $7.76, while gross revenue averaged $20.65 per verified conversion. Those two figures created the working space for media cost, operational variance and downstream quality. A source could not be judged only by its click price because a cheap click with weak conversion value would still consume the margin.
The campaign produced a calculated 3.06% click-to-conversion rate and $0.632 in gross revenue per click. The buyer used these values as reconciliation points, not universal targets. Device mix, source pricing and conversion delay could change the same ratios even when the offer stayed constant.
The record also shows why test design matters in Italy. A broad launch was useful for discovery, but a broad campaign left unchanged would have mixed high-value cohorts with segments that had not yet earned additional spend. The customer therefore moved from exploration into more isolated source and device groups.
Creative should represent actual gameplay and disclose material purchase or eligibility conditions where required.
Campaign setup and targeting
In-page push combined a notification-style message with on-page inventory, allowing broad browser reach without depending on an existing push subscription.
Creative variants were grouped by promise and audience problem. The buyer tracked each message through to the landing page so a strong click rate could not hide a weak conversion path.
The campaign preserved the supplied CID MOBI-IT-007 as the reference for the analyzed record. Source identifiers, creative identifiers and conversion feedback were treated as a connected measurement path. That allowed the buyer to compare the original traffic purchase with the customer outcome rather than optimizing from disconnected reports.
The starting structure gave In-Page Push Ads enough breadth to test delivery while keeping the acceptable loss explicit. Publisher segments that accumulated spend without a verified outcome were candidates for reduction, while segments with repeatable conversions could move into separate scale groups.
The reported 60.6% average win rate was interpreted together with source quality. Raising bids could improve access to a segment, but it could also change the auction mix. The buyer reviewed performance again after material bid or budget changes instead of assuming the original efficiency would remain constant.
- GEO: Italy (IT)
- Format: In-Page Push Ads
- Primary objective: User acquisition
- Campaign reference: MOBI-IT-007
- Reported publisher coverage: 839
- Average bid win rate: 60.6%
Tracking and data quality
Server-to-server conversion feedback connected the advertiser-side event with the campaign click and source identifiers. This reduced dependence on browser-only signals and helped the buyer distinguish a delivery problem from a tracking or landing-page problem.
The source document describes a fast, geographically distributed landing setup with a target time to first byte below 120 milliseconds. The practical lesson is not that one latency number guarantees conversion. It is that redirects, script weight and unstable mobile rendering can create apparent traffic-quality issues that begin on the advertiser side.
The customer reconciled the reported 3,096 conversions with the accepted business event for mobile gaming. FroggyAds traffic-quality controls can reduce exposure to invalid activity, but they do not replace advertiser-side validation, duplicate handling or downstream acceptance rules.
The campaign’s calculated CPC of $0.238 was useful for budget planning, while the $7.76 cost per verified conversion remained the more important commercial boundary. The difference between those metrics shows why optimization stopped at neither impressions nor clicks.
Conversion maturity was included in the decision process. A segment that appeared weak before delayed events arrived could be removed too early, while a strong early cluster could look better than it was if later quality or refund data had not matured.
