Skip to content

How to sell conference tickets on your own website

You can sell conference tickets from your own site in three ways: link to a hosted checkout page, embed the ticket form inline, or open it in a popup from a button. Inline and popup embeds keep the form in your site context; a standard hosted-page link leaves your domain unless you configure a supported custom domain. Builder plans and code-block restrictions can affect setup.

By Checkout Page · Updated September 5, 2026 · 9 min read

On this page

Why sell conference tickets on your own site instead of a marketplace?

Selling on your own site can keep the ticket offer in your brand context and give you direct access to the registration data and tracking you configure, subject to the platform, privacy rules and consent choices. A marketplace can contribute discovery. Compare actual referral and completed-order data rather than assuming either channel owns the customer or causes the sale.

Discovery is the reason to evaluate a marketplace. The value varies by event and audience: measure registrations attributed to browsing separately from traffic generated by your list, speakers, sponsors, partners and paid campaigns.

Brand and statement descriptors can also affect buyer questions. Test the hosted and embedded paths with attendees and finance contacts, and state the merchant descriptor before payment when it may differ from the conference name.

Then there is data control. A checkout connected to your own systems can give you direct access to attendee details and registration answers, subject to the platform terms, privacy notice and applicable law. Access to purchase data does not automatically create permission to send marketing email; collect consent or document another lawful basis and honor opt-outs.

What are the three ways to put ticket sales on your website?

Link to a hosted ticket page, embed the ticket form inline in a page, or open it in a popup from a button. A hosted link takes seconds and needs no code. Inline suits a dedicated Tickets page. A popup suits a Buy tickets button in your navigation or hero.
MethodSetupBest forTrade-off
Hosted page linkPaste a URL into a buttonLaunching in an hour, email and social linksThe buyer leaves your domain
Inline embedOne code block in your Tickets pageYour main tickets pageNeeds a page with room for the full form
Popup or buttonOne code block plus a buttonHomepage, header, speaker pagesAn extra click before the form appears

The three methods can be combined: an inline embed on the tickets page, a popup from a site button, and a hosted link in channels that do not support embeds. Use only the paths you can test and maintain.

Two details decide which one you reach for. First, how much of the page is doing selling work: if the copy above the form is what convinces people, inline. Second, whether the buyer arrived ready to pay: from an email that already said "early bird ends Friday", a hosted link is fine and the fastest path.

How do you add tickets to WordPress, Webflow, Framer, Squarespace or Wix?

These builders offer HTML, code or embed elements, but availability can depend on plan, theme and security settings. WordPress uses a Custom HTML block, Webflow an Embed element, Framer an Embed component, Squarespace a Code block, and Wix an Embed HTML element. Confirm the current builder requirements and test the published page.
BuilderWhat to addNotes
WordPressCustom HTML block, or a full-width block in a page builderWorks in the block editor; avoid pasting into the visual editor of a classic theme
WebflowEmbed element inside your Tickets sectionPreview does not always render embeds; check the published page
FramerEmbed component set to a fixed or auto heightSet the layout to fill the section width
SquarespaceCode block on a blank sectionOn some plans, code blocks need a Business plan or higher
WixEmbed HTML elementGive the element a generous height so the form is not scrollable inside a small box

Checkout Page's embed works on all five, inline or as a popup, and every event also gets a hosted page on a checkoutpage.com subdomain that you can link from anywhere. Custom domains are available on the Scale plan if you want tickets.yourconference.com. The mechanics are in how it works.

How do you track which channel sold the tickets?

Tracking pixels and UTM parameters can support channel attribution when they are configured consistently and used lawfully. Neither produces perfect attribution: consent choices, browser controls, cross-domain navigation and the analytics setup can change what is recorded. Reconcile campaign data with completed orders.

Tracking pixels are available on Checkout Page from the Launch plan up. Add the pixel for whichever ad platform you actually spend on, and confirm it fires on the confirmation step, not just the ticket page. A pixel that only records page views tells you about interest, not revenue.

UTM parameters are simple to add to links, but the destination analytics must preserve and record them. Keep the scheme consistent:

  • Newsletter: utm_source=newsletter and utm_medium=email and utm_campaign=earlybird
  • Speaker link: utm_source=speaker and utm_medium=referral and utm_campaign=jane-doe
  • LinkedIn post: utm_source=linkedin and utm_medium=social and utm_campaign=cfp-close

Give each speaker or sponsor a tagged link when you intend to evaluate referrals, and document how completed orders are attributed. Tie the scheme to dates in your conference ticket sales timeline so each push can be reviewed separately.

What should a conference tickets page contain?

Show the current tiers, prices and primary action early, followed by agenda, speakers, venue, inclusions, FAQ and refund-policy details. This hierarchy is a reasonable starting point, not a proven universal layout. Measure clicks and completed purchases, and test it with buyers who did not design the page.

A layout that works, top to bottom:

  1. Event name, dates, city, and one line on who it is for.
  2. The ticket tiers with prices, what each includes and the deadline for the current tier.
  3. The ticket form itself, inline, or a button that opens it.
  4. Agenda at a glance, even if it is only tracks and times.
  5. Speakers, with photos and companies.
  6. Venue, address, and a note on hotels or parking.
  7. What is included: meals, workshops, recordings, the dinner.
  8. FAQ: invoices, transfers, group rates, visa letters, dietary needs.
  9. A link to the refund policy and the group ticket contact.

