AUDIENCE: Administrators, Marketing Users, Graphic Designers, IT Team
- Learn how to suppress Act-On cookie logging within forms
- Identify areas where the form will behave as normal
- Learn about scenarios where the Act-On cookie should not be logged in a form
There are a few instances where the Act-On cookie should not be logged. For example, if you publish an internal form allowing internal employees to submit referrals, cookies should not be logged. Suppressing the cookie will ensure that the submitting employee is not shown as a known prospect in your Website Prospector report. Although the cookie is not logged in this example, the form signups can still be used as a Marketing list for nurturing purposes.
Below are the steps to prevent the Act-On cookie from being logged after a form submission:
- Create the Act-On form under Content > Forms.
- If the form is already created, hover over the desired form and choose Edit
- Insert a Hidden field in the form using _suppressLogging as the Data Field Name.
- Enter a value of '1' in the Data Field Value field.
- Click Submit, and save the form.
The form will behave as usual in the following areas:
- The signup data will continue to write to the Signup list
- The normal response display (per Step 2 - Settings of the form) will continue to occur after submission
- Confirmation email messages will continue to be sent if they are enabled
- Data will continue to push to the CRM if enabled
- Form views will continue to be tracked in the form report
If the '_suppressLogging' feature is enabled, the Act-On form will NOT:
- Show form submissions in the form report,
- Cookie the form submitter
- Log the form submission in the contact's Act-On activity history
If you would like to continue to apply a behavior score to these activities, use the Custom Events feature to upload the Signup list and associate a behavior score. See the article Creating and Scoring Custom Events for further information.