{"id":1948470,"date":"2020-11-23T08:09:15","date_gmt":"2020-11-23T13:09:15","guid":{"rendered":"https:\/\/staging.theeventscalendar.com\/knowledgebase\/?post_type=tribe-knowledgebase&p=1948470"},"modified":"2022-07-22T13:10:06","modified_gmt":"2022-07-22T17:10:06","slug":"enabling-attendee-information-for-tickets","status":"publish","type":"post","link":"https:\/\/staging.theeventscalendar.com\/knowledgebase\/enabling-attendee-information-for-tickets\/","title":{"rendered":"Enabling Attendee Information for Tickets"},"content":{"rendered":"\n

Individual Attendee Collection (IAC) is a feature in Event Tickets Plus<\/a> that allows enabling attendee information to be collected on each ticket when multiple tickets are purchased together. Without IAC, the tickets only enable attendee information about the individuals purchasing the tickets. IAC changes that by allowing information to be entered for each ticket on an individual basis.<\/p>\n\n\n\n

As such, you can reliably gather and record the name and email address of all attendees in a way that allows exporting, searching, sorting, and API access.<\/p>\n\n\n\n

Enabling individual attendee collection globally<\/h2>\n\n\n\n

The feature can be enabled in the plugin settings, located at Tickets \u2192 Settings \u2192 Attendee Registration<\/strong><\/p>\n\n\n\n

\"Collecting<\/figure>\n\n\n\n
  • Allow Individual Attendee Collection:<\/strong> IAC is enabled, but option for the person purchasing tickets.<\/li>
  • Require Individual Attendee Collection:<\/strong> IAC is enabled and the person purchasing tickets is required to provide information for each ticket before proceeding.<\/li>
  • No Individual Attendee Collection:<\/strong> IAC is disabled.<\/li><\/ul>\n\n\n\n

    Once saved, this is the default setting for all new tickets. You can still override the setting on a per-ticket basis in the WordPress editor.<\/p>\n\n\n\n

    \n

    \ud83d\udc4b Heads up!<\/strong> Individual Attendee Collection requires the updated ticket and\/or RSVP experience to be enabled on sites already running Event Tickets. You can enable the updated experience from Tickets<\/strong> \u2192<\/strong> Settings<\/strong> \u2192<\/strong> General \u2192 Display<\/strong>. For new installs (since version 5.0), this experience will be enabled automatically and you will not see these setting options.<\/p>\n\n\n\n

    \"\"<\/figure>\n<\/div><\/div>\n\n\n\n

    Enabling IAC in the WordPress editor<\/h2>\n\n\n\n

    No matter what IAC you set for the default in the plugin settings, you can still manage the IAC for individual tickets in the WordPress editor directly in the Ticket block. Add a Ticket block to the post, and select the “Attendee Collection” option to expand the IAC settings for that ticket.<\/p>\n\n\n\n

    \"Collecting
    The “Attendee Collection” option is located in the Ticket block.<\/figcaption><\/figure>\n\n\n\n

    <\/p>\n\n\n\n

    \"Collecting
    Once expanded, the “Attendee Collection” section offers the same three settings that we covered in the global settings. Note that the pre-selected option will match your global setting. So, for example, if your global setting is to “require” IAC, then the Ticket block setting will also “require” IAC by default.<\/figcaption><\/figure>\n\n\n\n

    Enabling attendee collection with a filter<\/h2>\n\n\n\n

    In addition to using the plugin settings, the default IAC setting can be programmatically set to any of the three possible settings with the following function:<\/p>\n\n\n

    \n<?php\n\nadd_filter( 'tribe_tickets_plus_attendee_registration_iac_default_setting_for_all_tickets', 'my_custom_iac_setting_for_all_tickets' );\n\n\/**\n * Filter the Individual Attendee Collection setting for all tickets.\n *\n * @param string $default_iac_setting The default IAC setting for all tickets (none, allowed, required).\n *\n * @return The default IAC setting for all tickets (none, allowed, required).\n *\/\nfunction my_custom_iac_setting_for_all_tickets( $default_iac_setting ) {\n  \/\/ Set the default as allowed.\n  return 'allowed';\n}\n<\/pre><\/div>\n\n\n
    Enabling attendee collection WordPress editor<\/h2>\n\n\n\n
    Even if IAC is disabled in your plugin settings, you can still use the feature by enabling it when creating a new ticket in the WordPress editor.<\/p>\n\n\n\n
    • Add a ticket block to the editor<\/li>
    • Create at least one ticket and save it by selecting “Create Ticket”<\/li>
    • Select the option to add attendee information<\/li><\/ul>\n\n\n\n
      <\/p>\n\n\n\n
      No Individual Attendee Collection<\/h3>\n\n\n\n
      This is the out-of-the-box default setting and is the only Attendee Collection setting available in Event Tickets Plus versions prior to 5.1.0.<\/p>\n\n\n\n
      This setting means that any Attendee (and ticket) generated will use the Billing Purchaser\u2019s name and email address. In the same breath, only the Billing Purchaser will receive an email containing all tickets purchased.<\/p>\n\n\n\n
      Allow Individual Attendee Collection<\/h3>\n\n\n\n
      We consider this as the middle-of-the-road compromise between No individual attendees<\/em> and Require individual attendees<\/em> ticket sale options. This setting also places control in your Purchaser\u2019s hands as they initially purchase each ticket, including if they choose to update their Attendee tickets post-purchase.<\/p>\n\n\n\n
      As folks select to purchase tickets to your upcoming event, the experience this setting provides includes: <\/p>\n\n\n\n
      • The option for your purchaser to either leave themselves (the Billing Purchaser) as the Attendee name and email address, or<\/li>
      • To add a different name and email address (other than themselves) to any given ticket.<\/li><\/ul>\n\n\n\n
        Post-purchase: the Billing Purchaser can log into your website, head to the Event page > My Tickets, and update (e.g. change) the ticketing information for a given Attendee.<\/p>\n\n\n\n
        The information used within tickets that have \u201cAllow Individual Attendees\u201d is that the same information is allowed to be reused for multiple tickets, and\/or default to the Billing Purchaser\u2019s name and email.  <\/p>\n\n\n\n
        Note:<\/strong> Any Attendee that the Billing Purchaser adds a unique (different) email address to, will receive their own individual ticket confirmation email and the Billing Purchaser will receive the standard ticket email confirmation, which contains all tickets purchased.<\/p>\n\n\n\n
        <\/p>\n\n\n\n
        Require Individual Attendee Collection<\/h3>\n\n\n\n
        There is a strong case in which \u201cRequiring\u201d Individual Attendee Collection for a ticket is beneficial for your upcoming event if enabling attendee information is important to you. By using this ticket sales option, the Billing Purchaser will be required to add a unique name and email address for each attendee. <\/p>\n\n\n\n
        For example: the ticket\u2019s Billing Purchaser selects 4 tickets to an upcoming event. Prior to completing their purchase, they must add a unique (different) name and email address for each of the 4 Attendees. None of the Attendees need to be the Billing Purchaser\u2019s information either. They can simply purchase the tickets on behalf of the Attendees. By doing so, each individual Attendee will each receive their own individual ticket confirmation email and the Billing Purchaser will receive the standard ticket email confirmation, which contains all tickets purchased. <\/p>\n\n\n\n
        As folks select to purchase tickets to your upcoming event, the experience this setting provides includes: <\/p>\n\n\n\n
        • The requirement for the Billing Purchaser to add a different name and email address (other than themselves) to every Attendee\u2019s ticket prior to completing their purchase.<\/li><\/ul>\n\n\n\n
          Post-purchase: the Billing Purchaser can log into your website, head to the Event page > My Tickets,<\/em> and update (e.g. change) the ticketing information for a given Attendee, however, it must be different from all other Attendees for that set of tickets purchased.<\/p>\n\n\n\n
          When modifying the name or email address on the My Tickets page for an attendee ticket with Individual Attendee Collection required, any email can be used even if the email address is used for another attendee already.<\/p>\n\n\n\n
          <\/p>\n\n\n\n
          Resending Tickets<\/h3>\n\n\n\n
          The Event Tickets Plus system keeps checking for when Billing Purchaser updates (e.g. changes) an Attendee\u2019s email address. When such an action takes place (post-purchase), a checkbox will appear allowing the user to select to resend the ticket email upon saving the new updated information. <\/p>\n\n\n\n
          Enabling attendee information with Individual Attendee Collection provides flexibility in the way your Event Attendees are generated. <\/p>\n\n\n\n
          As the default, only the Billing Purchaser is listed as the Attendee to an event. If they purchase multiple tickets, their name and email address will be listed as the Attendee. <\/p>\n\n\n\n
          Individual Attendee Collection provides you with two additional ticket sales options: <\/p>\n\n\n\n
          • \u201cAllow\u201d Individual Attendee Collection<\/li>
          • \u201cRequire\u201d Individual Attendee Collection<\/li><\/ul>\n\n\n\n
            The goal of the Individual Attendee Collection project is to adjust the system so that you can reliably gather and record the name and email address of all attendees in a way that allows exporting, searching, sorting, and API access.<\/p>\n\n\n\n
            Note:<\/strong> You can enhance your ticket sales by using both Individual Attendee Collection and custom Attendee Registration Information fields. Let Individual Attendee Collection collect and organize your Attendees and use the power of Attendee Registration Information to gather even more custom information!<\/p>\n","protected":false},"excerpt":{"rendered":"
            Individual Attendee Collection (IAC) is a feature in Event Tickets Plus that allows enabling attendee information to be collected on each ticket when multiple tickets are purchased together. Without IAC, the tickets only enable attendee information about the individuals purchasing the tickets. IAC changes that by allowing information to be entered for each ticket on…<\/p>\n","protected":false},"author":19,"featured_media":1955565,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_kad_blocks_custom_css":"","_kad_blocks_head_custom_js":"","_kad_blocks_body_custom_js":"","_kad_blocks_footer_custom_js":"","_swpsp_post_exclude":false,"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"ep_exclude_from_search":false,"footnotes":""},"categories":[1],"tags":[],"stellar-product-taxonomy":[],"class_list":["post-1948470","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"acf":[],"taxonomy_info":{"category":[{"value":1,"label":"Uncategorized"}]},"featured_image_src_large":["https:\/\/images.theeventscalendar.com\/kb\/uploads\/2023\/02\/social-share-1024x538.png",1024,538,true],"author_info":{"display_name":"Erica Eide","author_link":"https:\/\/staging.theeventscalendar.com\/knowledgebase\/author\/ericaeide\/"},"comment_info":0,"category_info":[{"term_id":1,"name":"Uncategorized","slug":"uncategorized","term_group":0,"term_taxonomy_id":1,"taxonomy":"category","description":"","parent":0,"count":139,"filter":"raw","term_order":"0","cat_ID":1,"category_count":139,"category_description":"","cat_name":"Uncategorized","category_nicename":"uncategorized","category_parent":0}],"tag_info":false,"_links":{"self":[{"href":"https:\/\/staging.theeventscalendar.com\/knowledgebase\/wp-json\/wp\/v2\/posts\/1948470","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/staging.theeventscalendar.com\/knowledgebase\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/staging.theeventscalendar.com\/knowledgebase\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/staging.theeventscalendar.com\/knowledgebase\/wp-json\/wp\/v2\/users\/19"}],"replies":[{"embeddable":true,"href":"https:\/\/staging.theeventscalendar.com\/knowledgebase\/wp-json\/wp\/v2\/comments?post=1948470"}],"version-history":[{"count":1,"href":"https:\/\/staging.theeventscalendar.com\/knowledgebase\/wp-json\/wp\/v2\/posts\/1948470\/revisions"}],"predecessor-version":[{"id":1955981,"href":"https:\/\/staging.theeventscalendar.com\/knowledgebase\/wp-json\/wp\/v2\/posts\/1948470\/revisions\/1955981"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/staging.theeventscalendar.com\/knowledgebase\/wp-json\/wp\/v2\/media\/1955565"}],"wp:attachment":[{"href":"https:\/\/staging.theeventscalendar.com\/knowledgebase\/wp-json\/wp\/v2\/media?parent=1948470"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/staging.theeventscalendar.com\/knowledgebase\/wp-json\/wp\/v2\/categories?post=1948470"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/staging.theeventscalendar.com\/knowledgebase\/wp-json\/wp\/v2\/tags?post=1948470"},{"taxonomy":"stellar-product-taxonomy","embeddable":true,"href":"https:\/\/staging.theeventscalendar.com\/knowledgebase\/wp-json\/wp\/v2\/stellar-product-taxonomy?post=1948470"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}