Registration process questine
- Started
- Last post
- 9 Responses
- BusterBoy
OK...bit of an odd one here.
I'm doing a project with my brother...we're sending out some information to about 200 small to medium sized businesses in a particular industry. We need these companies to register to become involved.
Tricky thing is we don't want any Joe Blow to be able to register if they visit the website. The site is basically just a landing page with a button you can click to go to the register page.
I'm a bit conflicted about the best way to do this.
1. Let anyone have the ability to register. We only want people in this particular industry to register...nobody else. So if anyone else does, their registration will be null and void.
2. Provide the businesses a username/password so they need to login before they can register.
3. Send them a secret URLAnd if I send them a secret URL, what format is better:
http://register.thecompany.com
www.thecompany.com/registerAny thoughts appreciated...hope I've explained this in a semi-coherent way.
- monNom0
How likely is it that some random person visits the website and signs up for more information, while also not being in your target audience? Pretty slim I think.
If you just don't put the link to the register form in the website navigation, that's probably enough security. And that one guy who deviously finds his way in is probably a good lead anyway!
- dbloc-2
password protect it. wend out the code/password
- sted-1
email, card with only the code for zynga:
'thecompany.com / #C-ZnVja21'
simple redirect matching the '#C-' part in the url to run a check on the active keys, if it's an active key delete the key and ask for an email address to send out some activation + to be able to ask actually for details or whatever u do.
- monNom-2
if you really want to, you can give each user your email a unique one-time code.
ie:
user: Jane Doe
email:
uid: 35f5782642e9fa0f6cfff5a552e2ae97
(that's an md5 hash of the email)then on the link you put
http://www.ourcompany.co/registe…
and when your user submits the form, you take that url parameter uid and match it against your contact database.
- oh well. jane(at)doe.com, and you'll need to hover to see that link.monNom
- dbloc-2
you can also send out an access code and make that a field in the registration as required.
- BusterBoy-2
I was thinking the easiest way, keeping in mind we'll be targetting some luddites may be just to have a subdomain...ie
http://register.thecompany.com
Makes them feel slightly exclusive. Fairly easy to navigate to.
Thoughts?
- ben_-1
We had a problem like this recently with a client.
Opted for a landing page that had a really brief summary of the benefit to the person signing up, then what the program would be asking of them.
Users were invited to "submit" their company to the program which allowed the client to simply curate who could be involved and send a really nice form letter to the ones who weren't chosen this time around.
Seems to be working well so far.