Reduce SPAM Registrations
To reduce the amount of SPAM that reaches your Lasso database through your project website contact form (registration page), submissions should first be validated before being passed through. To validate a submission on the form, a reCAPTCHA or HoneyPot must be implemented. The lead can then be submitted to Lasso.
1 - Ensure that the Lasso UID, Client ID, and Project ID are not on the registration form
The Lasso UID, Client ID, and Project ID should not be on the registration form nor in its source code. It is important that these IDs cannot be viewed by the public as they can be used to bypass the form and submit SPAM registrations. The Lasso UID is your API key for submitting leads to Lasso.
2 - Add a reCAPTCHA or Honeypot
3 - (optional): Submitting to Lasso via cURL
Once a submission to your form has been validated by reCAPTCHA or a HoneyPot, it can be transferred to Lasso. Please refer to Registering via cURL using PHP for instructions on how to add your private IDS and submit leads to Lasso. If you would like to construct your own submission, please view an example of the required format here. Then refer to the NOT using PHP section for instructions on how to submit.
Important Note: The Lasso UID is the API key that allows submissions to Lasso. It should not be on the form nor in its code. The reCAPTCHA will stop bots from entering submissions using the form but if the key is taken, submissions can be made without a form.
If your registration page(s) have been compromised by a SPAM bot, resulting in SPAM leads being submitted to your project database, Lasso recommends replacing the Lasso UID on your registration page(s). Prior to replacing the Lasso UID, ensure that you have implemented a reCAPTCHA code and hidden your Lasso UID, Client ID, and Project ID.