Home Forums Event Espresso Premium Gather 2nd Attendee Info prior to payment in Registration Form

Gather 2nd Attendee Info prior to payment in Registration Form

Posted: July 6, 2020 at 3:47 pm


July 6, 2020 at 3:47 pm

We provide a retreat experience for couples and would like to have the registration work so that we can collect the information for both attendees prior to going to the payment screen, but cannot figure out how to do this?

Tried to do a bundled package, but it only collects data for the primary attendee. Guidance would be greatly appreciated.



  • Support Staff

July 6, 2020 at 5:13 pm

Hi there,

You need to select at least the ‘personal information’ group on additional registrants within this section on the event:


July 8, 2020 at 4:00 pm

Yes, so we did this; however, when EE sends out the email, only the primary registrant shows up in the attendee list.


  • Support Staff

July 9, 2020 at 4:38 am

Which email are you referring to? Registration Approved?

If you are unsure post the subject of the email and we can tell from that, or a screenshot.


July 9, 2020 at 11:18 am

Yes, the registration approved email.


  • Support Staff

July 10, 2020 at 5:05 am

That’s odd, can you link me to the event in question so I can add a test registration?

Also, are you using the ‘Primary Registrant’ or ‘Registrant’ context of the Registrant Approved message type?


July 10, 2020 at 11:11 am

Here’s the link:

I’ve set up a promo code “EETest” for you to use. It is only valid once.

I’m not sure I follow when you ask about using the ‘Primary Registrant’ or ‘Registrant’ context of the Registrant Approved message type? We are using the “Primary Registrant” message. Here’s a screenshot that I hope helps.

Screenshot of Primary Registrant email backend


  • Support Staff

July 13, 2020 at 8:35 am

Hi there,

Both of your events only allow for a single ticket at this time.

Within Event Espresso each ticket is a registration, so if you only allow 1 ticket you are only collecting one registrants details (the primary registrant).

Right now you have the ‘Personal Information’ group set up to collect data for the Groom and then a custom question group to collect the Brides information (and then others for additional information). So within EE there is only 1 registrant and then all of your custom questions are saved to that registrant.

If you want to split out registrants so that each is actually a registrant on the event within EE and show individually you’ll need to adjust your Personal Information group to be more generic (as it will be asked twice, right now it would ask or the Groom’s details twice because you’ve set the group name etc to be related to the Groom) and allow for 2 tickets (you can keep them as a bundle but you need to select 2 tickets).

OR, if you simply want the emails to show the Brides details along with the Groom’s in the email, that is also possible but note that this limits some things you can do within Event Espresso a you are basically using 1 registrant as 2. For example, your sold counts will be per couple rather than per person and anywhere Event Espresso would split registrants you will only have 1.

The former option would be the recommended setup for Event Espresso but if you let me know which you prefer to use I can let you know what you need to change.


July 14, 2020 at 10:08 am

We would prefer the latter. We want our sold totals to be per couple, not per individual – as couples are required to attend together.


  • Support Staff

July 15, 2020 at 5:52 am

I’m not sure I follow when you ask about using the ‘Primary Registrant’ or ‘Registrant’ context of the Registrant Approved message type? We are using the “Primary Registrant” message. Here’s a screenshot that I hope helps.

Each message type has multiple ‘contexts’ and each of those messages has its own template which you can edit.

A quick example with the ‘Registration Approved’ message type is the message you send to the Event Admin most likely has different information than what you include to the Registrant (or Primary Registrant). Both are still a ‘Registration Approved’ message, just used in a different context.

This is important as you can edit each template individually and users often edit the wrong template, test their changes and find nothing changed and assume it’s broken, we also need to know which you are using to know where to add the additional details.

So, in Event Espresso -> Messages -> Default Messages Templates (assuming you aren’t using custom templates?)

Find the ‘Registration Approved’ message type and by default, it’ll show like this:

The ‘Primary Registrant’ context is disabled by default (which is why it is grey) but based on your comments and screenshot you are editing the primary registrant context, so click that.

The toggle switch at the top of that page is green and you have something like [PRIMARY_REGISTRANT_EMAIL] in the ‘To’ field, correct?

