The usual traffic sources can be unstable from time to time: some markets close, some conditions change, and in some channels it becomes harder to scale without losing traffic quality. That is why traffic diversification is no longer a “nice to have someday” idea, but a normal working strategy for teams that want to maintain volume and avoid depending on a single channel.

One source that is definitely worth paying attention to right now is Mintegral. It is an In-App platform with event-based optimization, broad targeting options, and a clear scaling logic.

But instead of theory, let’s get straight to practice.
In this case study, we’ll break down how a team with a licensed iGaming product entered Mintegral Ads with a $2,000 test budget, started with an Android app, later added iOS, and reached $22,000+ in monthly spend within a few months.

The result for the period: $62,785 in ad spend, an average ROI of 29.8%, 508 purchases within 7 days after install, and a CPA of $123.59.
This is the first Mintegral case study on the market that we can share with real inputs, numbers, and launch logic. Thanks to our clients for allowing us to share this experience and show how the source works in practice.

Case inputs

Source: Mintegral
Operating system at launch: Android
Launch country: Czech Republic
Vertical: iGaming
Offer: licensed iGaming product
App: licensed app
Team: experienced In-App team, but with no previous Mintegral launch experience
Test budget: $2,000
Work period: February 2026 — present

The team had already worked with In-App traffic and launched its own apps in other sources. They had apps, creatives, and MMP statistics for registrations, deposits, and FTDs, but Mintegral was being tested for the first time.

So the goal was not to “learn In-App from scratch,” but to carefully test a new source: understand its traffic quality, test formats, check how event-based optimization works, and assess whether it could gradually move into stable volume.

Why Android was chosen for the first test

The first launch was made with an Android app.

Android is usually cheaper to test and gives access to more available traffic. For checking a new In-App source, this is a convenient starting point: the team can quickly understand whether the integration works correctly, whether events are coming through, whether there are first conversions, and how the source behaves in the selected market.

At the start, the account was topped up with $2,000. The goal was not to scale volumes immediately, but to test Mintegral in real conditions, collect the first data, and only then decide whether it made sense to expand the launch.

For a new source, this is a normal approach: first technical setup, events, and quality — then scaling.

Why the campaign was launched straight to an event instead of CPI

Since the apps had already been running in other In-App sources, the team had accumulated MMP statistics for registrations, deposits, and FTDs.

After the integration was set up correctly, Mintegral allowed the team to launch directly with TCPE optimization, without having to start with CPI first.

FTD was selected as the main event. Additional events were also matched:
— app login;
— registration;
— deposit.

The more correct data the source receives, the easier it is for the system to understand user behavior and optimize media buying.
At the start, the target FTD cost was set above the KPI — around 120% of the desired cost. For example, if the team’s target FTD was $100, the campaign was launched with $120.

This was done intentionally. The team wanted to enter the auction a little more aggressively, get delivery faster, and collect enough data to evaluate source quality. At the first stage, it was more important not to squeeze the bid too hard right away, but to give Mintegral enough room to learn.

Creatives: the team moved over what already worked in In-App

At the start, the team did not build a creative strategy from scratch.

They were already running In-App traffic in other sources and understood which formats performed better. For Mintegral, they decided to move over proven combinations:
— video + end card;
— video + playable end card.

Each campaign included 3–6 creatives. This allowed the team to avoid launching with just one hypothesis, while also keeping the test controlled enough to understand what actually drove the result.

This approach works well for a new source: take a working base, adapt it to the platform, and see how Mintegral distributes traffic across creatives.

Targeting: why the team started broad

IThe campaigns were launched with a broad audience.

At the start, the team did not touch gender or age in order not to reduce reach without enough statistics. The only limitation was targeting a higher OS version from the beginning.

Why?
In-App sources do not always know enough about users for gender and age targeting to work perfectly. Sometimes these settings do not improve conversion, but simply narrow the audience and increase buying costs.

So the team started broad: first collect statistics, then optimize by ad inventory, apps, and app categories.

First stage: small budget, event and integration check

During the first 2–3 days, the campaign had a small daily budget of around $100.

