Private Label - Direct Registration
"Direct Registration" bypasses our standard registration and login forms.
Users log into your site, then click a link to go to the picks page for your private label sports pool site on our servers. They never see a registration form or login form on the private label site. They don't have to remember any password on the private label site.
You are in control of how many entries a player may have. Players can have unlimited entries, but your site controls that. Each entry must have a different screen name, but the same email address and password sent. See below for tech details on what information gets sent.
You will need to place a hidden HTML form on your site that "POSTs" key information to the private label site on our servers. The hidden HTML form should use hidden input tags, found in the sample below. The values of the hidden tags should be dynamically populated, by your site, based on the user that is logged in.
The user should not fill in any of the fields, since they are hidden. The user will only see a graphic, button or link that will act as a "submit" button, transferring them and POSTing their hidden data to the private label site. The private label site will register them and/or log them in, based on the hidden data.
Please do NOT send the user's actual password for your site.
Tech Details
iFrame
If the contest site is to be iframed within your site, then the contest site must use a "subdomain" of yours. This will require upgrading to our "gold template".
ie. If your site is https://www.yoursite.com, then the iframed contest site must be something like: https://contest.yoursite.com or https://bracket.yoursite.com .
The reason for this is due to ever-tightening browser security settings. Most popular browsers don't allow setting 3rd party cookies in iframes. Our sites require cookies to be set, in order for people to stay logged in.
Your IT team should be able to easily make this temporary DNS change to the subdomain. You will still own the domain and subdomain, you will just need to point the subdomain to our servers for the duration of the contest.
If the contest site is to be iframed within your site, then the contest site must use a "subdomain" of yours. This will require upgrading to our "gold template".
ie. If your site is https://www.yoursite.com, then the iframed contest site must be something like: https://contest.yoursite.com or https://bracket.yoursite.com .
The reason for this is due to ever-tightening browser security settings. Most popular browsers don't allow setting 3rd party cookies in iframes. Our sites require cookies to be set, in order for people to stay logged in.
Your IT team should be able to easily make this temporary DNS change to the subdomain. You will still own the domain and subdomain, you will just need to point the subdomain to our servers for the duration of the contest.
Posting to bracket site (outside of an iframe)
Due to increasingly tighter browser security settings, most popular browsers don't allow POSTing info to different domains. Unless, the user has previously visited the 3rd party domain. If your testing uncovers this issue, it may require a 2-step work-around process. The work-around process involves sending the user to a special page on the bracket site. The bracket site immediately returns the user to a "jump" page on your site, which then POSTs their unique info to the custom pool site. This process satisfies browser security policies, because they did go to the custom pool site prior to POSTing data to it.
Due to increasingly tighter browser security settings, most popular browsers don't allow POSTing info to different domains. Unless, the user has previously visited the 3rd party domain. If your testing uncovers this issue, it may require a 2-step work-around process. The work-around process involves sending the user to a special page on the bracket site. The bracket site immediately returns the user to a "jump" page on your site, which then POSTs their unique info to the custom pool site. This process satisfies browser security policies, because they did go to the custom pool site prior to POSTing data to it.
- Send the user to our "pre registration" page before POSTing their information to the private label site. Send users to "pre_registration.aspx?to=", but with a parameter in the querystring. The parameter should be the URL to your system, that you want them to return to. eg. https://yourplname.pooltracker.com/tourney/pre_registration.aspx?to=https://www.yourdomain.com/bracketpage/ ..where the value of the "to" parameter is set to your "bracket page" URL. The "pre_reg.." page will immediately send the user "to" that page. ie. https://bracketdemo.pooltracker.com/tourney/pre_registration.aspx?to=https://www.google.com Please note, you may need to URLEncode the URL in the "to" parameter.
- Your "bracket page", ie. https://www.yourdomain.com/bracketpage/ , should then POST the hidden information to "directregistration.aspx", per the samples.
A test page will be available, once the private label site is up: _testDirectRegistration.aspx
ie. https://yourplname.pooltracker.com/tourney/_testDirectRegistration.aspx
Sample hidden HTML form
We will send you the URL to your private label site, once it is online and ready.
SN: asxljw