Your App, Everywhere.
Maximize re-engagement with Engage SDK. It's a powerful way to bring your personalized content to where your users are —and seamlessly guiding them into the relevant in-app experiences.
Re-engage users across surfaces & devices
Surfaces the best & most relevant content from user’s favorite apps
Top 3 user journeys to engage your users on Collections
Frequently asked questions
Getting started & integration
How do I express interest in joining the Engage SDK developer preview?
If your app offers content in one of the content categories supported by Engage SDK, we invite you to express interest here.
Are there eligibility requirements for enrolling in the developer preview?
Yes. You can learn more about the eligibility requirements and ongoing requirements by visiting our developer pages.
What are the technical requirements to integrate the Engage SDK?
You’ll need to integrate Engage SDK into your app and implement the necessary APIs to publish your content clusters. You can learn more about the technical details, step-by-step guidance, and best practices here.
Will integrating my app with Engage SDK impact the size of my APK?
Integrating your app with Engage SDK adds approximately less than 50KB to the average compressed APK size.
Does my app need to be installed on the device for my content to be delivered to users?
Yes, our primary goal is to help developers re-engage with their existing users. A user must have the app installed on the device to receive your content. If your app is integrated with Engage SDK but not yet installed by the user, select surfaces, like Collections, will recommend the user install it. If the user installs your app, Collections will update immediately to incorporate your content.
Supported surfaces & markets
Which surfaces & markets are supported by Engage SDK?
Our goal is to continue to expand your reach with Engage SDK by bringing your content to more surfaces across markets. Today, Engage SDK delivers content to the following surfaces, which vary by supported content categories and market availability.
Active surface |
Supported content category |
Market availability |
|---|---|---|
| Collections | Watch, Listen, Social, Read, Food, Shop, Travel |
|
| Apps Home on Play Store | Watch, Listen, Social, Read, Food, Shop |
|
| You tab on Play Store | Watch, Listen, Social, Read, Food, Shop |
|
| Entertainment Space on select Android tablets | Watch, Listen, Read |
|
| Google TV | Watch |
|
Best practices for content publishing
What types of content clusters can be published
Several types of content clusters can be published:
Recommendations: Allows you to provide personalized and timely suggestions for users (e.g., "Top 10 for you").
Continuation journeys: Enables users to pick up where they left off in your app (e.g., "Continue watching," "Continue listening").
Featured: Spotlights your hero content in a larger, more premium UI placement (Collections only).
How often should content be published? Is it when the user opens the app?
Publishing fresh, timely, and personalized recommendations can help improve discovery. Based on early learnings, we recommend thinking about publishing content in two key ways:
Push content on a regular cadence—like refreshing it daily—so it always stays fresh for your users. You can also publish more or less frequently depending on your users' usage patterns.
Publish immediately after a user finishes a session in your app. This ensures the content displayed is the most up-to-date and reflects their latest activity. This also powers continuation journeys, enabling a user to easily pick up right where they left off and seamlessly guide them into the relevant in-app experiences.
Will Engage SDK support additional content categories in the future?
Engage SDK already supports Watch, Listen, Social, Read, Food, Shop, and Travel. We expect to expand support for additional content categories - like Health & Fitness - in the coming year.