Stay organized with collections
Save and categorize content based on your preferences.
When you use media recommendations, you can demote recommendations based on
viewer data or content age. Recommendations that meet the demotion criteria that
you specify are demoted to the bottom of the results list. This feature is
available only for media recommendations, not for custom search and recommendations.
Demotion is set on the serving config level. You can have multiple
serving configs per media recommendations app, each with a different
demotion setting. For more information about serving configs, see
Create and manage serving configs.
Demote based on viewer data
You can demote recommendations based on how an end user has recently interacted
with the recommended content.
If your recommended content has a detail page, then you can demote it if the
user has recently viewed it. If your content is playable media, then you can
demote it depending on the amount of time the user played it or the percentage
of the content that the user played.
To demote recommendations based on viewer data:
In the Google Cloud console, go to the AI Applications page.
Click the name of the app that you want to configure recommendations for.
Go to the Configurations > Serving tab.
If you have more than one serving config, select the serving config that you
plan to set demotion for.
In the Recommendation demotion section, turn on the
Demote recommendations based on viewer data toggle to see the available demotion
options.
Select your demotion option and, if prompted, enter a threshold value for
when to trigger demotion.
Click Save and publish.
Demote based on content age
You can demote playable content based on its age. You set the age threshold in
days, and any content that reaches that age is demoted to the bottom of the
results list.
To demote recommendations based on content age:
In the Google Cloud console, go to the AI Applications page.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-25 UTC."],[[["\u003cp\u003eMedia recommendations can be demoted based on viewer data or content age, pushing them to the bottom of the results list.\u003c/p\u003e\n"],["\u003cp\u003eDemotion settings are configured at the serving config level, allowing for multiple serving configs per media recommendations app, each with unique demotion criteria.\u003c/p\u003e\n"],["\u003cp\u003eViewer data demotion can be based on how recently an end user interacted with content, such as viewing a detail page, or the amount/percentage of playable content they consumed.\u003c/p\u003e\n"],["\u003cp\u003eContent age demotion allows you to specify a threshold in days, after which playable content will be demoted.\u003c/p\u003e\n"],["\u003cp\u003eConfiguring demotion can be done in the \u003cstrong\u003eAgent Builder\u003c/strong\u003e page in the Google Cloud Console, in the \u003cstrong\u003eServing\u003c/strong\u003e tab, where the corresponding setting can be toggled on.\u003c/p\u003e\n"]]],[],null,["# Demote media recommendations\n\nWhen you use media recommendations, you can demote recommendations based on\nviewer data or content age. Recommendations that meet the demotion criteria that\nyou specify are demoted to the bottom of the results list. This feature is\navailable only for media recommendations, not for custom search and recommendations.\n\nDemotion is set on the serving config level. You can have multiple\nserving configs per media recommendations app, each with a different\ndemotion setting. For more information about serving configs, see\n[Create and manage serving configs](/generative-ai-app-builder/docs/serving-configs).\n\nDemote based on viewer data\n---------------------------\n\nYou can demote recommendations based on how an end user has recently interacted\nwith the recommended content.\n\nIf your recommended content has a detail page, then you can demote it if the\nuser has recently viewed it. If your content is playable media, then you can\ndemote it depending on the amount of time the user played it or the percentage\nof the content that the user played.\n\nTo demote recommendations based on viewer data:\n\n1. In the Google Cloud console, go to the **AI Applications** page.\n\n [AI Applications](https://console.cloud.google.com/gen-app-builder/start)\n2. Click the name of the app that you want to configure recommendations for.\n\n3. Go to the **Configurations** \\\u003e **Serving** tab.\n\n4. If you have more than one serving config, select the serving config that you\n plan to set demotion for.\n\n5. In the **Recommendation demotion** section, turn on the\n **Demote recommendations based on viewer data** toggle to see the available demotion\n options.\n\n6. Select your demotion option and, if prompted, enter a threshold value for\n when to trigger demotion.\n\n7. Click **Save and publish**.\n\nDemote based on content age\n---------------------------\n\nYou can demote playable content based on its age. You set the age threshold in\ndays, and any content that reaches that age is demoted to the bottom of the\nresults list.\n\nTo demote recommendations based on content age:\n\n1. In the Google Cloud console, go to the **AI Applications** page.\n\n [AI Applications](https://console.cloud.google.com/gen-app-builder/start)\n2. Click the name of the app that you want to configure recommendations for.\n\n3. Go to the **Configurations** \\\u003e **Serving** tab.\n\n4. If you have more than one serving config, select the serving config that you\n plan to set demotion for.\n\n5. In the **Recommendation demotion** section, turn on the\n **Demote recommendations based on content age** toggle.\n\n6. Enter a content age threshold value for when to trigger demotion.\n\n7. Click **Save and publish**."]]
