What OpenCourt sends to Meta and Google — and what it never sends

A plain-English breakdown of the conversion data OpenCourt shares with ad platforms, how it protects your customers' privacy, and what stays private.

When you turn on Ad and Conversion Tracking, OpenCourt reports your online sales to the ad platforms you connect — so Meta and Google can see which ads actually bring in paying customers. This page explains exactly what gets sent, and just as importantly, what never does.

Ad and Conversion Tracking is in public beta. To turn it on for your club, email support@getopencourt.com or your OpenCourt customer success manager.

The events OpenCourt reports

Four things get reported, and only these:

  • A page view — someone visited your club's booking pages (sent from their browser).

  • A checkout started — someone reached the payment step (sent from their browser).

  • A purchase — someone actually paid for something online. This one is sent from OpenCourt's servers using Meta's Conversions API, not from the customer's browser — so it still arrives even when ad blockers or iOS privacy settings block browser tracking. Your purchase data is the signal that matters most, and server-side delivery is what keeps it reliable.

  • A new membership — when someone buys their first membership, a Subscribe event is sent alongside the purchase (never instead of it). Renewals, bookings, events, and store sales report a purchase only.

Google gets the same picture: GA4 receives page_view, begin_checkout, and purchase, and Google Ads receives the purchases as offline click conversions.

The value reported is what the customer actually paid

Each purchase carries the net cash captured — the amount after any promo code, pass, or account credit — never the list price. That keeps your ad optimization honest: the platforms learn to find customers based on real revenue, not inflated sticker prices.

Front-desk sales are excluded — on purpose

Sales your staff ring up at the front desk (admin and POS sales) are never sent. A walk-in who paid at the counter didn't come from an online ad, and mixing that revenue in would teach the ad platforms the wrong lessons about which ads work. Only online sales — the ones an ad could plausibly have driven — are reported.

What travels with each purchase

A few extra fields go along with every purchase so the platforms (and you) can tell sale types apart:

Field

What it contains

content_category

Which kind of sale it was — one of: membership, membership_renewal, court, event, store, coach_lesson, gift_card

content_name

The real name of what was bought — the membership plan, product, event, or court/bay label

content_ids / contents / num_items

The itemized contents of the order

is_new_customer

Whether this was the person's first purchase at your club

membership_status

A coarse label only: member, non-member, or lapsed

Customer identifiers are hashed before they leave OpenCourt

For an ad platform to credit a sale to an ad, it needs to recognize which of its users made the purchase. OpenCourt handles this with one-way hashing (SHA-256): the customer's email, phone number, and a per-club customer ID are scrambled into a fingerprint before sending. Meta or Google can match that fingerprint against the hashes of their own logged-in users — but the raw email and phone number are never transmitted, and a hash can't be reversed back into them. You get accurate ad attribution without handing over your customer list in readable form.

No card or payment details are ever sent. OpenCourt only sends what ad platforms need to match a sale to an ad.

Your responsibilities

When you turn the feature on, OpenCourt shows a data-sharing disclosure that you accept — that covers OpenCourt's side of the sending. Your club remains responsible for its own privacy disclosures: your privacy policy should mention ad-platform data sharing, and your region may require a cookie or consent banner (for example under GDPR in Europe or CPRA in California). This isn't legal advice — if you're unsure what your region requires, check with a legal advisor.