Stay organized with collections
Save and categorize content based on your preferences.
The following are a list of frequently asked questions by partners when
onboarding or migrating from the legacy feed spec.
General questions
The following are a list of frequently asked questions.
Should I use the legacy or new feed spec when onboarding?
The v1 feed spec is now fully launched and therefore should be used.
Multiple tickets are supported in the feed spec, should I send all tickets
While we do support multiple tickets we still recommend sending only the
cheapest single adult ticket information. Multiple tickets should be used in
cases where there are multiple sellers for the same event.
Migration related questions
The following are a list of frequently asked questions related to migrating
from the legacy feed spec.
What are the key differences between the legacy spec and the new single feed spec
Feed metadata is provided by a separate file upload.
Instead of three separate feeds (service, merchant, availability), we now
require only a single events feed to be uploaded in addition to the metadata
feed.
Proto definitions of the new spec is much cleaner and include only events
related fields.
You can now send us multiple tickets per event, each with its own availability.
Certain fields such as action_links, prices have been renamed and reworked
Many of the structures have been simplified, for example: contents of the old
ticketing_vertical_specific_data has been flattened out.
How does the migration process work?
Migration process is as follows:
When you are ready to start the migration work, you can upload directly to
the sandbox (partnerdev) environment. Make sure to use the generic SFTP
endpoint when uploading.
Once implementation is complete on sandbox, the Google team will do a review
comparing the sandbox and production environment data.
If there doesn't seem to be major issues, Google will make the changes to
the partner production environment so partners can prepare the upload to
production.
As with the sandbox, partners will need to set up credentials for the
generic feed SFTP server.
Partners then should turn off the automated uploads to the prod environment
for the legacy uploads.
Partners can upload the new feed to production to complete the switch over.
Can I keep using the existing feed spec?
Yes, the current feed spec will be supported into 2025. However there are a
number of advantages in using the new spec including:
Much cleaner and better defined feed specification
[[["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"]],["Last updated 2025-05-29 UTC."],[[["\u003cp\u003eThe v1 feed specification is in pilot and not yet ready for general availability, but partners can reach out to their Google counterpart if interested in using it.\u003c/p\u003e\n"],["\u003cp\u003eWhile the new spec supports multiple tickets per event, it is recommended to send only the cheapest single adult ticket information unless there are multiple sellers for the same event.\u003c/p\u003e\n"],["\u003cp\u003eMigration to the new spec involves a multi-step process including sandbox testing and review by Google before production rollout.\u003c/p\u003e\n"],["\u003cp\u003ePartners can continue using the existing feed spec into 2025, but the new spec offers advantages such as a cleaner definition, better error messages, a single feed, and faster processing times.\u003c/p\u003e\n"]]],["Partners migrating from the legacy feed spec should be aware of key differences in the new spec: a single events feed plus a metadata file replaces three separate feeds, and multiple tickets per event are now supported. The migration involves contacting Google, setting up sandbox and production environments, and uploading the new feed. Partners can use either format for now, but there is an advantage to switching to the new spec which offers faster processing and a simpler format.\n"],null,["# Frequently asked questions\n\nThe following are a list of frequently asked questions by partners when\nonboarding or migrating from the legacy feed spec.\n\nGeneral questions\n-----------------\n\nThe following are a list of frequently asked questions.\n\n### Should I use the legacy or new feed spec when onboarding?\n\nThe v1 feed spec is now fully launched and therefore should be used.\n\n### Multiple tickets are supported in the feed spec, should I send all tickets\n\nWhile we do support multiple tickets we still recommend sending only the\ncheapest single adult ticket information. Multiple tickets should be used in\ncases where there are multiple sellers for the same event.\n\nMigration related questions\n---------------------------\n\nThe following are a list of frequently asked questions related to migrating\nfrom the legacy feed spec.\n\n### What are the key differences between the legacy spec and the new single feed spec\n\n- Feed metadata is provided by a separate file upload.\n- Instead of three separate feeds (service, merchant, availability), we now require only a single events feed to be uploaded in addition to the metadata feed.\n- Proto definitions of the new spec is much cleaner and include only events related fields.\n- You can now send us multiple tickets per event, each with its own availability.\n- Certain fields such as action_links, prices have been renamed and reworked\n- Many of the structures have been simplified, for example: contents of the old ticketing_vertical_specific_data has been flattened out.\n\n### How does the migration process work?\n\nMigration process is as follows:\n\n1. When you are ready to start the migration work, you can upload directly to\n the sandbox (partnerdev) environment. Make sure to use the generic SFTP\n endpoint when uploading.\n\n2. Once implementation is complete on sandbox, the Google team will do a review\n comparing the sandbox and production environment data.\n\n3. If there doesn't seem to be major issues, Google will make the changes to\n the partner production environment so partners can prepare the upload to\n production.\n\n4. As with the sandbox, partners will need to set up credentials for the\n generic feed SFTP server.\n\n5. Partners then should turn off the automated uploads to the prod environment\n for the legacy uploads.\n\n6. Partners can upload the new feed to production to complete the switch over.\n\n| **Note:** at any point, partners can rollback and reupload in the legacy feed format in case something went wrong with the new spec. Both formats are supported by Google concurrently, Google will take the latest upload from either formats as the latest upload.\n\n### Can I keep using the existing feed spec?\n\nYes, the current feed spec will be supported into 2025. However there are a\nnumber of advantages in using the new spec including:\n\n- Much cleaner and better defined feed specification\n- Much better error messages\n- Only a single feed instead of 3 feeds\n- Faster processing times"]]