# Overview

The Things to do platform enables qualifying partners to show travel activity
related items on Google-owned surfaces. The Things to do data feed is used for
advertising campaigns in Things to do ads as well as powering various Things to
do search experiences.

## Things to do surfaces

Things to do products are displayed in various formats across a number of
surfaces. To simplify requirements they can in general be split into 4 different
modules, the Ads module, booking module, experiences module and operator booking
module. Each module have different sets of feed requirements in order to be
served, for more information about specific feed requirements see
[Required and recommended fields](https://developers.google.com/actions-center/verticals/things-to-do/guides/partner-integration/required-fields).

### Things to do Ads module

By fulfilling the requirements for Things to do Ads, products are eligible
to serve on Things to do Ads using the Google Ads platform. Once Google Ads
accounts are allow listed and linked to a feed integration, feed data such as
images, title, ratings can then be used by Google Ads on the various
Things to do Ads surfaces.

### Things to do attractions booking modules

The things to do attractions booking module is designed to show users entry
ticket prices to various attraction points of interest (such as Museums, theme
parks) as well as provide a way for users to compare prices between various OTAs
and the official ticket provider. This module triggered for eligible POIs where
Google has the official ticket prices (collected internally or by partners).

Admissions include access to a tourist attraction with no add-ons or only
minor additions, such as access to an extended area, skipping the line,
priority access, and audio guides. Multi-day passes, passes with admission to
multiple points of interest, or park entries with access to multiple attractions
also qualify as Admission for tickets that don't include add-ons.
Entry tickets that include additional add-ons such as guides, transportations
services, meals, event tickets or personalized services are considered as
Experiences.

#### Things to do operator booking module (OBM)

The things to do operator booking module provides a way for tour operators to
display their products on their own Google Business Profile entry. Alongside
the tour operator products, tours provided by this operator through different
OTAs are also displayed.

For list of eligible businesses see [Operator booking module eligibility](https://developers.google.com/actions-center/verticals/things-to-do/guides/partner-integration/obm-eligibility).

> [!IMPORTANT]
> **Important:** Operator's business must be findable on Google maps in order for this module to be shown. Operators should register a Google Business Profile for their business in the case the business is not already findable on Google maps.

### Things to do experiences module

The things to do experiences module is designed to show to users the various
guided tours and experiences related to a particular points of interest.

## Data upload

Product data is uploaded by you to Google using SFTP using SSH authentication.
Things to do processing pipeline then processes and converts the data to an
internal format, which is then used by the various Things to do platforms to
serve content to the users.

The supported upload format is JSON. If there are too many activities to be
uploaded in a single file, you can upload the data using multiple files by
having the correct metadata fields in each of the uploaded files. The
Things to do processing pipeline then consider those uploads as a single
feed.

> [!NOTE]
> **Note:** Google don't support incremental updates for activities. The full set of activities should be uploaded each time (via one or more JSON files) as the previously uploaded data are then completely replaced.

## Upload cadence

How frequently the data is uploaded should be based on how often the
content of the data changes and how much it changes by. In general, Google
recommends you upload a new version of the data once per day, however you can
upload more or less often based on the size of the feed and the frequency at
which the content changes.

> [!IMPORTANT]
> **Important:** To ensure a minimum level of data freshness and provide a good user experience, Google require a production feed to be uploaded as least once every 30 days. If the data feed has not been updated after 30 days, Google reserves the right to automatically take down all products in production.

## Validation errors and warnings

Once upload has been completed, partners can then see the result of the upload
using the Action Center. Access are made available to you as part of the
integration. The Action Center provides up-to-date transfer status of your
feed uploads, a listing of product uploaded and any error messages which
occurred during processing.

The URL and credentials are shared once integration work has begun.

## Things to do policies

Contents uploaded must comply with the following policies:

- [Things to do policies](https://support.google.com/hotelprices/answer/10723240)

- [Things to do price policies](https://support.google.com/google-ads/answer/11387663)

- [Things to do official site policies](https://support.google.com/hotelprices/answer/13149532)

- [Things to do prohibited practices policies](https://support.google.com/google-ads/answer/16574455)

Products which violate the policies may be taken down by Google without
notice.

## Getting support

For integration-related technical support, you can reach out to us through our
dedicated [contact us form](https://support.google.com/travel/contact/ttd).

For contractual questions, speak to your Google representative.

### Request for business data

To initiate a new request for business data that is not already available using the reports in the Actions Center, contact us using the [Business Data Availability \& Access Form](https://support.google.com/reserve/contact/business_data_availability_and_access).