Google is building an on-device surface that organizes users' apps by verticals and enables a new immersive experience for personalized app content consumption and discovery. This fullscreen experience provides developer partners with an opportunity to showcase their best rich content in a dedicated channel outside of their app.
This guide contains instructions for developer partners to integrate their video content, using the Engage SDK to populate both this new surface area and existing Google surfaces.
Integration detail
Terminology
This integration includes the following three cluster types: Recommendation, Continuation, and Featured.
Recommendation clusters show personalized suggestions for content to watch from an individual developer partner.
Your recommendations take the following structure:
Recommendation Cluster: A UI view that contains a group of recommendations from the same developer partner.
Figure 1. Entertainment Space UI showing a Recommendation Cluster from a single partner. Entity: An object representing a single item in a cluster. An entity can be a movie, a TV show, a TV series, live video, and more. See the Provide entity data section for a list of supported entity types.
Figure 2. Entertainment Space UI showing a single Entity within a single partner's Recommendation Cluster.
The Continuation cluster shows unfinished videos and relevant newly released episodes from multiple developer partners in one UI grouping. Each developer partner will be allowed to broadcast a maximum of 10 entities in the Continuation cluster. Research has shown that personalized recommendations along with personalized Continuation content creates the best user engagement.
Figure 3. Entertainment Space UI showing a Continuation cluster with unfinished recommendations from multiple partners (only one recommendation is currently visible). The Featured cluster showcases a selection of entities from multiple developer partners in one UI grouping. There will be a single Featured cluster, which is surfaced near the top of the UI with a priority placement above all Recommendation clusters. Each developer partner will be allowed to broadcast up to 10 entities in the Featured cluster.
Figure 4. Entertainment Space UI showing a Featured cluster with recommendations from multiple partners (only one recommendation is currently visible).
Pre-work
Minimum API level: 19
Add the com.google.android.play:engage library to your app:
dependencies {
// Make sure you also include that repository in your project's build.gradle file.
implementation 'com.google.android.play:engage:1.5.0-alpha'
}
To make the Engage SDK function for devices with Android 11 and above, declare the following in the manifest file:
<queries>
<package android:name="com.android.vending" />
</queries>
For more information, see Package visibility in Android 11.
Summary
The design is based on an implementation of a bound service.
The data a client can publish is subject to the following limits for different cluster types:
| Cluster type | Cluster limits | Maximum entity limits in a cluster |
|---|---|---|
| Recommendation Cluster(s) | At most 5 | At most 50 |
| Continuation Cluster | At most 1 | At most 10 |
| Featured Cluster | At most 1 | At most 10 |
Step 0: Migration from existing Media Home SDK integration
Map data models from existing integration
If you are migrating from an existing Media Home integration, the following table outlines how to map data models in existing SDKs to the new Engage SDK:
| MediaHomeVideoContract integration equivalent | Engage SDK integration equivalent |
|---|---|
com.google.android.mediahome.video.PreviewChannel |
com.google.android.play.engage.common.datamodel.RecommendationCluster |
com.google.android.mediahome.video.PreviewChannel.Builder |
com.google.android.play.engage.common.datamodel.RecommendationCluster.Builder |
com.google.android.mediahome.video.PreviewChannelHelper |
com.google.android.play.engage.video.service.AppEngageVideoClient |
com.google.android.mediahome.video.PreviewProgram |
Divided into separate classes: EventVideo,
LiveStreamingVideo, Movie, TvEpisode,
TvSeason, TvShow, VideoClipEntity |
com.google.android.mediahome.video.PreviewProgram.Builder |
Divided into builders in separate classes: EventVideo,
LiveStreamingVideo, Movie, TvEpisode,
TvSeason, TvShow, VideoClipEntity |
com.google.android.mediahome.video.VideoContract |
No longer needed. |
com.google.android.mediahome.video.WatchNextProgram |
Divided into attributes in separate classes:
EventVideoEntity, LiveStreamingVideoEntity,
MovieEntity, TvEpisodeEntity,
TvSeasonEntity, TvShowEntity,
VideoClipEntity |
com.google.android.mediahome.video.WatchNextProgram.Builder |
Divided into attributes in separate classes:
EventVideoEntity, LiveStreamingVideoEntity,
MovieEntity, TvEpisodeEntity,
TvSeasonEntity, TvShowEntity,
VideoClipEntity |
Publishing clusters in Media Home SDK vs Engage SDK
With Media Home SDK, clusters and entities were published through separate APIs:
// 1. Fetch existing channels
List<PreviewChannel> channels = PreviewChannelHelper.getAllChannels();
// 2. If there are no channels, publish new channels
long channelId = PreviewChannelHelper.publishChannel(builder.build());
// 3. If there are existing channels, decide whether to update channel contents
PreviewChannelHelper.updatePreviewChannel(channelId, builder.build());
// 4. Delete all programs in the channel
PreviewChannelHelper.deleteAllPreviewProgramsByChannelId(channelId);
// 5. publish new programs in the channel
PreviewChannelHelper.publishPreviewProgram(builder.build());
With Engage SDK, cluster and entity publishing are combined into a single API call. All entities that belong to a cluster are published together with that cluster:
new RecommendationCluster.Builder<VideoEntity>()
.addEntity(MOVIE_ENTITY)
.addEntity(MOVIE_ENTITY)
.addEntity(MOVIE_ENTITY)
.setTitle("Recommendation")
.build();
Step 1: Provide entity data
The SDK has defined different entities to represent each item type. We support the following entities for the Watch category:
MovieEntityTvShowEntityTvSeasonEntityTvEpisodeEntityEventVideoEntityLiveStreamingVideoEntityVideoClipEntity
The charts below outline available attributes and requirements for each type.
MovieEntity
| Attribute | Requirement | Notes |
|---|---|---|
| Name | Required | |
| Poster images | Required | At least one image is required, and must be provided with an aspect ratio. (Landscape is preferred but passing both portrait and landscape images for different scenarios is recommended.) |
| Playback uri | Required | The deep link to the provider app to start playing the movie. |
| Info page uri | Optional | The deep link to the provider app to show details about the movie. |
| Release date | Required | In epoch milliseconds. |
| Availability | Required | AVAILABLE: The content is available to the user without any further action. FREE_WITH_SUBSCRIPTION: The content is available after the user purchases a subscription. PAID_CONTENT: The content requires user purchase or rental. PURCHASED: The content has been purchased or rented by the user. |
| Offer price | Optional | Free text |
| Duration | Required | In milliseconds. |
| Genre | Required | Free text |
| Content ratings | Required | Free text, please follow the industry standard. (Example) |
| Watch next type | Conditionally required | Must be provided when the item is in the Continuation cluster and must be one of the following four types: CONTINUE: The user has already watched more than 1 minute of this content. NEW: The user has watched all available episodes from some episodic content, but a new episode has become available and there is exactly one unwatched episode. This works for TV shows, recorded soccer matches in a series, and so on. NEXT: The user has watched one or more complete episodes from some episodic content, but there remains either more than one episode remaining or exactly one episode remaining where the last episode is not "NEW" and was released before the user started watching the episodic content. WATCHLIST: The user has explicitly elected to add a movie, event, or series to a watchlist to manually curate what they want to watch next. |
| Last engagement time | Conditionally required | Must be provided when the item is in the Continuation cluster. In epoch milliseconds. |
| Last playback position time | Conditionally required | Must be provided when the item is in the Continuation cluster and WatchNextType is CONTINUE. In epoch milliseconds. |
TvShowEntity
| Attribute | Requirement | Notes |
|---|---|---|
| Name | Required | |
| Poster images | Required | At least one image is required, and must be provided with an aspect ratio. (Landscape is preferred but passing both portrait and landscape images for different scenarios is recommended.) |
| Info page uri | Required | The deep link to the provider app to show the details of the TV show. |
| Playback uri | Optional | The deep link to the provider app to start playing the TV show. |
| First episode air date | Required | In epoch milliseconds. |
| Latest episode air date | Optional | In epoch milliseconds. |
| Availability | Required | AVAILABLE: The content is available to the user without any further action. FREE_WITH_SUBSCRIPTION: The content is available after the user purchases a subscription. PAID_CONTENT: The content requires user purchase or rental. PURCHASED: The content has been purchased or rented by the user. |
| Offer price | Optional | Free text |
| Season count | Required | Positive integer |
| Genre | Required | Free text |
| Content ratings | Required | Free text, please follow the industry standard. (Example) |
| Watch next type | Conditionally required | Must be provided when the item is in the Continuation cluster and must be one of the following four types: CONTINUE: The user has already watched more than 1 minute of this content. NEW: The user has watched all available episodes from some episodic content, but a new episode has become available and there is exactly one unwatched episode. This works for TV shows, recorded soccer matches in a series, and so on. NEXT: The user has watched one or more complete episodes from some episodic content, but there remains either more than one episode remaining or exactly one episode remaining where the last episode is not "NEW" and was released before the user started watching the episodic content. WATCHLIST: The user has explicitly elected to add a movie, event, or series to a watchlist to manually curate what they want to watch next. |
| Last engagement time | Conditionally required | Must be provided when the item is in the Continuation cluster. In epoch milliseconds. |
| Last playback position time | Conditionally required | Must be provided when the item is in the Continuation cluster and WatchNextType is CONTINUE. In epoch milliseconds. |
TvSeasonEntity
| Attribute | Requirement | Notes |
|---|---|---|
| Name | Required | |
| Poster images | Required | At least one image is required, and must be provided with an aspect ratio. (Landscape is preferred but passing both portrait and landscape images for different scenarios is recommended.) |
| Info page uri | Required | The deep link to the provider app to show the details of the TV show season. |
| Playback uri | Optional | The deep link to the provider app to start playing the TV show season. |
| Season number | Required | Positive integer |
| First episode air date | Required | In epoch milliseconds. |
| Latest episode air date | Optional | In epoch milliseconds. |
| Availability | Required | AVAILABLE: The content is available to the user without any further action. FREE_WITH_SUBSCRIPTION: The content is available after the user purchases a subscription. PAID_CONTENT: The content requires user purchase or rental. PURCHASED: The content has been purchased or rented by the user. |
| Offer price | Optional | Free text |
| Episode count | Required | Positive integer |
| Genre | Required | Free text |
| Content ratings | Required | Free text, please follow the industry standard. (Example) |
| Watch next type | Conditionally required | Must be provided when the item is in the Continuation cluster and must be one of the following four types: CONTINUE: The user has already watched more than 1 minute of this content. NEW: The user has watched all available episodes from some episodic content, but a new episode has become available and there is exactly one unwatched episode. This works for TV shows, recorded soccer matches in a series, and so on. NEXT: The user has watched one or more complete episodes from some episodic content, but there remains either more than one episode remaining or exactly one episode remaining where the last episode is not "NEW" and was released before the user started watching the episodic content. WATCHLIST: The user has explicitly elected to add a movie, event, or series to a watchlist to manually curate what they want to watch next. |
| Last engagement time | Conditionally required | Must be provided when the item is in the Continuation cluster. In epoch milliseconds. |
| Last playback position time | Conditionally required | Must be provided when the item is in the Continuation cluster and WatchNextType is CONTINUE. In epoch milliseconds. |
TvEpisodeEntity
| Attribute | Requirement | Notes |
|---|---|---|
| Name | Required | |
| Poster images | Required | At least one image is required, and must be provided with an aspect ratio. (Landscape is preferred but passing both portrait and landscape images for different scenarios is recommended.) |
| Playback uri | Required | The deep link to the provider app to start playing the episode. |
| Info page uri | Optional | The deep link to the provider app to show details about the TV show episode. |
| Episode number | Required | Positive integer |
| Air date | Required | In epoch milliseconds. |
| Availability | Required | AVAILABLE: The content is available to the user without any further action. FREE_WITH_SUBSCRIPTION: The content is available after the user purchases a subscription. PAID_CONTENT: The content requires user purchase or rental. PURCHASED: The content has been purchased or rented by the user. |
| Offer price | Optional | Free text |
| Duration | Required | Must be a positive value in milliseconds. |
| Genre | Required | Free text |
| Content ratings | Required | Free text, please follow the industry standard. (Example) |
| Watch next type | Conditionally required | Must be provided when the item is in the Continuation cluster and must be one of the following four types: CONTINUE: The user has already watched more than 1 minute of this content. NEW: The user has watched all available episodes from some episodic content, but a new episode has become available and there is exactly one unwatched episode. This works for TV shows, recorded soccer matches in a series, and so on. NEXT: The user has watched one or more complete episodes from some episodic content, but there remains either more than one episode remaining or exactly one episode remaining where the last episode is not "NEW" and was released before the user started watching the episodic content. WATCHLIST: The user has explicitly elected to add a movie, event, or series to a watchlist to manually curate what they want to watch next. |
| Last engagement time | Conditionally required | Must be provided when the item is in the Continuation cluster. In epoch milliseconds. |
| Last playback position time | Conditionally required | Must be provided when the item is in the Continuation cluster and WatchNextType is CONTINUE. In epoch milliseconds. |
EventVideoEntity
The EventVideoEntity object represents an event, such as the Olympic Games.
| Attribute | Requirement | Notes |
|---|---|---|
| Name | Required | |
| Poster images | Required | At least one image is required, and must be provided with an aspect ratio. (Landscape is preferred but passing both portrait and landscape images for different scenarios is recommended.) |
| Playback uri | Required | The deep link to the provider app to start playing the video. |
| Event location | Optional | Free text |
| Event broadcaster | Required | Free text |
| Duration | Required | Must be a positive value in milliseconds. |
| Watch next type | Conditionally required | Must be provided when the item is in the Continuation cluster and must be one of the following four types: CONTINUE: The user has already watched more than 1 minute of this content. NEW: The user has watched all available episodes from some episodic content, but a new episode has become available and there is exactly one unwatched episode. This works for TV shows, recorded soccer matches in a series, and so on. NEXT: The user has watched one or more complete episodes from some episodic content, but there remains either more than one episode remaining or exactly one episode remaining where the last episode is not "NEW" and was released before the user started watching the episodic content. WATCHLIST: The user has explicitly elected to add a movie, event, or series to a watchlist to manually curate what they want to watch next. |
| Last engagement time | Conditionally required | Must be provided when the item is in the Continuation cluster. In epoch milliseconds. |
| Last playback position time | Conditionally required | Must be provided when the item is in the Continuation cluster and WatchNextType is CONTINUE. In epoch milliseconds. |
LiveStreamingVideoEntity
| Attribute | Requirement | Notes |
|---|---|---|
| Name | Required | |
| Poster images | Required | At least one image is required, and must be provided with an aspect ratio. (Landscape is preferred but passing both portrait and landscape images for different scenarios is recommended.) |
| Playback uri | Required | The deep link to the provider app to start playing the video. |
| Start time | Optional | In epoch milliseconds. |
| Broadcaster | Required | Free text |
| View count | Optional | Free text, must be localized. |
| Watch next type | Conditionally required | Must be provided when the item is in the Continuation cluster and must be one of the following four types: CONTINUE: The user has already watched more than 1 minute of this content. NEW: The user has watched all available episodes from some episodic content, but a new episode has become available and there is exactly one unwatched episode. This works for TV shows, recorded soccer matches in a series, and so on. NEXT: The user has watched one or more complete episodes from some episodic content, but there remains either more than one episode remaining or exactly one episode remaining where the last episode is not "NEW" and was released before the user started watching the episodic content. WATCHLIST: The user has explicitly elected to add a movie, event, or series to a watchlist to manually curate what they want to watch next. |
| Last engagement time | Conditionally required | Must be provided when the item is in the Continuation cluster. In epoch milliseconds. |
| Last playback position time | Conditionally required | Must be provided when the item is in the Continuation cluster and WatchNextType is CONTINUE. In epoch milliseconds. |
VideoClipEntity
The VideoClipEntity object represents a video entity coming from social media,
such as TikTok or YouTube.
| Attribute | Requirement | Notes |
|---|---|---|
| Name | Required | |
| Poster images | Required | At least one image is required, and must be provided with an aspect ratio. (Landscape is preferred but passing both portrait and landscape images for different scenarios is recommended.) |
| Playback uri | Required | The deep link to the provider app to start playing the video. |
| Created time | Required | In epoch milliseconds. |
| Duration | Required | Must be a positive value in milliseconds. |
| Creator | Required | Free text |
| View count | Optional | Free text, must be localized. |
| Watch next type | Conditionally required | Must be provided when the item is in the Continuation cluster and must be one of the following four types: CONTINUE: The user has already watched more than 1 minute of this content. NEW: The user has watched all available episodes from some episodic content, but a new episode has become available and there is exactly one unwatched episode. This works for TV shows, recorded soccer matches in a series, and so on. NEXT: The user has watched one or more complete episodes from some episodic content, but there remains either more than one episode remaining or exactly one episode remaining where the last episode is not "NEW" and was released before the user started watching the episodic content. WATCHLIST: The user has explicitly elected to add a movie, event, or series to a watchlist to manually curate what they want to watch next. |
| Last engagement time | Conditionally required | Must be provided when the item is in the Continuation cluster. In epoch milliseconds. |
| Last playback position time | Conditionally required | Must be provided when the item is in the Continuation cluster and WatchNextType is CONTINUE. In epoch milliseconds. |
Example
MovieEntity movie = new MovieEntity.Builder()
.setName("Avengers")
.addPosterImage(
new Image.Builder()
.setImageUri(Uri.parse("http://www.x.com/image.png"))
.setImageHeightInPixel(960)
.setImageWidthInPixel(408)
.build())
.setPlayBackUri(Uri.parse("http://tv.com/playback/1"))
.setReleaseDateEpochMillis(1633032895L)
.setAvailability(ContentAvailability.AVAILABILITY_AVAILABLE)
.setDurationMillis(12345678L)
.addGenre("action")
.addContentRating("R")
.setWatchNextType(WatchNextType.TYPE_NEW)
.setLastEngagementTimeMillis(1664568895L)
.build()
Step 2: Provide Cluster data
It’s recommended to have the content publish job executed in the background (for example, using WorkManager) and scheduled on a regular basis or on an event basis (for example, every time the user opens the app or when the user just added something to their cart).
AppEngagePublishClient is responsible for publishing clients. There are five
APIs to publish clusters in the client:
isServiceAvailablepublishRecommendationClusterspublishFeaturedClusterpublishContinuationClusterdeleteClusters
API #1: isServiceAvailable
This API is used to check if the service is available for integration and whether the content can be presented on the device.
Task<Boolean> isAvailableTask = client.isServiceAvailable();
isAvailableTask.addOnCompleteListener(task - > {
if (resultTask.isSuccessful()) {
// Handle success
}
});
API #2: publishRecommendationClusters
This API is used to publish a list of RecommendationCluster objects.
Task<Void> task =
client.publishRecommendationClusters(
new PublishRecommendationClustersRequest.Builder()
.addRecommendationCluster(
new RecommendationCluster.Builder()
.addEntity(entity1)
.addEntity(entity2)
.setTitle("Recommendation")
.build())
.build());
When the service receives the request, the following actions take place within one transaction:
- Existing
RecommendationClusterdata from the developer partner is removed. - Data from the request is parsed and stored in the updated Recommendation Cluster.
In case of an error, the entire request is rejected and the existing state is maintained.
API #3: publishFeaturedCluster
This API is used to publish a list of FeaturedCluster objects.
Task<Void> task =
client.publishFeaturedCluster(
new PublishFeaturedClustersRequest.Builder()
.addFeaturedCluster(
new FeaturedCluster.Builder()
.addEntity(entity1)
.addEntity(entity2)
.build())
.build());
When the service receives the request, the following actions take place within one transaction:
- Existing
FeaturedClusterdata from the developer partner is removed. - Data from the request is parsed and stored in the updated Featured Cluster.
In case of an error, the entire request is rejected and the existing state is maintained.
API #4: publishContinuationCluster
This API is used to publish a ContinuationCluster object.
Task<Void> task =
client.publishContinuationCluster(
new PublishContinuationClusterRequest.Builder()
.setContinuationCluster(
new ContinuationCluster.Builder()
.addEntity(entity1)
.addEntity(entity2)
.build())
.build());
When the service receives the request, the following actions take place within one transaction:
- Existing
ContinuationClusterdata from the developer partner is removed. - Data from the request is parsed and stored in the updated Continuation Cluster.
In case of an error, the entire request is rejected and the existing state is maintained.
API #5: deleteClusters
This API is used to delete the content of a given cluster type.
Task<Void> task =
client.deleteClusters(
new DeleteClustersRequest.Builder()
.addClusterType(ClusterType.TYPE_CONTINUATION)
.addClusterType(ClusterType.TYPE_FEATURED)
.addClusterType(ClusterType.TYPE_RECOMMENDATION)
.build());
When the service receives the request, it removes the existing data from all clusters matching the specified cluster types. Clients can choose to pass one or many cluster types. In case of an error, the entire request is rejected and the existing state is maintained.
Error handling
It is highly recommended to listen to the task result from the publish APIs such that a follow-up action can be taken to recover and resubmit an successful task.
client.publishRecommendationClusters(
new PublishRecommendationClustersRequest.Builder()
.addRecommendationCluster(...)
.build())
.addOnCompleteListener(
task -> {
if (task.isSuccessful()) {
// do something
} else {
Exception exception = task.getException();
if (exception instanceof AppEngageException) {
@AppEngageErrorCode
int errorCode = ((AppEngageException) exception).getErrorCode();
if (errorCode == AppEngageErrorCode.SERVICE_NOT_FOUND) {
// do something
}
}
}
});
The error is returned as an AppEngageException with the cause included as an
error code.
| Error code | Note |
|---|---|
SERVICE_NOT_FOUND |
The service is not available on the given device. |
SERVICE_NOT_AVAILABLE |
The service is available on the given device, but it is not available at the time of the call (for example, it is explicitly disabled). |
SERVICE_CALL_EXECUTION_FAILURE |
The task execution failed due to threading issues. In this case, it can be retried. |
SERVICE_CALL_PERMISSION_DENIED |
The caller is not allowed to make the service call. |
SERVICE_CALL_INVALID_ARGUMENT |
The request contains invalid data (for example, more than the allowed number of clusters). |
SERVICE_CALL_INTERNAL |
There is an error on the service side. |
SERVICE_CALL_RESOURCE_EXHAUSTED |
The service call is made too frequently. |
Step 3: Handle broadcast intents
In addition to making publish content API calls through a job, it is also
required to set up a
BroadcastReceiver to receive
the request for a content publish.
The goal of broadcast intents is mainly for app reactivation and forcing data sync. Broadcast intents are not designed to be sent very frequently. It is only triggered when the Engage Service determines the content might be stale (for example, a week old). That way, there is more confidence that the user can have a fresh content experience, even if the application has not been executed for a long period of time.
The BroadcastReceiver must be set up in the following two ways:
- Dynamically register an instance of the
BroadcastReceiverclass usingContext.registerReceiver(). This enables communication from applications that are still live in memory.
class AppEngageBroadcastReceiver extends BroadcastReceiver {
// Trigger recommendation cluster publish when PUBLISH_RECOMMENDATION broadcast
// is received
// Trigger featured cluster publish when PUBLISH_FEATURED broadcast is received
// Trigger continuation cluster publish when PUBLISH_CONTINUATION broadcast is
// received
}
public static void registerBroadcastReceivers(Context context) {
context = context.getApplicationContext();
// Register Recommendation Cluster Publish Intent
context.registerReceiver(new AppEngageBroadcastReceiver(),
new IntentFilter(com.google.android.play.engage.service.Intents.ACTION_PUBLISH_RECOMMENDATION));
// Register Featured Cluster Publish Intent
context.registerReceiver(new AppEngageBroadcastReceiver(),
new IntentFilter(com.google.android.play.engage.service.Intents.ACTION_PUBLISH_FEATURED));
// Register Continuation Cluster Publish Intent
context.registerReceiver(new AppEngageBroadcastReceiver(),
new IntentFilter(com.google.android.play.engage.service.Intents.ACTION_PUBLISH_CONTINUATION));
}
- Statically declare an implementation with the
<receiver>tag in yourAndroidManifest.xmlfile. This allows the application to receive broadcast intents when it is not running, and also allows the application to publish the content.
<application>
<receiver
android:name=".AppEngageBroadcastReceiver"
android:exported="true"
android:enabled="true">
<intent-filter>
<action android:name="com.google.android.play.engage.action.PUBLISH_RECOMMENDATION" />
</intent-filter>
<intent-filter>
<action android:name="com.google.android.play.engage.action.PUBLISH_FEATURED" />
</intent-filter>
<intent-filter>
<action android:name="com.google.android.play.engage.action.PUBLISH_CONTINUATION" />
</intent-filter>
</receiver>
</application>
The following intents will be sent by the service:
com.google.android.play.engage.action.PUBLISH_RECOMMENDATIONIt is recommended to start apublishRecommendationClusterscall when receiving this intent.com.google.android.play.engage.action.PUBLISH_FEATUREDIt is recommended to start apublishFeaturedClustercall when receiving this intent.com.google.android.play.engage.action.PUBLISH_CONTINUATIONIt is recommended to start apublishContinuationClustercall when receiving this intent.
Integration workflow
For a step-by-step guide on verifying your integration after it is complete, see Engage developer integration workflow.
FAQs
See Engage SDK Frequently Asked Questions for FAQs.
Contact
Please contact engage-developers@google.com if there are any questions during the integration process. Our team will reply as soon as possible.
Next steps
After completing this integration, your next steps are as follows:
- Send an email to engage-developers@google.com and attach your integrated APK that is ready for testing by Google.
- Google will perform a verification and review internally to make sure the integration works as expected. If changes are needed, Google will contact you with any necessary details.
- When testing is complete and no changes are needed, Google will contact you to notify you that you can start publishing the updated and integrated APK to the Play Store.
- After Google has confirmed that your updated APK has been published to the Play Store, your Recommendation, Featured, and Continuation clusters will be published and visible to users.