피드 파일이 준비되면 안전한 위치에 호스팅하세요. Google은 콘텐츠가 최신 상태로 유지되도록 정기적으로 피드를 가져옵니다(일반적으로 하루에 한 번). Google 담당자와 협력하여 호스팅 세부정보와 호스팅된 위치에서 피드를 가져오는 가장 좋은 시간을 공유합니다.
피드 호스팅 권장사항
피드를 호스팅하는 가장 좋은 방법과 호스팅된 위치에서 피드가 구성되는 방식은 데이터 제공업체의 재량에 따르지만, 원활한 가져오기를 위해 피드를 구성하는 방법에 관한 몇 가지 권장사항을 소개합니다.
'latest'라는 폴더를 만듭니다(대소문자 구분 안 함). 이 폴더는 매일 JSON 피드 파일로 업데이트되며 Google이 특정 시점에 가져와야 하는 파일만 포함되어야 합니다.
최신 폴더 아래에 하위 폴더를 만들지 마세요. 계층 구조를 단순하게 유지합니다. 즉, 모든 JSON 파일이 '최신' 폴더 바로 아래에 있어야 합니다.
원하는 경우 'date-time'이라는 이름의 폴더에 지난 30일간의 피드를 저장하도록 선택할 수 있습니다. 이는 이전 버전의 피드에 문제가 있거나 이전에 제공된 메타데이터를 조회해야 하는 경우에 유용합니다. Google은 이러한 폴더를 어떤 방식으로도 사용하지 않습니다.
'최신' 폴더에 크기가 0KB인 파일/빈 파일이 없어야 합니다.
파일을 원활하게 가져올 수 있도록 Google이 항상 '최신' 폴더에 액세스할 수 있는지 확인합니다.
Google에서 스테이징 피드를 요청하는 경우 스테이징 피드를 호스팅할 별도의 폴더를 만들어야 합니다. 예를 들어 프로덕션 피드의 계층 구조가 ../latest/인 경우 스테이징 피드에 다른 계층 구조(예: ../staging/latest/)를 만들 수 있습니다.
호스팅 방법
아래 표에는 지원되는 피드 호스팅 방법과 Google 담당자와 공유해야 하는 세부정보가 나와 있습니다.
메서드
세부정보 필요
인증 지원
Google Cloud Storage(GCS)
GCS 객체, 버킷 또는 폴더 URL
액세스 사용자 인증 정보
피드를 매일 한 번 가져오는 데 가장 좋은 시간
Google Cloud Storage URL은 `088794101-100000002-account@partnercontent.gserviceaccount.com`과 공유해야 합니다(스토리지 객체 뷰어 권한).
Google Cloud Storage에 피드 호스팅 섹션에서 자세한 내용을 확인하세요.
[null,null,[],[[["\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,["# Host the feed file\n\nOnce 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------------------------------------\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---------------\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-------------------------------------\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."]]
