Hi everyone,
I'm working through a challenge with our Marketo event registration forms and would appreciate some guidance.
Our business partners want the ability to register clients on their behalf and/or the ability for registrants to add guests, then later pull a full registration list with all registrants.
We’ve run into an issue where a partner enters their own email address but fills out the guest’s name and phone number, causing the form submission to update their existing record instead of creating a new one for the guest.
Here’s an example of what our form would potentially look like:
--
First Name:
Last Name:
Phone Number:
Email:
+ Add Guests
Guest First Name:
Guest Last Name:
Guest Phone Number:
Guest Email Address:
+ Add Another Guest
--
Currently, I pull registration lists using a Smart List > Filled Out Form filter, but this approach wouldn't capture guest details accurately because the guest fields aren't the primary email address field within the Marketo form.
Does anyone have advice on how to correctly capture guest registrations while ensuring the master registration list remains accurate? Any best practices or alternative solutions would be greatly appreciated!
Thanks in advance!
This is the standard Referral Form pattern. Search my past posts for links to examples.
Perfect, thank you!
I have found several posts that cover this topic, but not finding very good examples of how to set this up. Here's a post I'm looking through right now:
Solved: Re: When a customer fills out a referral form, is ... - Marketing Nation
And you left a comment that says:
@SanfordWhiteman wrote:You don't need a multi-part form per se. It can all be one form: you post each of the referrals when they click submit (loop over the form data and submit again).
I've built forms where someone can refer unlimited people at a time (hitting an "add more" button to add additional referral sections). It's easy once you understand the order of operations.
I'm particularly interested in the information in bold.
Also: Wouldn't there be issues with adding contacts to our database who haven't specifically opted in? That's a concern of mine.
My brain is breaking trying to understand and comprehend how to implement this.
Here's an example of a Referral Form that supports multiple emails in a single field (technically, all input[type=email] can support multiple). This can easily be refactored to have multiple email fields: MktoForms2 :: Referral v2.1.2 (supports multiple referrals)
As for the question about opt-in, that's common to all referral scenarios. You can filter the referred emails so they have to be at the referrer's domain (where applicable). But you can't escape the fact that yes, you are inviting people to fill out a form for someone else.
This is fabulous information, thank you! I'll revisit this thread on Monday with a fresh perspective.