The following describes the details of the Actions Center integration
process that are unique to Local Services Ads Redirect.
## Key Guidance
The following are examples and tutorial covering features that are required by
the Local Services Ads Redirect integration:
Feeds must be provided to Google on a regular basis for the data to be directly shown on Google.
The following feeds are needed.
| Feed | Description | Frequency |
|---|---|---|
| [Entity](https://developers.google.com/actions-center/verticals/local-services/redirect/reference/feeds/entity-feed) | Describes your entities. | Once every 24 hours |
| [Action](https://developers.google.com/actions-center/verticals/local-services/redirect/reference/feeds/action-feed) | Describes your deep links associated with your entities. | Once every 24 hours |
> [!NOTE]
> **Objective:** When you provide service names and descriptions, adhere to our [Content editorial guidelines](https://developers.google.com/actions-center/verticals/local-services/redirect/support#content-editorial-guidelines).
The feeds format is described with the
[protocol buffer 3 syntax](https://developers.google.com/protocol-buffers/docs/proto3) but you can upload your feeds
as the corresponding JSON format.
Please reference the feed samples below
- [Entity Feed](https://developers.google.com/actions-center/verticals/local-services/redirect/reference/feeds/entity-feed)
- [Action Feed](https://developers.google.com/actions-center/verticals/local-services/redirect/reference/feeds/action-feed)
We recommend that you upload the feeds in JSON format.
## Upload the feeds to your SFTP server
Upload your feeds to the sandbox environment. To do so, refer to the
usernames within the
[Partner Portal feed configuration](https://developers.google.com/actions-center/verticals/local-services/redirect/partner-portal/testing/feeds) page. The Google SFTP server is
available at `sftp://partnerupload.google.com` on port
`19321`.
> [!NOTE]
> **Note:** To access the sandbox, make sure that the [environment switcher](https://developers.google.com/actions-center/verticals/local-services/redirect/partner-portal/overview/environment-switcher) on the top is set to Sandbox.
We recommend that you give the files you upload unique names. For instance,
it can be helpful to append each filename with a timestamp. This helps to
troubleshoot issues and query for feed status.
> [!NOTE]
> **Note:** All feeds should be uploaded to the **Generic** SFTP server.
 Ensure you are uploading all feeds to the 'Generic' account.
Each feed needs to be uploaded through SFTP separately with a fileset descriptor file.
The filename of a fileset descriptor should be **\-\<
generation_timestamp\>.filesetdesc.json** ,
in which **\** should correspond to the following for each feed:
| Feed | FilesetDescriptor.name |
|---|---|
| Entity | `reservewithgoogle.entity` |
| Action | `reservewithgoogle.action.v2` |
Visit [Using the Generic feed SFTP server](https://developers.google.com/actions-center/verticals/appointments/redirect/reference/tutorials/generic-sftp)
for more information.
> [!WARNING]
> **Warning:** Upload your feeds to the production servers only after Google has tested and confirmed your feeds in the sandbox environment.
## Google evaluates feeds
Once you upload your feeds, Google processes and evaluates them for quality
and completeness. We look at several factors:
- Feeds meet the specifications.
- Feeds include all required fields.
- Each merchant has at least one `action_link` and one service with at least `action_link` defined.
- The majority of your merchant data matches with Google Maps locations.
> [!NOTE]
> **Note:** To ensure a smooth integration, perform a pre-evaluation of the factors above, except for the last one, before you submit your feeds.