Meta

The Meta integration connects your gym’s Meta Business account to 1Club, so bookings and sales are reported back to Facebook and Instagram as conversions. It is for the owner, or whoever runs your Facebook and Instagram ads. You connect it in one step through Meta Business Login, Meta’s own sign-in popup, where you pick your business, your dataset and your ad account - there is no pixel ID to hunt down, no access token to copy out of Events Manager, and no tag manager.

​

Why connect Meta

Meta on its own reports how many people clicked. With 1Club connected, it also sees how many of them booked and what they paid, so your ad results show bookings and revenue, and Meta can find more people like the ones who bought. The Meta pixel records page views and checkouts on your portal and website, and 1Club’s servers report the bookings and sales themselves, with the real amount. So conversions still count for visitors who block tracking scripts, and sales a browser never sees are reported too, such as a pass sold at the front desk. Typical uses:

• Putting ad spend where the bookings are - a padel gym running Instagram ads for off-peak courts sees bookings and revenue per ad set instead of link clicks, and shifts budget to the ad set that produced the bookings rather than the one with the cheapest clicks.
• Advertising for the first time - a yoga studio with no dataset creates one during setup, and can see from its first ad which ad brought people who actually bought a class pass.
• Seeing where the sale actually closes - a gym that takes most bookings at the desk sees online bookings reported as website conversions and desk bookings as in-person ones, and points its ads at a free trial rather than an online checkout.

​

What a dataset is

Meta calls the thing that collects your conversions a dataset. You may know it by its old name, the pixel - they are the same thing, and Meta renamed it. One dataset holds all the activity for one business: page views, bookings, purchases. If you have ever run a Facebook or Instagram ad with a website, you almost certainly already have one. If you have never advertised, you won’t, and 1Club can create it for you during setup.

​

Before you start

• Meta is a paid-plan feature. On the Free plan and during the trial, its Activate and Configure buttons stay greyed out until you upgrade.
• Connecting and changing the settings requires the settings.manage.organization permission. Viewing them requires settings.read.organization.
• You need a Meta Business account, and permission inside it to manage the ad account and dataset you want to use. If someone else runs your ads, they may need to do this step or grant you access first.

​

Connect Meta

1. Go to Settings > Integrations and click Activate on the Meta card, under Marketing. The Meta page opens.
2. Under Connect Meta, click Connect with Meta.
3. A Meta popup opens. Sign in, then choose the business, ad account, dataset and Facebook Page you want to share with 1Club, and confirm.
4. When the popup finishes, 1Club stores the connection, shows a Meta connected message, and opens the Meta assets card with what you shared.
5. For each kind of asset you shared exactly one of, 1Club selects it for you. If a dataset is selected, the status becomes Active straight away. If you shared several, pick the one you want in Meta assets.

Until a dataset is selected, the page shows “Pick a dataset to start. Nothing is tracked until you do.” and the status stays Inactive.

​

If you have no dataset yet

When the business you connected has no dataset, the Dataset (pixel) picker is greyed out and a New dataset name box appears below it. Type a name - your gym’s name is the usual choice, and it is what you will see in Meta Events Manager - and click Create dataset. 1Club creates it inside your business and selects it.

​

Connection status

The chip on the Connect Meta card shows one of:

• Not activated - no Meta connection exists yet.
• Inactive - a connection exists but isn’t reporting. Either no dataset is selected yet, or access was removed on Meta’s side. Pick a dataset, or click Reconnect.
• Active - a dataset is selected and conversions are being reported.

Once connected, the button changes to Reconnect, which reruns the Meta popup so you can share more assets or refresh access. Reconnecting keeps your dataset and ad account choices if you still share them, and keeps your switch settings. 1Club also checks the connection every day, and sets the status to Inactive if Meta no longer accepts it.

​

Meta assets

The Meta assets card shows your business name and lets you change what the connection points at. You can only pick from what you shared in the popup. If something is missing from a list, reconnect and share it.

• Dataset (pixel) - where your page views, bookings, and purchases are reported. Nothing is tracked without one.
• Ad account - used for audiences and campaigns. Not needed for tracking, but worth selecting now so you don’t have to reconnect later.
• Facebook Page - the Page your ads run from.

Each picker has a None option to clear a choice. A choice is saved as soon as you make it, and a Meta settings saved message confirms it. Refresh assets, next to Reconnect, reads the lists from Meta again. Use it after you create a dataset or ad account on Meta’s side, or if you think the connection was changed there. If a selected dataset or ad account is no longer shared, 1Club clears it.

​

How conversions are reported

1Club reports in two halves, and each does the part it is good at. From the browser - the Meta pixel. Loads on your member portal and website and records:

• Page view - every page a visitor opens.
• Reaching checkout - a visitor starting to pay for a booking.

From 1Club’s servers - the Conversions API. Reports what actually happened:

• Booking - when a booking is confirmed, with the amount charged. A booking held while the member pays is reported only once the payment goes through.
• Purchase - when an order is completed, with the order total.

This split matters. The pixel is blocked for many visitors, and it never knows what anything cost. Reporting bookings and purchases from 1Club’s servers means those conversions still count, carry the real revenue, and include sales that never touched a browser, such as a pass rung up at the desk.

​

Online and in-person sales are labelled differently

Meta asks every conversion where it happened, and requires the answer to be accurate. 1Club labels each one honestly:

