Note that in the above example, we’re using the Infusionsoft “Password” field. If you’re using a custom field for a password, you will need to change this to map to your custom field. Custom fields start with an underscore (_).

Shortcode Parameters

autologin: Set to yes to autologin the user after successful registration. Defaults to no.

date_fields: A comma separated list of the fields used to store date information, so that Memberium can convert these fields to the date/time format that Infusionsoft needs. Optional, only required if you’re using date fields.

failure_url: The URL to redirect to if the signup fails. Optional. Defaults to the current page.

form_id: The CSS ID to use for the form. Optional. Defaults to a system generated CSS value.

goal: The Campaign Builder API goal to trigger if the signup is successful. There is no failure goal since a failure does not create a new contact.

pass_fields: Whether to pass the form fields to the next page. By default this is disabled. Set this to a non-zero value to enable this feature. By default, the password is not passed to the next page.

pass_password: Whether to include the password in the fields passed to the next page. By default this is false. Set this to a non-zero value to enable this feature. If pass_fields is not enabled, then this setting has no effect.

required_fields: A comma separated list of fields that must be populated in order to complete processing the form. This is a server side check, and does not replace any JavaScript or HTML form validity checks you may wish to use.

success_url: The URL to redirect to if the signup is successful. Optional. Defaults to the current page.

tagids: A comma separated list of tags to apply if the signup is successful.

Description

This shortcode provides a safe and secure way to enable new user signups and allow them to choose their own passwords, without using Infusionsoft web forms.

The risk with using Infusionsoft webforms and allowing users to choose their own password, is that a dishonest user (attacker) can use someone else’s email to signup, supplying a new password in the process and take over the account. This shortcode neatly solves this problem.

Flexible Form Design
Memberium generates the form tags themselves, but the input tags, buttons and styling are all yours. You can use either an automatically generated CSS ID, or specify your own for complete control.

Special Field Handling
Memberium will scan the submitted form to see if a password has been supplied in the password field you have specified in your configuration, if no password was supplied, then a password will be automatically generated for the new user.

You can specify a comma separated list of required fields that must be populated in order to complete processing the form. This is a server side check, and does not replace any JavaScript or HTML form validity checks you may wish to use.

You can create input fields that are used for input confirmation by using adding “_confirmation” to the field name. For example, if you wanted the user to enter their password twice to confirm they entered it properly, you would use two field names: “Password”, and “Password_confirmation”. Memberium will test the fields on the server to ensure they verify before completing the signup. Note that Memberium does not automatically add code to verify that the fields match in the browser. Field names are case sensitive.

You can now reliably request date information, and have that data optionally converted into Infusionsoft’s internal format. You may wish to collect the user’s birthday or some other date, you can now reliably store this information.

Pass Fields to Next Page
You can optionally pass the value of the fields to the next page so that you can incorporate these fields into other scripts. If you choose to pass the fields, you can also optionally choose whether or not you pass the password field. Because “_confirmation” fields are redundant, they are not passed to the next page.

Failure and Success URL’s
You can specify URL’s to redirect to after the form is completed. URL’s for both success, and failure can be set. By default the form will stay on the same page.

Campaign Builder Integration
Once your new user successfully registers, you’ll want to start your automation processes on the backend. You can specify tags or Campaign Builder Goals to be applied when the form successfully completed. If you need to set multiple tags, it is possible to do it in the form, however it is much more efficient to use a Campaign Builder API goal, or a tag goal, and process your various new user setup tasks there. Generally we recommend API Goals over Tag Goals for reliability.

There are no goals or actions for a failed signup, since it does not create a contact record.

Web Form Ninja Tips and tricks

You can tell HTML to require a field by adding the required attribute to your input tag.

PHP

1

<input name="Password"required="required"type="password"/>

You can tell HTML to require a valid looking email address by changing the type to “Email” in your tag.

PHP

1

<input name="Email"required="required"type="email"/>

If you’d like help with your form, contact us at Support and please provide a copy of the form code you’re trying to use.

Shortcode Attributes

Conditional: No (?)Nestable: No (?)Accepts formatting: Yes* (?)Capturable: No (?)