Things just ain’t the same for mobile. Times are changing, and signals are disappearing.

We recently outlined what mobile marketers need to know about the Android Privacy Sandbox. Now, we turn our lens toward publishers.

Google’s Android Privacy Sandbox isn’t just another update — it’s a fundamental overhaul of mobile ad infrastructure enhancing user privacy, and impacting how ads are served and measured. But as with any ad tech update, every overhaul comes with both opportunity and complexity. This guide aims to break down these changes, offering a balanced view of what publishers can expect — and what they should watch out for along the way.

What’s Really Going On Inside the Android Privacy Sandbox?

Android Privacy Sandbox is Google’s response to the increasing demand for user privacy. It’s designed to create a delicate balancing act of protecting personal data while still enabling effective advertising.

For publishers, the transition requires rethinking how ads are targeted and measured. While Google presents the Sandbox as a solution to the privacy dilemma, it’s critical to assess whether it meets publishers’ needs without introducing new challenges.

Can it live up to the mobile IDs of the past? Is this really the silver bullet it claims to be?

Core Objectives:

Protecting User Privacy: While this is crucial, what happens to data granularity and advertiser effectiveness when third-party access is restricted?

Balancing Personalization with Privacy: Can the Sandbox deliver personalized ad experiences without compromising user privacy? This is the tightrope that the Sandbox attempts to walk — relevance without invasiveness.

Redefining Measurement Tools: The new APIs promise precise metrics, but the transition might come with trade-offs in data richness and complex implementation.

Showdown: Android Privacy Sandbox vs. SKAdNetwork vs. Ad Attribution Kit

Why pit the Android Privacy Sandbox against Apple’s SKAdNetwork and Ad Attribution Kit? Because they all address balancing privacy with effective advertising — but in distinct ways. By understanding these differences, publishers can make smarter choices about which strategies to adopt as they navigate mobile privacy.

The Publisher’s Playbook: Opportunities and Potential Pitfalls

1. Cross-App Tracking: The End of an Era?

The decline of cross-app tracking is more than a simple shift. It forces data collection strategies that could either unlock new opportunities or leave gaps in your data.

2. Ad Targeting and Measurement: New Tools, New Complexities

The new Sandbox APIs promise a lot but also require a leap of faith. Will these tools deliver the precision they claim, or will they leave publishers with a diluted version of what was once possible?

3. Revenue Implications: Walking a Tightrope

The impact on revenue streams is real. While contextual ads and first-party data are touted as solutions, the practical implications could be more nuanced.

Real-World Experiences: Insights from Early Adopters

1. Gameloft’s Strategic Leap: Testing the Limits of Privacy-First Ad Measurement

Gameloft, a mobile gaming titan, has been at the forefront of adopting the Android Privacy Sandbox. Partnering with Singular, they tested the Attribution Reporting API, balancing effective ad measurement with the demands of user privacy. Their journey highlights both the promise and the challenges of adapting to these evolving standards, particularly in maintaining data accuracy and targeting precision.

2. Verve Group’s Bold Move: Redefining On-Device Bidding with Privacy Sandbox

Ad tech innovator, Verve Group, is pioneering on-device bidding through the Android Privacy Sandbox, focusing on the Protected Audiences API. By moving auctions to the user’s device, Verve reduced data transfers, aligning with privacy goals. But not without running into significant hurdles. Their collaborative work with partners like Remerge has been essential in overcoming these technical challenges, from latency issues to complex implementation requirements.

The Realities of Implementation: What Publishers Need to Know

1. Implementation Complexities: The Devil’s in the Details

Implementing these new APIs requires more than a simple update — it’s an extensive reworking of infrastructure. Publishers should invest significant resources into testing and development to ensure these systems work effectively. Expect compatibility issues.

2. Latency: The Hidden Cost of Privacy

On-device processing is a cornerstone of the Android Privacy Sandbox, but latency can become a significant issue, impacting ad delivery, viewability, speed, and efficiency.

3. Data Accuracy: A Double-Edged Sword

Privacy-preserving methods often result in less data granularity. While this protects users, it can also undermine ad targeting precision and measurement, leaving publishers questioning whether the benefits outweigh the drawbacks. Will we still be able to hit KPIs?

Game Plan For Sailing Mobile’s Privacy-Preserving Seas

1. Hoist Your Sails, But Chart Your Course Wisely

Early adoption is key to catching wind and gaining momentum but plot your journey carefully. Don’t drink the Kool-Aid just yet. Thorough testing and validation are necessary before full-scale implementation, ensuring you’re prepared for the uncharted waters.

2. Steer Your Ship with Trusted Crew

