Skip to main content

What does it mean to integrate Nettla with a third-party app?

Which apps you can connect, what data Nettla sends, how club and company setups interact, and where to get help.

Written by Nettla

An integration sends your Nettla data, such as players, bookings and payments, automatically to another tool you use, like Mailchimp, HubSpot or BigQuery. You connect them yourself in Settings → Integrations.

Apps you can connect

  • Mailchimp and HubSpot: player contact details for email marketing and CRM.

  • Mixpanel and BigQuery: all data for analysis and reporting.

  • Zapier, Google Sheets and Webhook: all data for automations and your own systems. Webhook is available at club level only.

Lights and door access, court cameras and booking aggregators are set up on the same page. See their own articles.

What data is sent

Data is sent as events in four categories:

  • User Events: player details, membership and cohort changes.

  • Booking Events: bookings created, changed, joined, cancelled and completed.

  • Payment Events: payments reserved, paid, refunded and so on.

  • Court Events: how many hours each court was bookable each day, for occupancy.

You can choose which categories each app receives with the gear icon. See "How do I choose which events are sent to an integration?".

Club and company integrations

  • You can set up integrations for a single club (club Settings → Integrations) or for your whole company (company Settings → Integrations).

  • If a club has its own integrations set up, they replace the company's for that club. That club's events then stop going to the company's apps.

Getting the most out of it

Setting up dashboards, automations and data flows in these tools often needs know-how for that tool. We recommend working with someone experienced in the platform, such as a HubSpot or Mixpanel specialist or a data engineer for BigQuery.

Privacy

Your club owns your player data. Players can opt out of marketing emails, and that choice is sent with their details. Always respect it. See "How do I respect players' marketing opt-outs in integrations?".

Did this answer your question?