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.

### Can I provide multiple localized URLs for different locales?

While the feed specification allows multiple locale entries in `localized_url`,
the serving system stores and serves only a single URL per event or ticket.
Dynamic URL selection based on user location or language setting is not
supported. If multiple entries are provided in `localized_url`, a single URL
will be selected and served globally. We recommend configuring your event
landing pages to automatically detect user language (e.g., using browser
`Accept-Language` headers or IP-based location) and redirect users to the
appropriate localized page.

## 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:

1. 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.

2. Once implementation is complete on sandbox, the Google team will do a review
   comparing the sandbox and production environment data.

3. 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.

4. As with the sandbox, partners will need to set up credentials for the
   generic feed SFTP server.

5. Partners then should turn off the automated uploads to the prod environment
   for the legacy uploads.

6. Partners can upload the new feed to production to complete the switch over.

> [!NOTE]
> **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.

### 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
- Much better error messages
- Only a single feed instead of 3 feeds
- Faster processing times