At this stage, the team was not checking volume, but the basics:
— whether events were being recorded correctly;
— whether the source could see registrations and FTDs;
— whether there were any integration issues;
— how delivery was being distributed;
— which creatives started taking spend.

After the first registrations were tracked correctly, the daily budget was increased to $200–400 and then kept roughly within that range.

This became the working pace for the test: enough to collect data, but without aggressive scaling that could burn the budget before proper analysis.

Why the team did not chase 10–30 events per day

Mintegral recommends collecting around 10–30 events per day per campaign for more effective optimization.
The team decided not to follow this recommendation literally.

On one hand, the more data the source receives, the better optimization can work. On the other hand, In-App sources do not always understand the user deeply enough for a simple budget increase to reduce CPA several times over.

So the team chose a calmer strategy: not to “spend until it works,” but to deliver gradually, monitor quality, optimize creatives, build blacklists, and lower TCPE as more statistics came in.

The working model looked like this:
— $200–400 daily spend per campaign;
— 3–6 creatives in rotation;
— creative refresh roughly once every 1.5–2 months;
— optimization through app blacklisting;
— gradual TCPE reduction after enough data was collected.

Optimization in Mintegral: what the team did during the launch

The team did not change everything chaotically. The work moved in several clear directions: inventory, creatives, bid, and event quality.

App blacklisting
At the start, the team did not have a ready blacklist for Mintegral. So part of the budget went into collecting statistics and understanding which apps delivered quality traffic and which ones should be excluded from delivery.
As data accumulated, the team analyzed ad inventory performance by OS and country. If a specific app consistently showed weak performance or low-quality traffic, it was added to the blacklist.

This gradually formed their own list of inefficient inventory.
For a first launch in a new In-App source, this is a normal situation. Without your own data, it is impossible to clean inventory perfectly in advance, so the blacklist is built based on actual results.

Working with creatives
The campaign kept 3 to 6 creatives in rotation. After enough spend was collected, weaker options were removed from delivery, while stronger ones remained active.

The team allocated around $100–200 to test one creative. That was enough to understand whether the angle had potential without spreading the budget too thin.
Creatives remained one of the key factors behind the result. Mintegral can provide volume, but the economics still depend on how well the creative catches the user and moves them toward the target action.

Gradual TCPE reduction
At the start, TCPE was set above the KPI — around 120% of the desired FTD cost. After 2–3 weeks, once more statistics had been collected, the team began gradually lowering the bid.

First, they reached the target cost, and after about a month they managed to bring it down to around 80% of the desired cost.
Daily volume did not drop. This was a strong signal that the source had started to hold the economics better than at the beginning.

Scaling: launching iOS and expanding volume

In the fourth week, the team launched the iOS app.

The logic was fully repeated:
— TCPE as the campaign type;
— video + playable;
— video + end card;
— 3–6 creatives in the campaign;
— $200–400 daily spend;
— gradual optimization by inventory and creatives.

Scaling did not happen through a sharp budget jump, but through careful expansion: first Android, then iOS, then new campaigns, creatives, and gradual spend growth.

iOS turned out to be more expensive than Android, but it still helped increase the overall volume. Additional formats also brought extra reach, although they were not always as effective as the main combinations: video + end card and video + playable.

Monthly spend dynamics

After the test budget, the team continued working with the source and gradually increased volumes.
Monthly spend:
— February: $8,291.409;
— March: $15,279.284;
— April: $17,210.982;
— May: $22,003.346.

Spend from February to April

Spend in May

The growth was gradual. The team did not try to force Mintegral with budget, but moved through optimization, TCPE reduction, creative updates, and campaign expansion.
This approach helped preserve traffic quality and avoid breaking the economics during growth.

Final case results

Over 4 months, the team spent $62,785 in ad budget and reached an average ROI of 29.8% across the full period.

During this time, the campaign generated:
— 409 purchases on the day of app install;
— 508 purchases within 7 days after install;
— average 7-day CPA — $123.59.

