How to Set up Member Space Tracking

Reach out to our team to have the Space Member Tracking Feature activated.
Once the feature is activated, go to Setup » Tracking and choose your tracking provider.

Cobot Setup menu showing Tracking option selected.

Custom JavaScript remains under Customize » JavaScript. More details.

Important Notes

Tracking scripts only load after a visitor grants the relevant Cookie Consent (Analytics for GTM, Marketing for Meta Pixel).
If your space uses the no_cookie_banner feature, you are responsible for consent and Cobot loads your tracking configuration immediately.

Available Tracking Providers

Meta Pixel

Choose Meta Pixel.
Enter your Pixel ID (digits only).
Click Save Tracking.

How to Track with Meta Pixel

Cobot loads the Meta Pixel base code after Marketing Cookie consent (ad_storage).
Cobot events are sent with fbq('trackCustom', eventName, properties).

These Cobot events also map to standard Meta events:

membership_signup_completed → CompleteRegistration
time_pass_purchase_completed → Purchase

Google Tag Manager

Choose Google Tag Manager.
Enter your container ID (GTM-XXXXXXX).

How to Track with Google Tag Manager

Cobot loads GTM after analytics cookie consent (analytics_storage).
Every Cobot event is pushed to dataLayer as:

{ event: 'cobot.membership_signup_completed', plan_id: '...', plan_name: '...' // …other properties }

Create GTM triggers that match cobot.* event names.

Custom JavaScript

Custom scripts are configured separately under Customize » JavaScript.

$Custom JavaScript settings panel with text input area for code, info banner about embedding on public and member-facing pages, and note about {{COBOT_USER_EMAIL}} placeholder.$

Listen for Cobot events:

document.addEventListener('cobot:tracking', (e) => { const { name, properties } = e.detail; // send to your analytics tool });

Or
Call the helper directly:

window.CobotTracking.track('my_custom_event', { foo: 'bar' });

💡 Placeholder {{COBOT_USER_EMAIL}} is replaced with the signed-in user’s email when available.

More details on customizing Cobot JavaScript here.

Event Catalog

Event names are stable. Property keys may grow over time. Treat missing properties as optional.

Membership Sign-Ups

membership_signup_plan_selected: Fired when a visitor clicks Sign up on a plan on the space homepage.

{ "plan_id": "plan-1", "plan_name": "Hot Desk", "plan_price": "100.0" }

membership_signup_started: Fired when the membership sign-up form page loads.

{ "plan_id": "plan-1", "plan_name": "Hot Desk", "plan_price": "100.0" }

membership_signup_submitted: Fired when the sign-up form is submitted.

membership_signup_payment_method_started: Fired when the post-application payment method picker is shown (no method selected yet).

membership_signup_payment_method_selected: Fired when a payment method form is shown after the member selects a method.
-

{ "payment_method_id": "pm-1", "payment_method_name": "Credit Card" }

membership_signup_payment_method_submitted: Fired when the selected payment method form is submitted during sign-up.

membership_signup_completed: Fired after the membership is created (Dashboard or payment method setup page with signup_completed=true).

{ "plan_id": "plan-1", "plan_name": "Hot Desk", "membership_id": "membership-1" }

Time Pass Purchases

time_pass_purchase_started: Fired when the member opens the buy Time Passes page.

time_pass_purchase_previewed: Fired when the purchase confirmation/preview page loads.

{ "time_pass_name": "Day Pass", "time_pass_spec_id": "spec-1", "no_of_passes": 2, "price": "40.0", "currency": "EUR", "per_invoice": false }

time_pass_purchase_confirmed: Fired when the member confirms the purchase on the preview page.

time_pass_purchase_completed: Fired on the Member Dashboard after a successful purchase.

{ "time_pass_name": "Day Pass", "time_pass_spec_id": "spec-1", "no_of_passes": 2, "price": "40.0", "currency": "EUR" }

Tracking Members via Google Analytics, Meta Pixel and Co.