How can I embed the ticketing purchase experience right into my website?

We get it - you've fought long and hard to get traffic to your website, and you want to keep them there!  No problem.  We think you deserve to keep that traffic on your site as well, and we designed a feature just to help make that experience as seamless as possible.

If you want to embed the ticketing experience right into your website, follow these instructions:

For a specific event:

1) Enter your admin dashboard by clicking the "Account" dropdown menu in the top-right corner and selcting "Admin"
2) Select the "Events" link at the top of the page
3) Select "Embed" from the list of options in your event's drop down menu
4) Copy and paste the iframe code into your website's code.
5) The default width and height are set to 1000px (width) by 700px (height). You can customize these by adjusting the width and height values in the iframe code. For use with mobile devices, we recommend using a percentage width instead of pixels. Using pixels may expand your embedded iframe off the screen, while a percentage will scale to fit the screen of whatever device is being used. To do this change the "1000px" value in the width setting to a percentage, such as "100%".


For all events at one venue:

1) Enter your admin dashboard by clicking the "Account" dropdown menu in the top-right corner and selcting "Admin"
2) Select the "Venue" link at the top of the page
3) Select the "Embed" link under your venue (first link in the row)
4) Copy and paste the iframe code into your website's code.
5) The default width and height are set to 1000px (width) by 700px (height). You can customize these by adjusting the width and height values in the iframe code.  For use with mobile devices, we recommend using a percentage width instead of pixels. Using pixels may expand your embedded iframe off the screen, while a percentage will scale to fit the screen of whatever device is being used. To do this change the "1000px" value in the width setting to a percentage, such as "100%".



For all of your events on Passage:

1) Enter your admin dashboard by clicking the "Account" dropdown menu in the top-right corner and selcting "Admin"
2) Select the "Events" link at the top of the page
3) Click the "Embed Events" link 
4) Copy and paste the iframe code into your website's code.
5) The default width and height are set to 1000px (width) by 700px (height). You can customize these by adjusting the width and height values in the iframe code.  For use with mobile devices, we recommend using a percentage width instead of pixels. Using pixels may expand your embedded iframe off the screen, while a percentage will scale to fit the screen of whatever device is being used. To do this change the "1000px" value in the width setting to a percentage, such as "100%".

Please Note (Updated Fall 2016): 

Recently, Safari made some changes that prevents session data from being passed to SSL sites embedded within a non-secure site. Sadly, this basically eliminates all e-commerce when embedded via an iframe in a non-secure site, because that session data is needed to track the checkout session. that means that embedding ticket sales could have issues with any iOS users who are also using Safari. The result is that this prevents tickets from being added to the cart for a user on an updated version of Safari on iOS. 

Because of this, we recommend having a link above the embed saying something like "Using Safari? Click HERE for tickets." That goes directly to the listing of events. 

If you run into anyone who says they're coming up with an empty cart, that would be because of this change by Safari. There are two really quick fixes: 

  1. They can use a different browser (no other browsers block the session data when embedded in an insecure page). 
  2. They can checkout by directly going to the event listing (No embed = no blocked session data). 

We're very sorry for the inconvenience (Safari didn't warn us either). We're actively researching and working on new ways to embed ticket sales within your site without using an iframe embed to avoid this issue in the future.