Make the deadline line specific and verifiable: "Early bird ends 14 October, then $599." Our conference ticket tiers guide covers how to set those dates and prices. Measure its effect rather than treating it as the highest-performing element by default.

Put the group option on the page as well as in relevant emails so buyers can see it before choosing quantity. Track group-order take-up; this site has no dataset showing that a visible "Team of 5" line converts solo buyers or is the highest-value page change.

From our publisher · Checkout Page

Put your ticket form on your own site

Embed inline or as a popup on WordPress, Webflow, Framer, Squarespace or Wix. Free up to $3,000 a month in sales.

Try Checkout Page →

How much do speed and mobile layout matter?

Mobile layout and load time are requirements to test, not reasons to predict an individual buyer's behavior. Check the published page on real phones: the ticket price, form, quantity controls and payment step should be readable and operable without horizontal scrolling or pinch-zooming.

Start with three checks. Open the tickets page on a real phone, not only a browser resize. Confirm the current price is easy to find. Confirm the ticket form and quantity control work without horizontal scrolling or pinch-zoom.

Measure the published page before diagnosing load time. Large video, unoptimized images and third-party scripts are candidates to inspect; compress media, defer noncritical content where appropriate and retest after each change.

Wallet payments can reduce the amount of card data a buyer must type on a compatible device. Availability and the exact flow depend on the browser, device, buyer and Stripe configuration, so test the payment methods important to your audience.

Why keep one canonical tickets URL?

Use a single tickets page for every campaign and carry the campaign identity in UTM parameters. Separate pages per channel split your search signals, scatter your analytics and create the classic failure where an old link from a sponsor deck points at a page with last year's prices.

Pick the URL before you announce anything: yourconference.com/tickets is fine. Every email, ad, sponsor deck, speaker post and QR code points there. When tiers change, you change one page, and every link ever published stays correct.

If you must run a special landing page for one audience, for example a partner rate, have it end in a button to the canonical tickets page rather than a second checkout. One checkout, many doors.

Keep last year's URL alive too. Redirect it to the current tickets page rather than deleting it, because the links in old newsletters and Slack messages are still being clicked.

How do you test checkout before you launch?

Buy a ticket yourself on a phone with a real payment method, then refund it. An end-to-end test can expose confirmation-email, required-field, payment and mobile-embed problems that an editor preview cannot. Allow enough time to correct and retest before announcing sales.
  1. Create a test ticket type at $1, or a free one, and set its capacity to a small number so it cannot run away from you.
  2. Open your published tickets page on a phone using mobile data, not office wifi.
  3. Buy the test ticket with a real card, filling in the registration fields exactly as an attendee would.
  4. Check the confirmation email arrives, that the QR ticket PDF is attached, and that the sender name and reply-to address are yours.
  5. Scan the QR code with your check-in scanner to confirm it validates, then check the attendee shows as checked in.
  6. Apply a coupon code to a second test order and confirm the discount and the final amount are what you expect.
  7. Export the attendees to CSV and confirm every registration answer came through in a usable column.
  8. Refund both orders from the dashboard, then hide or delete the test ticket type before you announce.

Repeat the test after any material change and again before the event. Edits to prices, tiers, dates and embedded code can introduce regressions even when the original setup passed.

If your fees, plan and per-ticket costs are still undecided, work through conference ticketing fees first, because the pricing model changes what you put on the page. A platform charging the buyer a fee at the last step needs that number disclosed next to the price.

Frequently asked questions

Do I need a developer to sell tickets on my website?
Often not. A hosted-page button needs only a link, and supported builder plans provide an embed or code element for inline and popup options. A developer may still be needed for a restricted theme, content-security policy, custom analytics or a builder plan that limits custom code. Test the published page rather than only the editor preview.
Should tickets open in a popup or sit inline on the page?
Inline for a dedicated tickets page, popup for a Buy tickets button in your header or on the homepage. Inline means the buyer never has to click twice. A popup keeps a marketing page focused while still selling from it.
Can I sell tickets on my website without a marketplace listing?
Yes, if you have another acquisition route such as a permissioned list, speakers, sponsors, partners or paid campaigns. A marketplace may still contribute discovery. Check referral and completed-order data before removing it, and compare the value of referred registrations with marketplace fees and brand trade-offs.
How do I test ticket checkout before I launch?
Create a hidden $1 ticket type or a free one, buy it yourself on a phone, check the confirmation email and QR ticket arrive, scan the QR with your check-in app, then refund the order. Repeat once with a coupon code applied. Then delete or hide the test type.
Which URL should I use in ads, emails and social posts?
One canonical tickets URL for everything, with campaign identity carried in UTM parameters rather than in different page paths. Multiple ticket pages split your analytics, your SEO signals and your ability to tell which channel actually sold seats.

Published by

Checkout Page

Checkout Page builds checkout and event ticketing software. This site covers conference registration through product documentation, fee calculations and practical planning examples.

Published by Checkout Page, one of the platforms covered. Comparisons use public pricing and documentation. Our editorial approach.