Why You Don’t Want to Add Eventbrite to Your WordPress Site

image of stop sign

As an event organizer, there are a number of different ways you can manage event registrations and ticketing through your WordPress site. What you shouldn’t do, however, is add Eventbrite to WordPress.

Eventbrite is a hosted event ticketing platform. This means you can create an account, create events, and allow prospective attendees to view event details and purchase tickets from your event page. Eventbrite also gives you the option to embed checkout on your WordPress site.

The main problem with adding Eventbrite to WordPress is that it takes away from the user experience you’d otherwise be able to deliver if you were using an integrated event management plugin that is designed specifically for WordPress, like Event Espresso

In this article, we’ll step through some of the main reasons why you don’t want to add Eventbrite to WordPress and explain what you can do instead.

Why You Shouldn’t Add Eventbrite to WordPress

If you’re organizing one or two free events (i.e. you’re not selling tickets) throughout the year, Eventbrite might be the right option for you.

However, if you’re looking for a way to sell event tickets and manage multiple events then you shouldn’t add Eventbrite to WordPress. Here’s why:

Reason #1: Doesn’t Let You Deliver a Seamless, Consistent Brand Experience

As we mentioned earlier, the main problem you’ll face when you add Eventbrite to WordPress is that you won’t be able to deliver a seamless, consistent brand experience to prospective attendees.

This is because the Eventbrite checkout page won’t match the rest of your website. So, when attendees reach checkout, they will be directed offsite away from your website and have no way to get back. As you can imagine, this is bad for user experience as it can be confusing for users and lead to a high site bounce rate..

In addition to this, it’s worth mentioning that Eventbrite has removed the calendar widget. This means that you have to add each event manually.

Instead of settling for the poor user experience you get when you add Eventbrite to WordPress or messing around with custom CSS code, we recommend using an event registration and ticketing plugin, like Event Espresso, that’s designed for WordPress.

The key benefits of using Event Espresso are that you get a quick, seamless, and branded checkout experience out of the box – no need for messing around with code or hiring a developer. In addition to this, you can also leverage Event Espresso’s smart single page checkout, offer group registrations, and add an events calendar and waitlist to your event page.

Event Espresso Events Caledar

For example, if you’re organizing an art camp event, you could add it to an events calendar using Event Espresso to make it easy for attendees to view event details and register.

Reason #2: You’ll Face Higher Costs

For paid events, Eventbrite fees and charges are based on the price of the ticket. While it may certainly be affordable for organizing a couple of events throughout the year, it can quickly get expensive for organizations that host lots of events and would like to sell tickets for each one. 

So, another reason you shouldn’t add Eventbrite to WordPress is that you’ll be charged based on how many tickets you sell and the price of the tickets. Not to mention, you’ll be limiting how prospective attendees discover your events.

Instead, you should use an event ticketing solution with a simple pricing model. Event Espresso, for example, lets you create and sell multiple ticket types at no additional charge. In addition to this, you can sell tickets to multiple dates for the same event.

Reason #3: You Don’t Own the Data You Collect

From a data security standpoint, one of the major drawbacks of adding Eventbrite to WordPress is that Eventbrite will still own all of the data you collect. This includes customer names, email addresses, and (most importantly) billing details. This isn’t ideal for self-hosted WordPress site owners since it means you can’t be GDPR-compliant.

To remain compliant, you need to use a WordPress event registration and ticketing plugin that gives you complete control over your attendees’ data. We recommend using Event Espresso considering it’s GDPR-compliant out of the box. It lets you easily export and erase any personal data you collect from attendees.

Reason #4: You Get Limited Payment Options

When you add Eventbrite to WordPress, you get limited payment options. More specifically, you can collect payments via invoice or check. Eventbrite also lets you collect payments on-site using the Eventbrite Organizer mobile app. You can use it to accept cash or credit card payments.

In order to deliver a better user experience to attendees, you should aim to make it easy for them to purchase event tickets. One way to do this is by using an event registration and ticketing plugin that supports multiple payment gateways.

Event Espresso lets you accept payments via invoice, check, PayPal, and credit cards as well as on-site payments. The plugin comes with six payment gateways out of the box with the option to integrate up to 17 additional payment gateways using add-ons.

Reason #5: Reports and Analytics Will Be Available on Eventbrite

As an event organizer, you probably already know how important it is to have easy access to reports and analytics. When you add Eventbrite to WordPress, all of your event data will be stored in Eventbrite only. This means that you’ll have to log in to your Eventbrite account to view reports and analytics each time.

The problem with this is that you and your team members will end up using multiple tools (Eventbrite and WordPress in addition to any CRMs and project management tools you use). It also makes it more difficult to automate workflows and export data.

Instead, you should use an event registration and ticketing solution that handles reports and analytics on the same platform. Event Espresso offers built-in reporting and analytics capabilities. This makes it easy to run a report directly from the WordPress dashboard to see the income and revenue you’ve generated from an event.

Conclusion

Instead of working out a way to add Eventbrite to WordPress, it’s much easier (and more cost-effective) to use a WordPress event registration and ticketing plugin, like Event Espresso.

You won’t have to worry about managing attendees’ personal data and you’ll get access to more payment gateways. Plus, you’ll have access to reports and analytics directly through your WordPress site.

Be sure to check out our Eventbrite vs Event Espresso comparison for more information and the Event Espresso demo to see the plugin in action!

 

