Page Scan

Feature Snapshot

Summary:
TrustedForm Page Scan is a feature that examines the static HTML content captured in a TrustedForm certificate to verify that specific text snippets—both required and forbidden—are present or absent, ensuring compliance and improving lead quality.

Key Benefits:

• Filters out leads that include undesired or deceptive language.
• Provides detailed scan outcomes to support automated lead filtering and manual review.

Typical Use Cases:

• Validating that web pages display accurate and expected advertisements.
• Rejecting leads when forbidden phrases indicating potential fraud or incentivization are detected.

How the TrustedForm Page Scan works

TrustedForm Page Scan operates by analyzing the static snapshot of a webpage stored within a TrustedForm certificate. When a lead is generated, the certificate captures the page’s HTML and visible text. Users supply text snippets categorized as “required” (which must appear) or “forbidden” (which should not appear). The scan is case insensitive regarding letters and ignores extra whitespace, but exact punctuation and spacing must match. The API response provides a comprehensive result which can be used to automatically accept, reject, or flag leads.

Step‑by‑Step Instructions

1. Configure Scan Parameters:
   In your TrustedForm API request or integration settings (e.g., via LeadConduit), specify the text snippets you wish to scan for by categorizing them as “required” or “forbidden.”

2. Review Scan Outcome:
   Examine the API response or integration result to assess if the page content used to generate a lead meets your criteria.

3. Apply Filtering or Flagging:
   Use the scan outcomes to automatically filter out leads that do not meet your requirements or to flag leads for further manual review.

Expected Result:
The API response will include which forbidden/required scans were found

Validation & Monitoring (optional)

• Test the Setup: Submit a test lead from a webpage designed with and without the specified text snippets, then verify that the scan outcome in the certificate or integration dashboard accurately reflects the presence or absence of each snippet.
• Where to Monitor?: Review the scan-related fields in the API response or integration logs.

Best Practices

• Maintain a centralized document listing all required and forbidden text snippets to avoid typos and ensure consistency.
• Ensure that the text specified exactly matches the page content—including punctuation and spacing—since even minor discrepancies can cause a scan failure.
• Configure separate filters or rules for required versus forbidden text to simplify troubleshooting and decision-making.
• Spot check the session replays from certifciate which fail to meet any rules established. Contact your partner about any corrective actions necessary.

Troubleshooting

Frequently Asked Questions (FAQ)

Q: What is TrustedForm Page Scan?
A: It is a feature that scans the static HTML content stored in a TrustedForm certificate for specific text snippets.

Q: Is the scan case sensitive?
A: No, the scan ignores differences in letter casing and extra whitespace, but it requires exact matches for punctuation and spacing.

Q: How can I use the scan outcomes?
A: The detailed scan results allow you to automatically filter, accept, or reject leads based on whether the page contains all required text and excludes forbidden content.

Q: Does TrustedForm page scanning impact the speed of the API response?
A: Yes, TrustedForm page scanning does add some time to the API response because it must load and search your webpage, which is a resource-intensive process. On average this adds 100–200ms, but it can vary based on the size of your site and the number of terms scanned.

Q: Does page scan work for TrustedForm Facebook Lead Ads certificates?
A: Yes. However, for TrustedForm Facebook Lead Ads certificates, page scan only supports scanning the custom disclaimer text and checkbox questions. It does not scan or search for text across the entire page, only within these supported areas.

Glossary