Because our passes are built on a mobile-optimized website, and not a native app, all of our passes are delivered and accessed with a URL. When your mobile pass is created, our technology defaults to the URL of app.bandwango.com. Because Bandwango is a white labeled product, we want a passholder to see your organization's website domain after signup. Together, we will create a subdomain to take the place of our default URL. Access to your organization’s DNS is required to complete this process. It is recommended to contact whomever manages your domain to assist with this task if necessary.

The first step in the process of creating a subdomain is to choose an action word like “fun” “explore” or “experience” placed before your domain name (word.yoursite.com). Once chosen and relayed to our team, we will create a target in our database that the subdomain can be pointed to within your DNS. To learn more about that process click here.

No. We can only create one subdomain URL per partner, which is why we recommend you choose a generic naming convention for your pass URL to account for any future mobile pass initiatives. All passes you create on our platform will utilize this URL

No. We encourage you to use your existing website to host and promote all of your passes, taking advantage of the marketing efforts you’re already using to drive traffic to your site. However, if you want to create a new domain to house and brand all of your Bandwango passes under, you can purchase said domain, and use that to create your subdomain.

No. Your pass is hosted on app.bandwango.com, but in order to fully white-label these passes to your organization, the subdomain setup is a crucial part of the onboarding process. Additionally, customers who do not create a subdomain URL matching their brand's typical domain structure risk losing data related to website activity since website tracking platforms rely on domain structures to organize data in their systems.

The landing page you create on your website to promote your passes, is different than the actual pass link that a customer will receive when their pass is delivered to them via text and email. You will be driving traffic to your landing page that will most likely use a slug, which is a different URL structure than a subdomain. A slug is a unique identifier attached to the end of a URL, and is a part of your website architecture. For example: www.yoursite.com/attractionpass.

Integration is the process of taking dynamic html embed code generated by the Bandwango platform, and embedding them onto a landing page on your website so passholders can sign up or purchase a pass. Upon completion of Client Review of the mobile pass, Bandwango will provide html embed codes for you to embed directly into your native site. Your team and partner organizations can create any number of destination sites with your preferred tags, routing, and marketing pixels and integrate these html codes directly onto these landing pages.

Yes, but this process must be done in coordination with the Bandwango team. If you remove or redirect the subdomain in your DNS without another target to point it towards, you will cause a service interruption with your mobile passes and embedded website elements. The setup process will need to be completed again from start to finish when you have the new domain ready.