Related Articles

Share a Reply or Comment

Your email address will not be published. Required fields are marked *

Need help with Event Espresso? Create a support post in our support forums

Do NOT follow this link or you will be banned from the site!
[gravityform id=116 title=false description=false]
<div class='gf_browser_unknown gform_wrapper' id='gform_wrapper_116' ><form method='post' enctype='multipart/form-data' id='gform_116' action='/2020/08/why-you-dont-want-to-add-eventbrite-to-your-wordpress-site/'> <div class='gform_body'><ul id='gform_fields_116' class='gform_fields top_label form_sublabel_below description_below'><li id='field_116_5' class='gfield gfield_contains_required field_sublabel_hidden_label field_description_below gfield_visibility_visible' ><label class='gfield_label gfield_label_before_complex' >What is your first name?<span class='gfield_required'>*</span></label><div class='ginput_complex ginput_container no_prefix has_first_name no_middle_name no_last_name no_suffix gf_name_has_1 ginput_container_name' id='input_116_5'> <span id='input_116_5_3_container' class='name_first' > <input type='text' name='input_5.3' id='input_116_5_3' value='' aria-label='First name' aria-required="true" aria-invalid="false" placeholder='First name'/> <label for='input_116_5_3' class='hidden_sub_label screen-reader-text'>First name</label> </span> </div></li><li id='field_116_1' class='gfield gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_116_1' >What is your email address so we can follow up with you?<span class='gfield_required'>*</span></label><div class='ginput_container ginput_container_text'><input name='input_1' id='input_116_1' type='text' value='' class='medium' placeholder='hello@example.com' aria-required="true" aria-invalid="false" /></div></li><li id='field_116_2' class='gfield gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_116_2' >Tell us about your concerns below<span class='gfield_required'>*</span></label><div class='ginput_container ginput_container_textarea'><textarea name='input_2' id='input_116_2' class='textarea medium' placeholder='What kind of events are you planning?' aria-required="true" aria-invalid="false" rows='10' cols='50'></textarea></div></li><li id='field_116_6' class='gfield field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' >GDPR Agreement</label><div class='ginput_container ginput_container_checkbox'><ul class='gfield_checkbox' id='input_116_6'><li class='gchoice_116_6_1'> <input name='input_6.1' type='checkbox' value='I consent to have this website store my submitted information so they can respond to my inquiry.' id='choice_116_6_1' /> <label for='choice_116_6_1' id='label_116_6_1'>I consent to have this website store my submitted information so they can respond to my inquiry.</label> </li></ul></div></li><li id='field_116_3' class='gfield gform_hidden field_sublabel_below field_description_below gfield_visibility_visible' ><input name='input_3' id='input_116_3' type='hidden' class='gform_hidden' aria-invalid="false" value='' /></li><li id='field_116_4' class='gfield gform_hidden field_sublabel_below field_description_below gfield_visibility_visible' ><input name='input_4' id='input_116_4' type='hidden' class='gform_hidden' aria-invalid="false" value='https://eventespresso.com/2020/08/why-you-dont-want-to-add-eventbrite-to-your-wordpress-site/' /></li><li id='field_116_7' class='gfield gform_validation_container field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_116_7' >Name</label><div class='ginput_container'><input name='input_7' id='input_116_7' type='text' value='' autocomplete='off'/></div><div class='gfield_description' id='gfield_description__7'>This field is for validation purposes and should be left unchanged.</div></li> </ul></div> <div class='gform_footer top_label'> <input type='submit' id='gform_submit_button_116' class='gform_button button' value='Send my message' onclick='if(window["gf_submitting_116"]){return false;} if( !jQuery("#gform_116")[0].checkValidity || jQuery("#gform_116")[0].checkValidity()){window["gf_submitting_116"]=true;} ' onkeypress='if( event.keyCode == 13 ){ if(window["gf_submitting_116"]){return false;} if( !jQuery("#gform_116")[0].checkValidity || jQuery("#gform_116")[0].checkValidity()){window["gf_submitting_116"]=true;} jQuery("#gform_116").trigger("submit",[true]); }' /> <input type='hidden' class='gform_hidden' name='is_submit_116' value='1' /> <input type='hidden' class='gform_hidden' name='gform_submit' value='116' /> <input type='hidden' class='gform_hidden' name='gform_unique_id' value='' /> <input type='hidden' class='gform_hidden' name='state_116' value='WyJbXSIsIjBiNjdjZjkyMDUzOWUxOWY5Y2NiZjIwMzM4YjA1Mjk4Il0=' /> <input type='hidden' class='gform_hidden' name='gform_target_page_number_116' id='gform_target_page_number_116' value='0' /> <input type='hidden' class='gform_hidden' name='gform_source_page_number_116' id='gform_source_page_number_116' value='1' /> <input type='hidden' name='gform_field_values' value='' /> </div> </form> </div><script type='text/javascript'> jQuery(document).bind('gform_post_render', function(event, formId, currentPage){if(formId == 116) {if(typeof Placeholders != 'undefined'){ Placeholders.enable(); }} } );jQuery(document).bind('gform_post_conditional_logic', function(event, formId, fields, isInit){} );</script><script type='text/javascript'> jQuery(document).ready(function(){jQuery(document).trigger('gform_post_render', [116, 1]) } ); </script>