Marco joins
Marco picks the Glacier plan and joins through your iJoin checkout, on your site or on ours. The membership lands in ABC like any other. That is the only way iJoin ever learns a name: it keeps a keyed hash of his email, never the email, and hands his browser a signed claim good for thirty days.
That is the whole file on Marco. No profile, no trail, no third party cookie.
Marco comes back
He opens your website to look at personal training. The pixel, one line of script
on your page, sees the claim, sets a first party cookie on your domain, and fires
visitor.return.
Nobody typed anything. Nobody logged in. A stranger doing the same thing stays a stranger: a cookie, two dates and a counter, and not one page recorded.
The other penguins know
Your workflow sends the event to Zapier, or straight to an endpoint you own. Zapier turns it into whatever your team already reads: a Slack ping, a text to the front desk, a task on Marco's record in your CRM, a note to the trainer he asked about.
If your endpoint blinks, iJoin retries five times over two and a half hours and keeps a record of every attempt. If it fails twenty times running, the workflow pauses and tells you, rather than shouting into a hole.
What can fire a workflow
Nine events, each one a fact about a member, never a guess. Pick the ones you care about; ignore the rest.
| Event | When it fires |
|---|---|
visitor.identified | A known member is seen on your site for the first time from this browser. |
visitor.return | A known member is back. The one most clubs wire first. |
checkout.started | Someone opened your join flow and got as far as the plan. |
checkout.abandoned | They left before paying. The follow up writes itself. |
lead.created | A new prospect entered your funnel. |
lead.joined | That prospect became a member. |
form.submitted | Someone filled in a form on your site. An enquiry, waiting to hear back. |
join.declined | They got as far as the card and the bank said no. The most recoverable lead there is. |
join.completed | A membership went through, with the plan and the club number on it. |
What it will never do
The pixel is useful because of what it refuses. Those refusals are not a policy page. They are code paths that do not exist.
Wire it in before the noon rush
Three steps. None of them involves a developer, a server or a support ticket.
visitor.return, then connect your own Zapier account or paste the URL of an endpoint you own. Every call is signed.Next opening tomorrow
Thirty minutes with David on Google Meet, walking through iJoin against your own club system. Pick a day that suits you.
Booking , .
You are on the calendar
, thirty minutes on iJoin. The invite is on its way to , with the Google Meet link in it.
Thirty minutes with David, walking through iJoin. Real openings, read from the calendar a moment ago.
Times shown in Eastern time.
FriOct 2
None of these work? See every open time.
See the checkout it learns from
North Pole Fitness Club is a gym we invented to show the platform. Its join flow runs against a real club management system, and that checkout is where the pixel learns a member from. Walk it, then picture the whole thing in your brand instead of penguins.
- Read the plans. They come from a live club system, not a spreadsheet.
- Start a join and watch the handoff to ABC. That handoff is where Marco became known.
- Then book thirty minutes and watch David wire a workflow against your own site.
Open the demo club See its join flow
Two minutes. No sign-up, no card, nothing to install.
