Not really, we like to think of a “latency budget” for every placement. Modern bidding is fast, and most apps have more than enough time to complete an auction before an impression is needed.

What we do is determine the approximate amount of time available and use it to your advantage. We optimize within your latency budget to maximize revenue without affecting KPIs.

Why wouldn't you?

App weight indeed varies with SDKs, meaning that final weight will depend on the amount of providers (mediations, networks) that the developer wants to include. As relates specifically to our SDK, the weight is approximately 4MB for both platforms (unlikely that it will have a big overall impact).

Yes, in order to get the most out of Loomit you may need to add other SDKs as well (if you’re going to run two mediations, then we’ll need those SDKs for example).

In this regard, we look at every app as a unique case and consider issues like stability, weight, compatibility and potential upside. More importantly, going forward our clients can manage these SDKs (how/when/if they’re used) through our platform, meaning way fewer integrations in the future.

The opposite, this is probably way better than what you did in the past. On one hand, we’ve made public our tool to ensure dependency compatibility across mediations and networks (check it out here). Using it helps navigate part of what used to be a headache by reducing the amount of times you set up and fail to launch.

What’s more, working with Loomit means that you can roll out your test like never before. Whereas you’d typically manage rollouts by slowly increasing traffic, our clients have the option to control the geo or user cohort that “tests” stability as well. 

Being able to do all this without the need to implement code, using real-time data and with the support of our outstanding Operations team makes for a seamless experience. This is exactly what makes us stand out.

Yes and no. First and foremost, it really depends on Applovin. Our experience indicates that Applovin asks for 100% of your traffic to be mediated by them in order to run ads ROAS campaigns, so if you were planning to use Loomit to access multiple mediations then the answer would be no.

On the other hand, not all of our solutions encourage the use of more than one mediation. We have plenty of Applovin only clients and we’re still able to deliver great results through Loomit. One of our clients, for example, relies on Loomit to manage a phase-in period for new users (which it uses to identify potential buyers). Once the phase-in period is over, ad-requests start being triggered for all users not identified as potential buyers. Those tagged as buyers go through a different journey involving less / no ads depending on the case.

This can all be set up through our dash, sending 100% of the inventory through Applovin and can be constantly modified / tested without the need to implement code changes.

Yes, of course. As a suite of pre-built adtech tools, Loomit enables clients to create the setups they want and this may include prebid / postbid.

Each mediation has its own set of rules and we encourage our clients to comply with the rules of the providers they choose to work with. We offer a broad set of tools, not all of which are allowed by all mediations and it’s important to check before implementing complex setups.

In the case of prebid and postbid for example, we have clients who use X3M Mediation who choose to create postbid setups for a specific network after the mediation. That’s perfectly ok with X3M.

Other tools, such as those that limit triggering requests according to the tags associated to different user cohorts are simply there to help studios determine WHO is monetized and are perfectly acceptable to all providers.

Of course, and many do. As a matter of fact, you could probably build most of the tools you pay for. That said, building this is hard, it takes time, needs maintenance and even then benefits from a holistic industry view to continue building.

Our guess is that you’re probably better off relying on a third party to provide this to you. Give us a call and let’s discuss. 

There are two key considerations here. First, you’re probably organizing your backlog using an “odds of success” estimation combined with “impact if successful” to maximize expected return.

If we can agree on the fact that having a single admon strategy across your user base is unlikely to be the best possible setup, then we can agree that “odds of success” for Loomit are as close to 100% as anything you’ve ever done. We enable infinite potential admon setups to extract more value going forward.

Second, this is the last adtech integration you’ll ever make. Testing setups without Loomit forces the AdOps team to compete for dev muscle in order to implement things (which may or may not work, need to be rolled back, etc). Through Loomit, AdOps is empowered to work using powerful new tools and setup combinations without the need to rely on new code. This added flexibility does wonders for the bottom line.

We’ve seen this implemented within a week. What else can you do in a week with these odds?

Of course. We’re agnostic as to how you sell ads and that applies not just to mediations or networks. We don’t want to get technical as to how we’d set it up (there’s several ways), but of course we’d help you implement direct transactions through Loomit.