Partnering with reliable DSPs, SSPs, and MMPs is crucial for steering the complex waters. Ensure these alliances are aligned, guiding you towards your specific goals — not just drifting the tide of broad industry trends.

3. Keep a Steady Hand on the Helm: Embrace New Standards, But Stay Informed

As you sail through the shifting currents of the Android Privacy Sandbox, keep a watchful eye on the horizon. While the new Attribution Reporting API offers potential, it’s vital to understand what’s being gained — and what might be lost. Stay informed and ready to adjust strategies as the seascape evolves.

Looking Forward: A Cautious Path to the Future

1. Stay Critical, Stay Agile

As the Android Privacy Sandbox develops, keep a close eye on updates. While it promises much, the reality may require agile adjustments to strategies and expectations.

2. Evolve with the Technology, But Manage Expectations

This shift isn’t a survival strategy — it’s about evolving. But evolution is complex and often slower than anticipated. Prepare for a marathon rather than a sprint.

The Android Privacy Sandbox is not a cure-all, publishers need to navigate these changes carefully, balancing new opportunities with potential pitfalls. By staying informed, skeptical, and proactive, you can make the most of this transition — without falling victim to the hype.

Additional Resources:

– Google Privacy Sandbox Documentation

– AppsFlyer’s Guide to Privacy Sandbox 

The post Dissecting the Android Privacy Sandbox: A Critical Guide for Publishers appeared first on AdMonsters.

As Google’s Android Privacy Sandbox gears up for its anticipated 2025 launch, mobile marketers need to stay ahead of the curve. Remerge, a leading Demand Side Platform (DSP), is at the forefront of this transition, collaborating  with Google and other ad tech partners, such as Verve, AppsFlyer, Adjust, and Singular, to ensure a seamless shift. Luckey Harpley, Staff Product Manager at Remerge, sheds light on what this means for the future of mobile marketing and how to navigate this new landscape.

Why Is Mobile Marketing Shifting to Privacy-First Advertising?

The rise of AI and sophisticated machine learning algorithms showcases the benefits of new technologies, but it also highlights the dangers of these advancements. People want more control over how big tech businesses manage their data. The advertising world is moving towards a privacy-centric future and marketers must adapt.

Apple made the first privacy move on mobile with the launch of its App Tracking Transparency (ATT) framework in 2021. Google’s answer is the Privacy Sandbox, a set of APIs to facilitate the selling, buying, and targeting of in-app ad placements, without requiring third-party cookies in Chrome or cross-app identifiers on Android. For Android, this will provide tracking and reporting via its Attribution API, targeting through Topics and Protected Audiences APIs, and data collection and handling via the SDK Run Time.

Why are DSPs Like Remerge Already Working on Solutions for the Android Privacy Sandbox?

It’s important to avoid a situation like the ATT rollout, where advertisers and publishers were left in the dark before its launch and struggled to understand how to run campaigns after it came into effect.

We want to ensure everything is ready for mobile marketers to run privacy-compliant advertising campaigns on Android without experiencing a drastic decline in performance. Android maintained its position as the leading mobile operating system worldwide in the first quarter of 2024, with a market share of 70.7% so this transitional period is crucial for the well-being of the mobile marketing ecosystem.

Does Google’s Decision to Keep Third-Party Cookies on Chrome Change Anything?

Google recently announced that they no longer plan to deprecate third-party cookies on Chrome and emphasized giving users the choice to opt-in to tracking. This update is unrelated to mobile. A similar approach is likely to happen on Android, where the GAID remains intact, and users can choose whether to share this with advertisers. In this scenario, nothing would change for mobile DSPs and their investment into Google’s APIs – the Android Privacy Sandbox would remain an essential framework for privacy-preserving advertising campaigns.

What Has Remerge Tested and Why Should Mobile Marketers Take Notice?

Remerge’s Research and Development team has been working on the Sandbox for over 1.5 years. They’ve focused on testing the Protected Audience API, which will allow advertisers to run retargeting campaigns on Android.

Tests have been completed with Mobile Measurement Partners (MMPs) like Adjust, AppsFlyer, and Singular. This includes developing a proof-of-concept for Custom Audience Delegation, a mechanism required for remarketing in Sandbox. This allows an MMP SDK to add users to custom audiences on behalf of advertisers based on their in-app behavior. Additionally, the first DSP/SSP on-device bidding test was conducted with Verve. These are small steps but important milestones for Sandbox testing, demonstrating that the Protected Audience API and custom audiences mechanisms are working as planned and validating product capabilities.

How Will a Mobile Marketing Manager’s Life Change When the Sandbox Rolls Out?

