The related browse action allows listeners to browse your service for music related to the current item. The following shows an example in the Info View of a related browse action. [block:image] { "images": [ { "image": [ "https://sonos-partner-documentation.s3.amazonaws.com/ReadMe-External/content-service-features/add-actions/related-browse/SonosApp-RelatedBrowse.png", null, "" ], "align": "center", "sizing": "55% " } ] } [/block] The following steps describe how to implement the related browse action: 1. Define the text string in your [i18next](doc:localization#i18next-file) file that is to display in the Info View of the Sonos app. ("Related Songs"). ```json { "en-US":{ "common":{ ... }, "integration":{ "RELATED_SONGS": "Related Songs" ... } }, } ``` 2. When the listener selects the ellipsis (...) to see the Info View, Sonos sends your service a [`getExtendedMetadata`](doc:getextendedmetadata) request. This example is for a track `itemType`. ```xml ... t:123456 ``` 3. Include all the custom action items for the Info View in your `getExtendedMetadata` response. To simplify this example we'll show a related browse custom action. ```xml t:123456 track This is the title Alternative audio/mp3 a:12345678 Example Artist M:123456 Alternative 236 true true true . . . Details for other custom actions in the Info View are not shown . . . related-t:123456 RELATED_SONGS ``` 4. Note the following about `relatedBrowse`: | Element | Description | | ------- | --------------------------------------------------------------------------------------------------------------------------------------------- | | `id` | The value `related-t:123456` identifies the service’s tracks related to the current track, `t:123456`. The pattern of these IDs is up to you. | | `type` | The value `RELATED_SONGS` corresponds to the JSON key in the i18next file above. | 5. When a listener chooses a `relatedBrowse` action, the Sonos app sends a [`getMetadata`](doc:getmetadata) request to your service using the given related browse `id` (`related-t:123456`). 6. Your service should respond to [`getMetadata`](doc:getmetadata) with a `mediaCollection` of related songs.