Bond can plug into the website you already have, whether it's built on WordPress, Webflow or another platform. This article walks through your options, from a simple link to a fully custom experience, so you and your web team can plan how customers find your programs and register.
Your options at a glance
Option | What it is | Best for |
Link out | A button or link that opens Bond registration in a new page | The quickest start, emails and social posts |
Embedded iframe | Bond registration shown directly on a page of your site | Keeping customers on your site from start to checkout |
Discovery page | One page listing all your programs and schedules, with filters | A "View all programs" page that updates itself |
Public APIs | Pull program data into pages you design yourself | Fully custom, branded browsing and search |
Deep links: send customers straight to a program
Every Bond program has its own URL. You can link or embed that URL anywhere to take customers straight into registration for that program, for example from a "Register now" button on your summer camp page or an ad campaign.
You can use deep links for some programs and a discovery page for others, and compare which drives more registrations.
Embedding Bond on your site (iframe)
An iframe shows Bond's registration flow inside a page of your website. Customers pick a program, create their account, sign waivers and pay without leaving your site.
You can embed a single program, or a discovery page with all your programming.
Bond's iframe is built to fill the full width of the page and has a fixed footer, so a few styling steps keep it working well on mobile.
For setup steps and example code, see Best practices for embedding Bond registration iframes.
Discovery pages: all your programs in one place
A discovery page shows all of your programs and schedules on one page, with filters, details and register buttons. It pulls directly from your Bond back office, so new programs and pricing changes show up automatically, with nothing to update on your website.
You can link to it or embed it, and customers stay in the same flow when they click to register. Your Customer Success rep can set one up for you. See Program Discovery Pages.
Build your own pages with Bond's public APIs
If you'd like full control over how programs are presented, your developers can use Bond's public APIs to pull program details such as name, price and availability into pages you design. For example, you could build your own search with filters for sport, age, day and time of day. When a customer chooses a program, deep-link them into Bond's registration (embedded or linked) to complete checkout.
Want an API key? Reach out to your Customer Success rep to get an API key. It gives you access to Bond's public APIs so you can restructure your website pages around your Bond data.
This option takes more work on your web team's side than an embed or discovery page.
Conversion tracking (Google Tag Manager and GA4)
You can track the full registration funnel, even when Bond is embedded in an iframe. Bond sends checkout events, through to purchase and amount, back to your page so Google Tag Manager or GA4 can record them. Your tracking keeps working whether customers land on a discovery page first or go straight into registration.
Embedded setups need a few scripts on your website. Start with Getting Started: Conversion Analytics.
Branding and content
Brand colors: set your primary, secondary and text colors in the back office under Organization Settings → Profile → Organization Branding. See Set Your Organization's Brand Colors.
Program content: program names, images and pricing come straight from your Bond back office. Keep them complete and up to date there, and they'll be correct everywhere they appear.
Planning your rollout
Start simple. Many facilities launch by linking or embedding Bond registration on their existing pages, then add dedicated landing pages for key programs later.
Landing pages for campaigns. For ads and promotions, a dedicated page for the program (such as summer camp) usually works better than a general location page. Embed or deep-link registration on that page.
Decide page by page. Choose where customers should see an overview page first and where they should go straight into registration.
Multiple locations: if your site uses a template for each location, build the Bond integration once in that template and duplicate it, rather than rebuilding it for every location.
Getting help
Your Customer Success rep can help you choose the right approach, set up discovery pages, provide an API key, and test your embed and tracking with you.