Advertisers won’t experience a considerable change in the buying process. At Remerge, marketers will continue to share their user data, desired campaign segmentation, and budget with the Account Management team as usual. Remerge will still be able to target users according to activity within an advertiser’s app and run creatives such as static and video. There’ll be no changes to CTR and CPX reporting, and for ROAS reporting, the data will likely have limited dimensionality, focusing on campaign and country-level reporting.

Google and its partners are doing the heavy lifting on the technical setup. Compared to ATT, the Android Privacy Sandbox is not only far more powerful with its targeting capabilities but also much more complex. This is a completely new tech stack with privacy-preserving mechanisms, and while we might see some performance dips initially, the long-term benefits are expected to be significant.

What About User Acquisition (UA) Campaigns?

While the focus has been on retargeting and the Protected Audience API, the Protected App Signals is supporting UA on Android. Although no industry players have made proposals on the Protected App Signals API yet, advertisers should reach out to their UA partners to discuss their plans.

What Can Mobile Marketers Do Right Now?

Advertisers should start finding a partner equipped to run mobile marketing campaigns on Android. Early adopters like Remerge, who have helped shape components of the Privacy Sandbox framework, will be well-positioned to hit the ground running when it launches.

The post What Should Mobile Marketers Know About the Android Privacy Sandbox Launch? appeared first on AdMonsters.

All mobile users are not treated equally, especially those with Android versus those with iOS. After all, they are two completely different operating systems, so it’s best to know the key differences to attain the success you want as a publisher. Both giants in the mobile ecosystem contain specific characteristics that demand careful consideration from publishers.

During a breakout session at AdMonsters Pub Forum Coronado Island, Joey Stern, Ad Systems Manager at TuneIn, led an exciting discussion during his session titled “Navigating Multi-Platform Madness: Unleashing Revenue Opportunities Within Complex Mobile Strategies.” The session is one to highlight as it delved into the critical differences between Android and iOS, emphasizing the role of privacy, app longevity, and user habits.

In the extension of the session below, Stern left further insight regarding strategies to combat the privacy constraints that come with both platforms, ways to unlock opportunities for audio monetization, optimizing ad revenue on Android’s extended lifespan, understanding diverse audiences, and leveraging app release info to quickly resolve any issues that arise. Learn more about the world of mobile according to Stern below.

Yakira Young: Can you explain some of the differences between Android and iOS platforms that app publishers should be thinking about?

Joey Stern: The biggest difference is how they handle privacy. iOS is much more locked up than Android. Android allows for a much more extended period of app updates, while iOS has a longer period of system updates, meaning Android users will be on newer app versions, while iOS users will get held back at some point, and those users may still offer valid revenue. Don’t just assume all mobile users have the same habits; test to see what divergences exist.

YY:  How can publishers navigate the very different approaches of iOS and Android as it pertains to privacy?

JS: Staying up to date is key here. This is a constantly moving goalpost and legally fraught.

• Pay attention to both the political decisions and the financial ones.
• Make sure you have a trusted privacy partner and meet with them regularly, not just when a big change is coming up.
• Understand that location can be a big factor in what platform/client your users are on, so privacy strategies should be location and device-specific where needed.

YY: What advice do you have for businesses looking to monetize audio? 

JS: Start understanding your demand options now, and figure out where to layer that in with existing audio. Companion Banners for audio ads are key drivers. Understanding the long tail of your users can help drive campaign revenue more than in-video ads. Also, server-side delivery (especially with Smart Speakers) is a huge opportunity, and having a DAI you trust and understand is key. This is new territory, and being nimble will be necessary for success.

YY: With apps on Android having a longer lifespan, how do you optimize ad revenue from these apps over an extended period? Do you utilize any particular tactics or approaches to maximize ad performance in such cases?

JS: With Android, the goal should be stability because there are various devices. Clear and actionable metrics are necessary to ensure a good user experience across a much bigger variety of possible screens. It also helps to build out ad requests with some flexibility or external configuration ability that isn’t app release-centric (request timers, ad units, etc).

YY: How should publishers go about understanding their audiences on both Android and iOS platforms? 

JS: TEST TEST TEST TEST. Look at different devices and check the basics:

• Clicks
• View Thru Rate
• Render rate
• Viewability

Your biggest asset is understanding your audiences by device and geography. Combine those data points to know where to offer higher-value users and when.

YY: How can getting app release information into your reporting help find issues as they are happening?

JS: Errors are so much easier to track when you understand what version of the app users are on. So it’s important to make the app version part of your key value reporting for tracking an issue quickly. Also, sometimes bulk user settings (logged in vs. new users vs. registered, for example) can help determine *who* and which issue is affecting vs. version which tells you *when*.

The post Diverse Approaches to App Inventory for Enhanced User Insights appeared first on AdMonsters.