<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1248981033026412&amp;ev=PageView&amp;noscript=1">

Dynamic Consent Documentation

Disclaimer: On January 24th, 2025, the FCC’s one-to-one consent rule, which required lead generators to obtain direct consent for each seller before contacting consumers, was struck down by the U.S. Court of Appeals for the Fifth Circuit. This means that, as of now, the rule is no longer in effect. However, businesses should continue to follow existing TCPA regulations and stay informed about any further legal developments or enforcement actions. This is not legal advice—please consult with a qualified attorney for compliance guidance. Please see this blog for more information.

boberdoo offers one-to-one consent solutions through our Dynamic Consent Form Builder and pingPostConsent API. Both solutions support retail and broker models, handle multiple distribution scenarios, and integrate with major lead generation companies and networks.

Updates and Alerts

  • Use the Dynamic Consent option in the Source Wizard to set up 1:1 sources. 
  • Seller Company Phone is now returned in the API response like forms. Use seller_phone_display.
  • If the profit on a lead is NEGATIVE and profit margin is NOT ignored, then lead posts will fail, because the lead could be sold with a loss. If you want to allow the post to be sold at a loss, edit the source settings to ignore profit margin. 
  • Bid_ID is a unique identifier that the lead system assigns to each potential match during the ping-post consent process.
  • Processing: pingPostLead and pingPostConsent behave the same way.
  • API Actions: pingPostLead and pingPostConsent. If you ping with one, you have to post with it.
  • Bid Modifiers are currently unavailable for pingPostConsent APIs and Dynamic Consent forms.
  • Bid Experiments are also not currently available for pingPostConsent API and Dynamic Consent forms.
  • Test_Lead=1 returns Matched response but total bids: 0 regardless of lead outcome.
  • For all updates, please refer to our changelog to get the full picture for all new updates. 

Processing Documentation

Topic Description Release Date Version & Download Link
Source Cost and Bid Explanation How vendor bids are returned and costs is calculated. January 16, 2025 v2 Download
Post Reject Second Chance Processing The presentation of additional matches after the initial company's attempt is unsuccessful.. January 15, 2025 v3 Download
Partner Consent Settings and Display Priority Options and priority of company information displayed to consumers.  January 16, 2025 v2 Download
Form Builder Documentation Place code on your site to dynamically display one-to-one matching companies.. January 16, 2025 v2 Download

 

Partner Use Case Documentation

Partner Type Description Release Date Version & Download
Exclusive Retail Partner Only and final company displayed. January 16, 2025 v2 Download
Shared Retail Partner Final company but may be one of many companies displayed. January 16, 2025 v2 Download
Exclusive Scenario Broker  Company that submits one bid for multiple companies to display. January 16, 2025 v2 Download
Shared Scenario Broker Company that submits a unique bid for each company returned to display. January 16, 2025 v2 Download
Exclusive Broker with RedirectURL Company that returns an additional redirect URL with success response. January 16, 2025 v2 Download

 

Dynamic Consent Reports

  • Forms Rejects Report - specifically identifies leads that come from boberdoo forms that are rejected. 
  • Incoming API Count By Source - summarizes a count of all posting API calls from each source per lead type. 
  • Consent Vs Regular Lead Post Report - summarizes a count of posted lead from pingPostLead and pingPostConsent APIs.

Webinar Resources

We have different webinars we have hosted and been a part of regarding one-to-one consent and our solutions for them. To sign up for any future webinars, please check out our boberdoo U sign up page

boberdoo Dynamic Consent Release Q&A

boberdoo Dynamic Consent 5.20.134 Release Update

Working with Resellers boberdoo's One-to-One Consent Webinar

FCC SERIES: EPISODE 17 - Lead-Gen 2.0: A detailed compliance checklist for 1:1 consent management with ActiveProspect

boberdoo Update 5.20 Walkthrough

boberdoo's Solution for the FCC One-to-One Consent Requirement

FAQ

Why does the post reject page display the consumer's phone number again?

The consumer's phone number is displayed on the Post Reject Second Chance step because that is required to be on the same page as the company and the "agree" button to which the consumer is providing consent. Because the consumer's original consent is no longer valid, we present the phone number again with the new match for new one-to-one consent.  

Do you have a checklist that we can use to get ready?

Yes! You can view it and download here.

How is source cost calculated in pingPostConsent API?

  • pingPostConsent and pingPostLead behave differently
  • pingPostConsent always calculated:
    • The lead cost is set as price - margin AFTER the sale is completed according to the selected matches and respective sales. 
    • The fixed cost set on the source is IGNORED for the consent lead post.

Will pingPostLead be deprecated in favor of pingPostConsent? 

No, pingPostLead will still work how it always has. 

I sell my leads exclusively. What happens if the consumer consents to the best bid but the post to that partner later fails? Can I still get consent for my other buyers? 

Yes, please see the Second Chance functionality available in boberdoo. 

Where can I “see” Dynamic Consent?

  • Forms Rejects Report
  • Leads tab filters
    • Is Dynamic Consent API?
    • Form Type
    • Green lead log

I already have boberdoo forms created. How can I update these forms to be Dynamic Consent?

You will need to create new forms that are Dynamic Consent instead of Standard forms. If you have to re-create a lot of them, templates can be helpful, which you can create while creating Dynamic Consent forms. 

Why does the consumer's phone number show up again? Regarding form builder with post reject second chance enabled.

The consumer's phone number is displayed on the Post Reject Second Chance step because that is required to be on the same page as the company and the "agree" button to which the consumer is providing consent. Because the consumer's original consent is no longer valid, we present the phone number again with the new match for new one-to-one consent.

How do I capture a Broker’s selling company?

  • Partner Company Display Priority
    • Company information returned in custom delivery
    • Consent Settings Configuration>Seller Company Name
    • Partner Company Information ONLY if no other settings are configured
  • Enhance Partners to consumers with:
    • Seller Company Phone
    • HTML Offer content