Stay organized with collections
Save and categorize content based on your preferences.
Once your feed file is ready, host it at a secure location. Google fetches the feed regularly, typically
once a day, to ensure that your content stays up-to-date. Work with your Google representative to
share the hosting details and the best time to fetch the feed from your hosted location.
Recommendations for hosting the feed
Although it's at the discretion of the data provider to determine the best way to host the feed and
how the feed is structured at the hosted location, here are some recommendations on how the feed
should be structured to enable a seamless fetch.
Create a folder named “latest” (case insensitive). Make sure this folder is updated with the JSON
feed files daily and only contains the files that Google should fetch for the day at any given time.
Do not create any subfolders under the latest folder. Keep the hierarchy flat i.e. all the json files
should be present directly under the “latest” folder.
Optionally, you can choose to store at least the last 30 days feed in folders named “date-time”.
This can come in handy in case there’s a need to track down an issue with the previous version of
the feed or lookup previously provided metadata. Google will not use these folders in any way.
Make sure the “latest” folder does not have any files with 0KB size/empty files at any given time.
Make sure that Google always has access to the “latest” folder so the files can be fetched in a
seamless manner.
In case Google requests for a staging feed, make sure a separate folder is created to host the
staging feed. For example, if the hierarchy for the production feed is ../latest/, then you can create a
different hierarchy for the staging feed, for example, ../staging/latest/.
Hosting methods
The table below lists the supported feed hosting methods and the details required to be shared with
Google representatives.
Method
Details Required
Authentication Support
Google Cloud Storage (GCS)
GCS object, bucket or folder URL(s)
Access Credentials
Best time to fetch the feed once daily
Google Cloud Storage URLs must be shared with `088794101-100000002-account@partnercontent.gserviceaccount.com`
(Storage Object Viewer permission) See more details in
Host the feed on Google Cloud Storage section
If you haven't already signed up for Google Cloud Storage, click Sign up for a free trial to start your free trial. (You pay for this service only after you reach your billing threshold or 30 days have passed.)
After signing up for a free trial, refresh the browser to update the screen.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],[],[[["\u003cp\u003eGoogle will fetch your content feed daily, or more frequently for live content, to keep your information current.\u003c/p\u003e\n"],["\u003cp\u003eStructure your feed with a "latest" folder containing daily JSON files for seamless fetching by Google.\u003c/p\u003e\n"],["\u003cp\u003eYou can optionally archive past feeds in dated folders for your own tracking purposes.\u003c/p\u003e\n"],["\u003cp\u003eChoose a hosting method from Google Cloud Storage, HTTPS, SFTP, or AWS S3, and share the details with your Google representative.\u003c/p\u003e\n"],["\u003cp\u003eWhen using Google Cloud Storage, ensure the "Storage Object Viewer" permission is granted to the designated Google account for access.\u003c/p\u003e\n"]]],["Host the feed at a secure location for Google to fetch regularly, typically once daily. Structure the feed with a \"latest\" folder containing current JSON feed files, and optionally, \"date-time\" folders for the last 30 days. Supported hosting methods include Google Cloud Storage, HTTPS, SFTP, and AWS S3, each requiring specific details and credentials shared with Google. For Google Cloud Storage, share the bucket URL and grant Storage Object Viewer permission to `088794101-100000002-account@partnercontent.gserviceaccount.com`. Then contact the Media Actions team to review the feed.\n"],null,["Once your feed file is ready, host it at a secure location. Google fetches the feed regularly, typically\nonce a day, to ensure that your content stays up-to-date. Work with your Google representative to\nshare the hosting details and the best time to fetch the feed from your hosted location.\n| **Note:** For certain use cases that require more real time data ingestion, such as Live TV use case where the programing can often update multiple times a day, Google may decide to fetch the feed more than once a day. In such cases, a representative may contact you to determine the best possible times to fetch the feed from your hosted location.\n\nRecommendations for hosting the feed\n\nAlthough it's at the discretion of the data provider to determine the best way to host the feed and\nhow the feed is structured at the hosted location, here are some recommendations on how the feed\nshould be structured to enable a seamless fetch.\n\n- Create a folder named \"latest\" (case insensitive). Make sure this folder is updated with the JSON feed files daily and only contains the files that Google should fetch for the day at any given time.\n- Do not create any subfolders under the latest folder. Keep the hierarchy flat i.e. all the json files should be present directly under the \"latest\" folder.\n- Optionally, you can choose to store at least the last 30 days feed in folders named \"date-time\". This can come in handy in case there's a need to track down an issue with the previous version of the feed or lookup previously provided metadata. Google will not use these folders in any way.\n- Make sure the \"latest\" folder does not have any files with 0KB size/empty files at any given time.\n- Make sure that Google always has access to the \"latest\" folder so the files can be fetched in a seamless manner.\n- In case Google requests for a staging feed, make sure a separate folder is created to host the staging feed. For example, if the hierarchy for the production feed is ../latest/, then you can create a different hierarchy for the staging feed, for example, ../staging/latest/.\n\nHosting methods\n\nThe table below lists the supported feed hosting methods and the details required to be shared with\nGoogle representatives.\n\n|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| **Method** | **Details Required** | **Authentication Support** |\n| Google Cloud Storage (GCS) | - GCS object, bucket or folder URL(s) - Access Credentials - Best time to fetch the feed once daily | - Google Cloud Storage URLs must be shared with \\`088794101-100000002-account@partnercontent.gserviceaccount.com\\` (Storage Object Viewer permission) See more details in [Host the feed on Google Cloud Storage](#host_the_feed_on_google_cloud_storage) section |\n| HTTPS | - HTTP Server URL(s) - Access Credentials - Best time to fetch the feed once daily | - Username **and** Password **or** [HTTP client certificates](https://support.google.com/webmasters/answer/6073543) |\n| SFTP | - SFTP Server URL(s) - Access Credentials - Best time to fetch the feed once daily | - Username **and** Password, **or** - Username, Private Key, **and** Private Key Passphrase **or** - Combination of both of the above |\n| AWS S3 | - S3 Bucket URL(s) (Example: S3://mediafeed-bucket/latest) - S3 Bucket Region (Example: EU-WEST-1) - Access Credentials - Best time to fetch the feed once daily | - Both Access Key ID **and** Secret Access Key **or** - S3 Buckets with unrestricted access (not preferred) |\n\nAfter you upload your feed file(s) using one of the above methods, contact the Media Actions team\nto review your feed file(s).\n\nHost the feed on Google Cloud Storage\n\nThe following steps demonstrates how to upload a feed file on Google Cloud Storage:\n\n1. Log in to [Google Cloud Platform console](https://console.cloud.google.com)\n and click the **Select a project** dropdown menu.\n\n2. In the pop-up window, click **NEW PROJECT**.\n\n3. Name your new project and click **CREATE**.\n\n4. On the navigation menu, click **Storage \\\u003e Browser**.\n\n5. If you haven't already signed up for Google Cloud Storage, click **Sign up for a free trial** to start your free trial. (You pay for this service only after you reach your billing threshold or 30 days have passed.)\n\n6. After signing up for a free trial, refresh the browser to update the screen.\n\n7. Click **Create bucket**.\n\n8. Name your bucket and click **Create**.\n\n9. On the Bucket details page, click **Upload files**.\n\n10. Upload your [feed file](./create-a-feed).\n\n | **Note:** Media Actions expect the feed to be updated regularly. To learn how to programmatically upload files to your Cloud Storage bucket, see this [page](https://cloud.google.com/storage/docs/uploading-objects).\n11. On the Bucket details page, click **Permissions**.\n\n12. Click **Add members**.\n\n13. In the **New members** field, enter the following email address:\n\n 088794101-100000002-account@partnercontent.gserviceaccount.com\n\n14. In the dropdown, select **Storage Object Viewer** and click **Save**.\n\nAfter you upload your feed file to a host system, contact the Media Actions team to review your feed file."]]