(The primary registrant is also a ‘registrant’ so in your setup you only want one of those 2 contexts enabled, otherwise they will receive both).

In your ‘ATTENDEE_LIST section, you can use the [ANSWER_*] shortcode to pull answers to specific question using the format [ANSWER_*{question_text}].

So below the </h4> tag, add something like:

<h4>[ANSWER_*Her First Name] [ANSWER_*Her Last Name]</h4>

That will pull the answers for the ‘Her First Name’ and ‘Her Last Name’ questions assigned to the current attendee in the loop (in your set up that is the Primary Registrant).


July 15, 2020 at 1:15 pm

Thank you! I will try this.


  • Support Staff

July 20, 2020 at 4:49 am

Hi there,

Just checking in to confirm if the above worked for you?

You must be logged in to reply to this support post. Sign In or Register for an Account

Support forum for Event Espresso 3 and Event Espresso 4.
Documentation for EE3 and EE4
Documentation for Event Espresso 3 Documentation for Event Espresso 4

Status: publish

Updated by  Tony 3 months, 1 week ago ago

Topic Tags


This topic is:
Do NOT follow this link or you will be banned from the site!
[gravityform id=80 title=false description=false ajax=false]
<div class='gf_browser_unknown gform_wrapper' id='gform_wrapper_80' ><form method='post' enctype='multipart/form-data' id='gform_80' action='/topic/gather-2nd-attendee-info-prior-to-payment-in-registration-form/'> <div class='gform_body'><ul id='gform_fields_80' class='gform_fields top_label form_sublabel_below description_below'><li id='field_80_1' class='gfield gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_80_1' >First name<span class='gfield_required'>*</span></label><div class='ginput_container ginput_container_text'><input name='input_1' id='input_80_1' type='text' value='' class='medium' aria-required="true" aria-invalid="false" /></div></li><li id='field_80_2' class='gfield gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_80_2' >Email address<span class='gfield_required'>*</span></label><div class='ginput_container ginput_container_email'> <input name='input_2' id='input_80_2' type='email' value='' class='medium' aria-required="true" aria-invalid="false" /> </div></li><li id='field_80_3' class='gfield gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' >GDPR Agreement<span class='gfield_required'>*</span></label><div class='ginput_container ginput_container_checkbox'><ul class='gfield_checkbox' id='input_80_3'><li class='gchoice_80_3_1'> <input name='input_3.1' type='checkbox' value='I consent to have this website store my submitted information so they can respond to my inquiry.' id='choice_80_3_1' /> <label for='choice_80_3_1' id='label_80_3_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_80_4' class='gfield gform_validation_container field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_80_4' >Phone</label><div class='ginput_container'><input name='input_4' id='input_80_4' type='text' value='' autocomplete='off'/></div><div class='gfield_description' id='gfield_description_80_4'>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_80' class='gform_button button' value='Download Now' onclick='if(window["gf_submitting_80"]){return false;} if( !jQuery("#gform_80")[0].checkValidity || jQuery("#gform_80")[0].checkValidity()){window["gf_submitting_80"]=true;} ' onkeypress='if( event.keyCode == 13 ){ if(window["gf_submitting_80"]){return false;} if( !jQuery("#gform_80")[0].checkValidity || jQuery("#gform_80")[0].checkValidity()){window["gf_submitting_80"]=true;} jQuery("#gform_80").trigger("submit",[true]); }' /> <input type='hidden' class='gform_hidden' name='is_submit_80' value='1' /> <input type='hidden' class='gform_hidden' name='gform_submit' value='80' /> <input type='hidden' class='gform_hidden' name='gform_unique_id' value='' /> <input type='hidden' class='gform_hidden' name='state_80' value='WyJbXSIsIjBiNjdjZjkyMDUzOWUxOWY5Y2NiZjIwMzM4YjA1Mjk4Il0=' /> <input type='hidden' class='gform_hidden' name='gform_target_page_number_80' id='gform_target_page_number_80' value='0' /> <input type='hidden' class='gform_hidden' name='gform_source_page_number_80' id='gform_source_page_number_80' 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 == 80) {} } );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', [80, 1]) } ); </script>