Page Scan

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. As a best practice, when implementing Page Scanning we highly recommend using a single document containing the required language. When configuring webpages and TrustedForm Page Scan, all configuration should come from this document and should be copied and pasted.


NOTE TrustedForm for Facebook Lead Ads only supports page scanning for custom disclaimer text and checkbox questions.


Page Scan using the TrustedForm API

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

Required Text: scan[]=puppies&scan[]=kittens
Forbidden Text: scan!=free

See the TrustedForm Claim API documentation for more details.

Page Scan using LeadConduit

You can set required and/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 or kittens and the forbidden text is free.

Did You Know? You can pass multiple values to either the required or forbidden text!

This is useful when a lead vendor has multiple variants of Opt-In language and you want to make sure at least one of those exist on the page. In the following example, one might require either puppies or kittens to be present on the page.


Creating a Filter for the Page Scan outcome is a bit tricky. Assuming you want to fail a lead when none of the Required Text is found, the filter must check for both:

  1. A null value for TrustedForm Scans Found
  2. At least one value for TrustedForm Scans Not Found

That filter looks like this:


NOTE Required and Forbidden text ignores casing and multiple whitespaces, 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 configure the required text "Brontosaurus FOREVER" and the page has "Brontosaurusforever"

Outcome: FAILS the required text audit because:

  1. There is a required white space between Brontosaurus and FOREVER


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 the 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.