Hi there,
Is there any way to disable some of the fields on the /account/register.aspx page? I want registering online to be as low-barrier as possible because we just made the switch to WordFly, and this is how people will sign up for our newsletter. Previously, we were using MailChimp, which wasn't connected to Tessitura, so lists could exist independently from Tess.
Now, we want people to sign up for the newsletter by registering (so we capture them as a constituent in Tess), but I don't necessarily need their home address , phone number, prefix, middle name, etc.
Without using jQuery/JS can I remove some of these fields within the system tables?
Thank you, any help is appreciated.
Going to play devil's advocate here. I don't think using Short Registration is a good way of signing up people for an email list. I would much rather prefer Wordfly hold onto this information until the user is planning to purchase.
Here's my rundown on ShortReg:
A) It creates a constituent in Tessitura without any meaningful information other than email and possibly a password.
B) It creates a login to said constituent, which can be troublesome since logins are unique and this may fail if the user is in the system and has opted out already, especially if they want to opt back in.
C)Users on the email list may be unaware they have a login as they have only signed up for an email list. One of the most prominent marketing tactics and checkout flows becomes complicated, lost sales and duplicate accounts abound.
D)Tessitura isn't an ESP, it's a CRM, and as such it doesn't handle email specifically well. ESPs treat a single email address as a registered endpoint, a user. Conversely Tessitura can associate multiple user accounts with the same email address as it is just storing contact information. The user account is not guaranteed to be unique to the email.
I know these views may seem a bit unfavorable but it has been my experience that using ShortReg when there is no intent to purchase can cause some serious confusion for patrons; especially with the way Tessitura handles Emails/Logins/Constituents compared to the rest of the Web.
Thank you for posting this Christopher, I actually agree and will use your much more eloquent way of explaining the pitfalls of email-only records in Tessitura than I have managed so far!