• A booking made in the member portal, on your website, in the mobile app, or through the marketplace is reported as a website conversion.
• A booking taken at the front desk or on a kiosk is reported as an in-person conversion.
• A purchase takes the label of its bookings. A sale with no booking, such as a membership or a product rung up at the till, is reported as other, because 1Club can’t tell where it happened. So is a booking that came in through the API or another integration.

This is deliberate. Reporting till sales as website conversions would inflate your online ad results and teach Meta to optimize toward the wrong thing.

​

Cookie consent

The Meta pixel is advertising tracking, so it is covered by your cookie banner. It only loads for visitors who accept marketing cookies, and it never loads before they answer. If a visitor accepts partway through their visit, the pixel starts on that page. The Marketing category on your banner controls this. Analytics consent is separate - a visitor can allow you to measure site usage while still refusing ad tracking, and 1Club honors that. Server-side reporting is a different matter under privacy rules and isn’t governed by the browser banner. Turn it off with the Conversions API switch if your policy requires it.

​

Switching tracking on and off

Two independent switches in the Meta assets card, both on by default. A change is saved as soon as you flip the switch.

• Browser pixel - loads the Meta pixel on your portal and website. Turn it off to stop all browser-side tracking while keeping server-side reporting.
• Conversions API - reports bookings and purchases from 1Club’s servers. Turn it off to stop server-side reporting while keeping the pixel.

Turning both off keeps the connection but reports nothing.

​

Testing your setup

Meta Events Manager has a Test events tool that shows conversions arriving in real time.

1. In Meta Events Manager, open your dataset and go to Test events. Copy the test code it shows (it looks like TEST12345).
2. Paste it into Test event code on the 1Club Meta page, then click outside the field. The code is saved when you leave the field.
3. With Conversions API on, make a test booking. It appears in Meta’s Test events view within a few seconds.
4. Clear the field when you are done, and click outside it to save. It is only for testing.

​

Deactivate

1. On the Meta page, click Deactivate at the top of the page.
2. Confirm in the Deactivate Meta? dialog. It warns that the integration stops working and its settings are deleted.

1Club stops reporting conversions, the pixel stops loading on your portal and website, and 1Club hands its access back to Meta. You return to Settings > Integrations. If deactivation fails, the reason is shown inside the dialog. Your dataset and its history stay in your Meta account. Deactivating removes 1Club’s access, not your data.

​

Worked examples

Padel gym running Instagram ads for off-peak courts. The gym connects Meta and selects the dataset it already used for a previous website. Within a week, its Instagram campaign in Ads Manager shows 34 bookings worth 1,190 BGN instead of just “412 link clicks”. It shifts budget to the ad set that produced the bookings rather than the one with the cheapest clicks. Yoga studio that has never advertised. The owner connects Meta, finds the dataset list empty, and uses Create dataset with the studio’s name. She runs her first Instagram ad the following week and can see from day one which ad brought people who actually bought a class pass. Gym taking most bookings at the desk. The gym connects Meta and sees online bookings reported as website conversions and desk bookings as in-person ones. The split makes it obvious that ads drive discovery, but the sale closes in the building - so it starts pointing ads at a free trial rather than an online checkout.

​

Tips and best practices

• Select the ad account when you connect, even if you aren’t running ads yet. It costs nothing and saves reconnecting later.
• Give it a few days. Meta needs a number of conversions before it can optimize on them. Don’t judge a campaign on its first day of accurate data.
• Leave the Conversions API on. It is the half that keeps working when the pixel is blocked, and the only one that sees front-desk sales.
• Use one dataset per business. Splitting your bookings across several datasets divides the signal and makes every campaign learn more slowly.
• Clear the test event code once you have finished testing.

​

Troubleshooting

• “Meta isn’t available on this server yet.” - the Meta connection isn’t enabled for your deployment. Contact 1Club support.
• The Activate button is greyed out - Meta is a paid-plan feature. Upgrade from the Free plan or the trial.
• “Meta connect isn’t ready yet” - the Meta popup hasn’t finished loading. Wait a moment and click Connect with Meta again.
• “Pick a dataset to start. Nothing is tracked until you do.” - you connected but no dataset is selected. Pick one in Meta assets, or create one.
• The dataset list is empty - the business you shared has no dataset. Use Create dataset, or reconnect and share a business that has one.
• “Reconnect Meta before creating a dataset.” - 1Club doesn’t know which business to create it in, usually because you shared several. Click Reconnect and share only the business you want.
• The ad account or Page list is empty - you didn’t share them in the popup. Click Reconnect and select them this time.
• “That Meta asset was not shared with 1club” - the item you picked isn’t shared any more. Click Refresh assets, or reconnect and share it again.
• “Your Meta connection was revoked”, or the status went to Inactive on its own - access was removed on Meta’s side, or Meta no longer accepts the connection. Click Reconnect.
• No conversions in Events Manager - check that the status is Active, a dataset is selected, and the Conversions API switch is on. Use the test event code to watch events arrive live.
• Page views are missing but bookings appear - that is the cookie banner doing its job. Visitors who decline marketing cookies get no pixel, so browser events are always lower than server events.

​

Related

• Integrations - the full integration catalog and how activation works.
• Social booking - tagged “Book now” links that show which social platforms drive bookings.
• Google Tag Manager - load your own analytics tags on the portal and website.
• Automations - follow up with the members your ads bring in.