Feature Snapshot
Summary:
TrustedForm Verify 1:1 Consent Check is a feature within the TrustedForm Verify offering that programmatically confirms whether a certificate was able to clearly document a consumer providing consent in a one‑to‑one manner to be contacted by a specific company.
Key Benefits:
- Confirms compliance with regulations that require one-to-one consent (e.g. CMS) by verifying consumer consent on an individual basis.
- Reduces legal risk by identifying leads that have not provided explicit one‑to‑one consent.
- Automates verification steps, saving time and minimizing manual review efforts.
Typical Use Cases:
- Pre‑qualifying leads before initiating any regulated communications.
- Integrating with CRM or lead management systems to automatically flag or reject non‑compliant leads.
How the TrustedForm Verify 1:1 Consent Check works
When a consumer submits a web form that uses the TrustedForm Certify Web SDK and includes the required TrustedForm Consent Tags, an automated process can determine whether consent was granted to a single entity at a time. By making an API request and using the Verify operation the response returns the value of “one_to_one”:
• true – Explicit one‑to‑one consent was provided.
• false – Consent was not provided in a one‑to‑one manner.
• null – The check could not be performed because the required consent tags were missing or the lead source (e.g., Meta Lead Ads) does not support this feature.
Step‑by‑Step Instructions
-
Request Vendor Implementation:
Ask your lead vendors to implement TrustedForm Certify on their web forms and properly add the required TrustedForm Consent Tags per the provided guidelines. -
Enable the Consent Check:
Log in to your TrustedForm account, navigate to your Verification Criteria page, and enable the 1:1 Consent Check by entering your company’s legal name as it appears in the consent statement. -
Integrate the Verify API:
Configure your system or lead distribution platform to call the Verify API for each incoming TrustedForm certificate. -
Review the API Response:
Examine the response for the “one_to_one” property:
• A value of true means the consumer provided explicit one‑to‑one consent.
• A value of false indicates consent was not given.
• A value of null suggests that the check was not performed due to missing tags or unsupported lead source.
Expected Result:
Your system receives a clear API response indicating whether one‑to‑one consent was granted (true), denied (false), or indeterminate (null), enabling automated decision-making for lead processing.
Validation & Monitoring (optional)
-
Test the Setup:
Submit a test lead via a TrustedForm‑enabled web form that includes properly tagged consent language. Then, make a Verify API call and confirm that the “one_to_one” property returns the expected value (typically true when explicit consent is provided). -
Where to Monitor?:
Monitor your API logs or CRM integration logs for the “one_to_one” property and associated compliance alerts.
Best Practices
- Ensure all lead vendors strictly follow TrustedForm Consent Tagging guidelines so that the one‑to‑one consent data is accurately captured.
- Regularly review new consent language variations in your Consent Language Manager and update approvals as necessary.
- Clearly communicate your company’s consent language requirements to all partners and vendors to prevent discrepancies.
- Periodically test your Verify API integration with leads from different sources to ensure the “one_to_one” value is consistently and correctly reported.
Troubleshooting
| Symptom / Error | Likely Cause | Resolution |
|---|---|---|
| “one_to_one” property returns null/false | Required consent tags not properly implemented or the “advertiser_name” parameter missing in the request | Confirm with your vendors that TrustedForm Consent Tags are correctly embedded and verify that your company’s legal name is accurately entered. |
Frequently Asked Questions (FAQ)
Q: What exactly is the 1:1 Consent Check?
A: It is a TrustedForm Verify feature that programmatically tests if a consumer provided explicit one‑to‑one consent—consent that is uniquely tailored to your company—when submitting their information.
Q: Why is one‑to‑one consent important for my business?
A: One‑to‑one consent is essential to comply with regulations such as those enforced by CMS. It minimizes legal risks by ensuring you only contact leads who have explicitly agreed to be communicated with by your company.
Q: How do I implement and use the 1:1 Consent Check?
A: Enable the check on your Verification Criteria page by entering your company’s legal name, ensure that your vendors add the required TrustedForm Consent Tags, and integrate the Verify API in your lead processing system to automatically assess the “one_to_one” property.
Q: What does it mean when the “one_to_one” property returns null?
A: A null value indicates that the consent check could not be performed—either because the necessary consent tags were omitted on the form or the lead source does not support this check (e.g., Meta Lead Ads).
Glossary
| Term | Definition |
|---|---|
| 1:1 Consent Check | A TrustedForm Verify feature that verifies whether a consumer provided explicit one‑to‑one consent for your company’s communications. |
| TrustedForm Certify | The process and associated script that generates a certificate capturing a consumer’s session data and consent information upon form submission. |
| Consent Tags | HTML elements embedded in web forms that capture the consent language, ensuring that the consumer explicitly agrees to be contacted by a specific advertiser. |
| Verify API | The API endpoint used to assess a TrustedForm certificate against your defined criteria, including checking the “one_to_one” property for consent validation. |
| one_to_one property | A field in the TrustedForm certificate’s API response that indicates whether explicit one‑to‑one consent was provided (true, false, or null). |
Comments
0 comments
Please sign in to leave a comment.