Looking at the dynamics, the source gradually became stronger. Spend increased from $8,291 in February to $22,003 in May, while ROI did not drop — it grew to 33.8%. CPA also decreased: from $135.92 in February to $119.58 in May.

This shows that Mintegral did not just provide test volume. It moved into stable buying with budget growth, positive ROI, and an improved purchase cost.

What the team had to account for during the launch

The case was successful, but the result did not appear by itself. The team had to go through several working stages that are normal for a new In-App source: collect statistics, check traffic quality, test creatives, and find a comfortable scaling pace.

Traffic quality should be checked at the app level
Mintegral can provide volume, but inventory quality needs to be controlled. At the start, part of the budget went into collecting app-level statistics to understand which placements were worth keeping and which ones should be excluded.
This is one of the key points in In-App buying: it is important to look not only at overall CPA or ROI, but also at which apps generate events and which ones simply take spend.

Creatives still matter
Even if a format has already worked in other In-App sources, that does not guarantee it will perform equally well in Mintegral.
Some creatives did not deliver the required conversion, so they were turned off after testing. The working creatives were the ones that produced not just clicks and installs, but further events: registrations, deposits, and purchases.

Scaling within one country limits flexibility
The team worked within one country. This limited scaling options: they could not simply open several additional markets in parallel and quickly add volume through new traffic pockets.

So growth came through more careful steps:
— first Android;
— then iOS;
— additional ad formats;
— targeting and OS version work;
— bid and daily budget management;
— inventory optimization.

Not every budget increase leads to better results
The team tested an increase in daily budget. At one point, the Android budget was raised to $800 per day, but twice this worsened conversion: the source started buying broader inventory more actively, and quality dropped.
After that, the team returned to a safer range and understood that for this setup, it was more comfortable to keep daily spend up to $500.

The team did not try to scale at any cost. When budget growth worsened traffic quality, they returned to a comfortable daily spend, cleaned inventory, updated creatives, and continued optimizing campaigns gradually. This approach helped keep ROI positive.

What to check before launching Mintegral

Mintegral can be a strong source for teams that already understand In-App and are ready to work with event-based optimization.

But it is not worth entering blindly.
Before launch, it is important to:
— set up MMP integration correctly;
— match key events in advance;
— choose the event for TCPE optimization;
— avoid setting the starting bid too low;
— avoid overloading the campaign with narrow targeting before you have statistics;
— upload several working creatives;
— regularly clean ineffective apps;
— reduce TCPE gradually, not immediately;
— evaluate the source by event quality, not only by delivery volume.

How Profit Rental helps with Mintegral launches

Mintegral should not be treated as a source where you “just launch and wait.” It is a tool where results come through calm optimization: events, creatives, blacklists, bids, and gradual volume expansion.

Mintegral can now be tested not only with a license. This makes it easier for teams to enter the source if they want to test the platform without lengthy preparation at the start.

We do not guarantee approval, but we can review your inputs in advance, advise on preparation, and help you go through the process as correctly as possible.

Profit Rental helps with the operational side of the launch:
— Mintegral accounts;
— top-ups;
— event setup;
— launch preparation;
— launch support;
— scaling support.

Conclusion

In this case, Mintegral worked as a stable In-App source for gradual scaling.
The team started with an Android app and a $2,000 test budget, checked the technical setup, events, and first registrations, then reached a working daily spend of $200–400 per campaign and gradually increased volumes.

The key factors behind the result were:
— launching directly on TCPE;
— optimizing for FTD;
— using already proven In-App formats;
— broad start without unnecessary audience narrowing;
— app blacklisting;
— creative work;
— gradual TCPE reduction;
— careful scaling through new campaigns and an iOS app.

Over several months, the team managed to grow spend from the test budget to $22,000+ per month without breaking the economics through aggressive scaling.

Mintegral is worth testing for teams that already understand In-App, know how to work with events, and are ready to optimize not only by bid, but also by inventory, creatives, and user quality.

If you want to launch campaigns in Mintegral without unnecessary operational work, message the Profit Rental bot. We will help with the account, top-up, event setup, and support so you can move from test to profit faster.

Share: