Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
Quando o arquivo do feed estiver pronto, hospede-o em um local seguro. O Google busca o feed regularmente, normalmente
uma vez por dia, para garantir que seu conteúdo permaneça atualizado. Trabalhe com seu representante do Google para
compartilhar os detalhes de hospedagem e o melhor momento para buscar o feed do local hospedado.
Recomendações para hospedar o feed
Embora seja a critério do provedor de dados determinar a melhor maneira de hospedar o feed e
como ele é estruturado no local hospedado, confira algumas recomendações sobre como o feed
deve ser estruturado para permitir uma busca perfeita.
Crie uma pasta chamada "latest" (sem distinção entre maiúsculas e minúsculas). Verifique se essa pasta é atualizada diariamente com os arquivos de feed
JSON e contém apenas os arquivos que o Google precisa buscar no dia.
Não crie subpastas na pasta mais recente. Mantenha a hierarquia plana, ou seja, todos os arquivos JSON
precisam estar presentes diretamente na pasta "latest".
Opcionalmente, você pode armazenar pelo menos o feed dos últimos 30 dias em pastas com o nome "data-hora".
Isso pode ser útil caso seja necessário rastrear um problema com a versão anterior do feed ou consultar metadados fornecidos anteriormente. O Google não vai usar essas pastas.
Verifique se a pasta "latest" não tem arquivos vazios/com tamanho de 0 KB.
Verifique se o Google sempre tem acesso à pasta "latest" para que os arquivos possam ser buscados de maneira
seamless.
Caso o Google solicite um feed de preparação, crie uma pasta separada para hospedar o
feed. Por exemplo, se a hierarquia do feed de produção for ../latest/, você poderá criar uma
hierarquia diferente para o feed de pré-produção, por exemplo, ../staging/latest/.
Métodos de hospedagem
A tabela abaixo lista os métodos de hospedagem de feed compatíveis e os detalhes necessários para compartilhar com representantes do Google.
Método
Detalhes obrigatórios
Suporte para autenticação
Google Cloud Storage (GCS)
URL de objetos, buckets ou pastas do GCS
Credenciais de acesso
Melhor horário para buscar o feed uma vez por dia
Os URLs do Google Cloud Storage precisam ser compartilhados com `088794101-100000002-account@partnercontent.gserviceaccount.com`
(permissão de leitor de objetos do Storage). Confira mais detalhes na seção
Hospedar o feed no Google Cloud Storage.
No menu de navegação, clique em Storage > Browser.
Se você ainda não se inscreveu no Google Cloud Storage, clique em Inscrever-se para um teste sem custo financeiro para iniciar o teste. Você pagará por esse serviço apenas depois de acumular custos. O pagamento será efetuado por meio de uma cobrança automática quando você atingir o limite para faturamento ou 30 dias após o último pagamento automático, o que ocorrer primeiro.
Depois de se inscrever para um teste sem custo financeiro, atualize o navegador para atualizar a tela.
Clique em Criar bucket.
Nomeie o bucket e clique em Criar.
Na página "Detalhes do bucket", clique em Fazer upload de arquivos.
[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."]]
