Capturing Leads From a Co-Registration Offer Path

TrustedForm works seamlessly with co-registration (“coreg”) platforms, but you may need to structure your pages differently to ensure that:

• The dynamically generated xxTrustedFormCertUrl field is captured and passed downstream.
• The consumer’s identifying information appears in the TrustedForm certificate.
• Your buyer receives either a single certificate or individual certificates per offer, depending on their requirements.

This guide explains how to implement TrustedForm correctly in a coreg environment and how to validate that your integration is working as expected.

Why Coreg Requires Special Handling

In a typical coreg flow:

• Users submit offers through your coreg platform—not directly to LeadConduit or a buyer’s CRM.
• The TrustedForm JavaScript snippet automatically injects a hidden certificate field (xxTrustedFormCertUrl) into every form on the page.
• Your platform must capture this hidden field on submission and pass it with the lead data.
• A TrustedForm certificate captures only the page on which the snippet is deployed. Pages are not linked, and multiple snippets on different pages do not share data.

Because of this, the consumer’s identifying information must be displayed on the same page where the TrustedForm snippet runs, so the certificate will include the information your buyer expects.

1. Capturing the Hidden xxTrustedFormCertUrl Field

What TrustedForm Automatically Does

• When the snippet loads, TrustedForm injects a hidden field named xxTrustedFormCertUrl (or a configured alternative) into each form on the page.
• Every form on that page receives the same certificate URL because TrustedForm generates one certificate per page instance.

What Your Platform Must Do

Your system should:

1. Capture all fields submitted with the form, including dynamically injected hidden fields.
2. Ensure xxTrustedFormCertUrl is included in the payload you send downstream.
3. Avoid hard-coding or manually adding the TrustedForm field—the SDK creates it automatically.

2. Ensuring Consumer Identifying Information Appears in the Certificate

TrustedForm certificates only reflect what is visible on the page containing the snippet.

To satisfy buyer expectations:

• The consumer’s personal information (name, email, phone, etc.) must appear on the same page as the opt-in for the offer.
• If consumer info is collected earlier in the flow, it must be re-displayed on the page where the consumer opts in.
• Snippets on different pages do not share visibility, so information on a previous page will not appear in the certificate.

3. Two Valid Coreg Implementation Patterns

Coreg platforms commonly implement TrustedForm using one of two patterns. Choose the pattern that aligns with your buyer requirements.

Option 1: Inline Expansion on a Single Page (One Certificate Per Page)

How it works:

• When the user selects an offer, you expand that offer inline on the same page.
• Previously collected identifying information is shown alongside the opt-in checkbox, disclaimers, or terms acknowledgment.
• The TrustedForm snippet runs once on the page.

Result:

• The entire page produces one TrustedForm certificate.
• All forms on the page share the same certificate URL.
• The certificate shows the consumer’s identifying information and all visible offer elements.

When to use it:

• When buyers are comfortable with one certificate covering multiple offers on a single page.

Option 2: Dedicated Page for Each Offer (Unique Certificate Per Offer)

How it works:

• Selecting an offer sends the user to a new page dedicated to that offer.
• This page displays both the user’s identifying information and the offer’s opt-in elements.
• Each page loads the TrustedForm snippet, generating a new certificate.

Result:

• Each offer gets its own unique TrustedForm certificate.
• Buyers can review each offer individually.

When to use it:

• This is the preferred method for most coreg operators, as it produces cleanly separated certificates per offer.

4. Validate Your Implementation

After implementing your chosen pattern, validate end-to-end:

1. Submit a test lead through your coreg flow.
2. Verify your captured payload includes:
   • xxTrustedFormCertUrl
   • All consumer identifying information
3. Open the TrustedForm certificate URL and confirm:
   • The page matches what the user saw
   • Consumer identifying information is visible
   • Opt-in elements and disclosures appear
4. If using Option 2:
   • Confirm each offer generates its own certificate
   • Ensure your platform associates the right certificate URL with the right offer

Troubleshooting

Frequently Asked Questions (FAQ)

Q: Do I need to manually add the xxTrustedFormCertUrl field to my form?
A: No. TrustedForm automatically injects it. Your job is simply to capture it on form submission.

Q: How do I ensure the certificate shows consumer identifying information?
A: Show the user’s identifying data on the same page as the opt-in elements where the TrustedForm snippet runs.

Q: Which integration option is recommended?
A: Most operators prefer Option 2 (dedicated page per offer), because it produces a unique certificate for each offer. Option 1 is still valid if one certificate per page meets your buyers’ needs.

Q: My platform already supports standard lead forms. What changes are needed for coreg?
A: You must:

• Capture the dynamic TrustedForm certificate field; and
• Display consumer identifying information on the same page as the opt-in capture.

Glossary