Skip to content
Tickets Please

Integration Settings

Integration Settings

Tickets Please connects with Google Maps, Gravity Forms, and WooCommerce to extend your event management capabilities. The Integration Settings panel is where you enter API keys and toggle these connections.

Navigate to Events > Settings > Integrations to configure these options.

Google Maps API Key

The Google Maps API key field accepts your Google Cloud API key for two purposes:

  1. Geocoding — Automatically converts venue addresses into latitude/longitude coordinates when you save a venue.
  2. Map embeds — Renders interactive Google Maps on single event pages that have a linked venue.

To get an API key:

  1. Go to the Google Cloud Console.
  2. Create a project (or select an existing one).
  3. Enable the Maps JavaScript API and Geocoding API.
  4. Create an API key under APIs & Services > Credentials.
  5. Restrict the key to your domain for security.

Paste the key into the Google Maps API key field and save. Maps and geocoding begin working immediately.

If you leave this field empty, map embeds will not render and venue addresses will not be geocoded automatically. You can still enter latitude and longitude manually on the venue edit screen.

Gravity Forms Integration

Two settings control the Gravity Forms connection:

  • Gravity Forms integration — Checkbox. When enabled, Tickets Please uses Gravity Forms to collect attendee information during ticket purchase and RSVP registration. Requires the Gravity Forms plugin to be installed and active.
  • Default GF form — A dropdown listing all available Gravity Forms. Select the form that should be used by default when creating new tickets. Individual tickets can override this with a different form.

When Gravity Forms integration is active:

  • The selected form renders inline during the ticket purchase or RSVP flow.
  • Form submissions are linked to the attendee record via the tickets_please_gf_form_data filter.
  • Collected data appears on the attendee detail screen in the admin.

If Gravity Forms is not installed, the checkbox is visible but non-functional. A notice reminds you to install the plugin.

Setting Up a Gravity Forms Attendee Form

  1. Create a new form in Forms > New Form.
  2. Add fields for the attendee information you need (name, email, dietary restrictions, emergency contact, etc.).
  3. Save the form.
  4. Return to Events > Settings > Integrations and select your new form as the Default GF form.

You do not need to configure Gravity Forms notifications or confirmations — Tickets Please handles attendee creation and confirmation emails independently.

WooCommerce Integration

The WooCommerce integration checkbox controls whether Tickets Please syncs with WooCommerce. This setting is auto-enabled when WooCommerce is active on your site.

When enabled:

  • Tickets can be sold through the WooCommerce checkout flow.
  • The Payment Settings panel shows WooCommerce as a payment provider option.
  • Ticket products are created and maintained automatically in WooCommerce — you do not need to create products manually.
  • WooCommerce order management, emails, and reporting apply to ticket purchases.

When disabled (or when WooCommerce is not installed):

  • Tickets are sold through the native Tickets Please checkout.
  • The WooCommerce payment provider option is hidden.

Disabling this checkbox does not delete any existing WooCommerce products or orders. It only stops future ticket sales from routing through WooCommerce.

Common Questions

Do I need a paid Google Maps API account? Google provides a free tier with generous limits (28,000 map loads and 40,000 geocoding requests per month). Most event sites stay well within these limits. You do need a billing account on Google Cloud, but you will not be charged unless you exceed the free tier.

Can I use a different mapping provider? Currently, Tickets Please supports Google Maps or no map. Set the map provider to None in Display Settings if you do not want map embeds.

What happens if Gravity Forms is deactivated after I have collected attendee data? Existing attendee data stored in Tickets Please meta fields is preserved. The Gravity Forms rendered fields will no longer appear on new ticket purchases, and the plugin falls back to its built-in attendee fields (name and email).

Can I use different Gravity Forms for different tickets? Yes. The Default GF form sets the fallback. When editing an individual ticket, you can select a different form from the ticket meta box. This is useful when different event types need different attendee information.

Does the WooCommerce integration work with WooCommerce Subscriptions? Tickets Please does not directly integrate with WooCommerce Subscriptions. Tickets are one-time purchases. For recurring event access, create separate tickets for each event instance.

Is the Google Maps API key shared with other plugins? No. The key entered here is used only by Tickets Please. Other plugins that need Google Maps (like map widgets or store locators) require their own API key configuration.

Next Steps

  • Display Settings — Control map visibility and provider selection on event pages.
  • Geocoding — Learn how venue addresses are converted to coordinates automatically.
  • Payment Settings — Choose between native checkout and WooCommerce for ticket sales.