Page Scanning

TrustedForm can perform a real-time scan of the form  to verify required verbiage is found and / or disallowed verbiage is not found on the page. The page scan happens on page load / when TrustedForm is instantiated and provides a simple and automatic test that disclosure language is present on the page.


Page Scan using the TrustedForm API

The required and/or forbidden text are passed to the TrustedForm API during the claim step as field parameters.

Required Text : scan=puppies
Forbidden Text : scan!=free

See the TrustedForm Claim API documentation for more details.


Page Scan using LeadConduit

You set required or forbidden text in the TrustedForm claim step in LeadConduit.

Open up your flow in edit mode, scroll down to the TrustedForm step, and click the Edit Field Mappings button

From there you can add new field mapping settings and define what you want to require or forbid.

In the example screenshot below, the required text is puppies and the forbidden text is free.

Please NOTE : Required and Forbidden text ignores casing and whitespace, but the text must otherwise be an EXACT MATCH.

Scenario : You configure the required text "Brontosaurus FOREVER" and the page has "Brontosaurus     forever"

Outcome : PASSES the required text audit.


Scenario : You require the text "I love puppies!" and the page instead has "I, love PUPPIES."

Outcome : FAILS the required text audit because 1) the comma in the text and 2) the period instead of exclamation point at the end of the text. 




Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


You must be logged in to comment.