## Venue and Events eligibility

Read through the following eligibility criteria before beginning an
integration. If you have a specific use case that you think should be evaluated
for an exception, reach out to your Google business development contact.

## Venue eligibility criteria

For an event venue to be eligible for the Events integration, the venue must
match to a business location in the Google Maps database (ex: business name,
address, phone number, and website)

## Supported venue types

The following table lists the venue types that are supported by the Events
integration. Given the wide variety of venues that manage events, this list is
not exhaustive of all venue types. This list is updated periodically, check back
here to stay up to date.

If you have questions about whether a specific venue type is supported, email
your business development contact.

| Venue Type | Applicable Venues (Not Exhaustive) | Not Enabled (Exceptions) |
|---|---|---|
| Sports Arena | Arena, Stadium, Athletic Field, Athletic Complex, Racetrack, Sports Complex | Gyms, Fitness Centers |
| Performance Space | Concert Hall, Opera House, Theater, Convention Center, Gallery | N/A |
| Food \& Music | Restaurant, Lounge, Bar, Brewery, Winery | Hotel |
| Miscellaneous | Garden, Park, School/University, Community Center | N/A |

## Eligible Event Types

- **Single-Date Events:** Individual concerts, games, and scheduled performances.
- **Recurrent Events:** Events operating on a regular, recurring schedule (e.g., weekly theater runs) **are eligible**, provided each instance contains accurate date/time availability and corresponding ticket pricing.

**What is NOT an Event:**

- Standard business/operating hours, drop-in sessions, or facility rentals.
- Routine promotions/deals (happy hours, daily specials), ongoing camps, or ticket on-sale dates.

For more info on what qualifies as an event, please check the
[Events Eligibility page](https://developers.google.com/actions-center/verticals/events/overview.md.txt).

## Content quality standards

Partners must maintain good merchant and service data quality content. The
Actions Center may not display the service, merchant, or integration if we find
errors in the quality that would negatively degrade the user experience.

## Venue name \& address

- Venue name must accurately reflect the legal business name of the event venue.
- Venue must accurately reflect the business address of the event venue.

## Event name \& descriptions

- Event descriptions must be descriptive, and accurately reflect the corresponding event displayed in the events booking module.
- Event name and localized_description of the event must follow proper capitalization and punctuation per local grammar.
  - Full capitalization, use of emoji or emoticons is not allowed.
  - Use of vulgar or offensive language is not acceptable.
  - Not allowed in name or description:
    - Promotional content, URL, email address, or phone number
    - Payment method
- Event must be bookable by the general public. A user shouldn't have to purchase a membership or belong to an organization to purchase the ticket on the partner website.

## Partner brand

- Partner brand name must accurately reflect the legal business name of the
  event ticket seller.

- If partner is an events aggregator, the landing page should reflect the
  branding of the aggregator. The legal business name of the event ticket seller
  should be apparent on the aggregator landing page.

- If a partner logo is submitted in the feed, the logo must be the one that
  officially relates to the brand name of the event ticket seller.

- Partners must not provide brand names or logos that could mislead end
  users of their relationship with the venue, performer, or event.

## Google Price Display Policy

The price shown on Google is tailored to match local regulations and display
standards in each jurisdiction, and must include all mandatory fees and taxes by
default.

For events held in the United States, the price sent through the feed may
exclude sales taxes, unless local law requires the price to include tax.
Partners remain responsible for complying with local pricing laws.

## Support and maintenance guidelines

The following guidelines apply to Support and Maintenance.

## Integration maintenance and support

Partner is committed to supporting and maintaining the integration with Google.
At a minimum, Partner is committed to the following support functions and
standards:

- Emergency Alert and Emergency Technical Support: Partner will provide high
  priority support for technical issues which result in the integration being
  disabled or non-functioning, greatly impacting the user experience, or any
  other emergency issue. To ensure a positive user experience, the partner will
  use commercially reasonable efforts to respond to and resolve any emergency
  issues within 1 business day.

- Non-Emergency Technical Support: Partner will provide standard support for
  non-emergency technical or production issues which don't disable the
  integration. To ensure a positive user experience, the partner will use
  commercially reasonable efforts to respond to any non-emergency issues within
  2 business days.

- Post-Launch Integration Health: Partner's integration health should meet the
  Google Action Center content quality standards and comply with applicable Google
  Action Center policies such that the end user experience is not degraded.

## Partner Takedown Reasons and Issue Descriptions

The Actions Center may disable your integration or inventory as necessary
inorder to maintain the user experience. If a takedown is required, we will
send you a notification and we will work with you to resolve the issue.

The following issue types describe the root causes of inventory takedowns and
the associated policies and guidelines:

### Partner unresponsive or SLA violation

This is encountered when the Actions Center team reaches out to your team with
an issue (technical, user issue, data issue, etc.) and does not hear back within
the time outlined in the [Support and Maintenance Guidelines](https://developers.google.com/actions-center/verticals/events/policies/platform_policies.md.txt#support_and_maintenance_guidelines).

Alternatively, if the issues identified are not resolved within the timeline
given, we may disable your integration. Once the issue is resolved and confirmed
by our team, we may restore your integration. You can reach out to the partner
support team with the email reference ID you received for status updates or to
inform us the issue has been resolved.

Relevant Policy: [Support and Maintenance Guidelines](https://developers.google.com/actions-center/verticals/events/policies/platform_policies.md.txt#support_and_maintenance_guidelines)

### Place Action policy violation

Actions Center requires that Place Actions link(s) must follow specific
guidelines to ensure the user experience. For example, Place Actions link(s)
must be actionable, lead to a dedicated landing page, and reflect the
partner branding displayed on the events booking module. Google's inability to
verify performer, venue, or branding details on the landing page may result in
listings not being displayed. In case of repeated or egregious performer or
venue misrepresentation, the partner may be suspended from the platform.

Relevant Policy: [Place Actions Policy](https://developers.google.com/actions-center/verticals/events/policies/integration_policies.md.txt#place_action_policies)

### Pricing policy violation

Partners must provide accurate, up-to-date pricing through timely feed updates.
Providing false, placeholder, speculative, or artificially deflated prices is
strictly prohibited. Failure to meet these standards will result in temporary
removal of price display (hidden prices), automatic demotion, listing takedowns,
or account suspension.

Ensure that the values provided to the Actions Center are accurate and meet our
[Pricing Policies](https://developers.google.com/actions-center/verticals/events/policies/integration_policies.md.txt#pricing_policies).
Reach out to the partner support team once the issue is resolved.

### Bad match or noncompliance of matching policy

Google attempts to match your event venue with Google Maps locations. After the
venue data is associated with a location, your events will be eligible to show
on the Actions Center. In order to ensure optimal user experience, the Actions
Center will attempt to correct matches. However, in the event that there is
insufficient information to match with the right maps listing, the Actions
Center will take down merchants with bad matches.

If an error occurs while matching and there is nothing to do to resolve it,
contact Google Events Support by
[submitting a support case](https://developers.google.com/actions-center/verticals/events/support.md.txt#how-to-get-help).