How To Implement 1-To-1 Consent In CAKE (BETA)

CAKE's solution, referred to as Find Eligible Buyers, is designed to ensure compliance with the new FCC rulings while making it easy for our clients to integrate with their websites and current setups in CAKE. When enabled, CAKE dynamically identifies all the buyer(s) eligible to purchase the lead and presents a server-side response. The page owner is then responsible for storing this response, displaying key information to the consumer, then telling CAKE which buyers the consumer opted into so CAKE can appropriately route them.

How Is Buyer Eligibility Determined?

Eligibility is determined in 1 of 2 ways depending on the type of buyers you are working with:

1. If working with a direct buyer, eligibility will be determined by evaluating the buyer's schedule, caps, credit, routing rules, filters, and other criteria configured directly in the CAKE UI. 
2. If working with a lead aggregator/broker (someone reselling the lead on their end) eligibility can further be determined by sending a ping to the buyer's system. 

How Do I Enable Find Eligible Buyers On My Offer?

To enable Find Eligible Buyers, follow these steps:

1. Navigate to the Offer Card
2. Click the Lead Gen tab
3. Click the Routing sub tab
4. Check the box for Enable Find Eligible Buyers
5. Click Save

How Do I Make The Find Eligible Buyers Request?

The Find Eligible Buyers workflow uses a ping and post setup. Once the setting has been enabled on the offer, any successful Server Post or Session Post request to that offer will return the the Find Eligible Buyers response. This does not apply to Browser posts. The CAKE posting document, which can be located on the Home tab of the Offer card > Posting Doc button has been updated with detailed instructions.

How Do I Skip Required Or Validated Fields On The Find Eligible Buyers Request?

In certain scenarios, clients may need to fetch eligible buyers before they have captured or validated all the fields required to sell the lead. For these reasons, CAKE offers the flexibility to skip selected fields during the Find Eligible Buyer request. 

To skip a required or validated field, follow these steps:

1. Open the Vertical card
2. Navigate to the Fields tab
3. Click the name of the field you want to exclude for the F.E.B request
4. Click the Add button for any new validation or double click the row to adjust existing validation
5. Check the box titled "Exclude From Eligible Buyers"
6. Click Update to save
7. Ensure the enabled indicator shows green

How Do I Skip Filters On The Find Eligible Buyers Request?

Similar to required and validated fields, clients may need to find their eligible buyers before they have captured all the necessary fields that make the lead payable to affiliates or qualified for buyers. Since filters are created globally and can be applied as Paid Filters and/or Buyer Filters, CAKE has introduced the flexibility to configure at multiple different levels.

To skip a filter at all levels, regardless of if it is set as a Paid Filter (Vertical or Campaign) or as a Buyer Contract Filter, follow these steps:

1. Navigate to the Setup main tab
2. Navigate to Filter Types sub tab
3. Click the Add button to create a new filter or double click the row to adjust existing filter
4. Check the box titled "Exclude From Eligible Buyers"
5. Click Update to save
6. Ensure the enabled indicator shows green

To override the filter setting at the Vertical or Campaign levels, follow these steps:

1. Open the Vertical or Campaign card
2. Navigate to Filter/Paid Filters tab respectively
3. Click the Add button to apply a new filter or double click the row to adjust an existing filter
4. In the Exclude From Eligible Buyers dropdown, select the desired option:
   1. Yes = skip the filter on the F.E.B request
   2. No = run the filter on the F.E.B request
   3. Default to Filter Type = adheres to what is set on the global filter level
5. Click Update to save

To override the filter setting at the Buyer Contract level, follow these steps:

1. Open the Buyer Contract card
2. Navigate to Filters tab
3. Click the Add button to apply a new filter or double click the row to adjust an existing filter
4. In the Exclude From Eligible Buyers dropdown, select the desired option:
   1. Yes = skip the filter on the F.E.B request
   2. No = run the filter on the F.E.B request
   3. Default to Filter Type = adheres to what is set on the global filter level
5. Click Update to save

How Do I Interpret The Find Eligible Buyers Response?

The initial request/ping will return the Find Eligible Buyers response. Page owners are encouraged to store the entire response but specifically need to store the following fields in order to proceed with a subsequent consent post.

• guid - CAKE's unique identifier for the F.E.B ping request. This id will be used to marry the lead with the consent post using ckm_guid.
• buyer_contract_id - The CAKE buyer contract ids eligible for the lead. After consent, these ids will be used to route the leads to the appropriate buyers using ckm_consent_id.
• consent_option_name - Your buyer's name to be presented on-page to the consumer. Compliance requires this be the exact buyer name that would be contacting the consumer.
• consent_option_tcpa_language - Your buyer's TCPA language to be presented on-page to the consumer. Compliance requires this be the buyer's specific TCPA language the consumer must opt into.
• lead_id - (Optional) Can be used to update the lead before or after the consent post with additional information. See Lead Update Method for details.

How Does CAKE Order Eligible Buyers?

By default, the group and position number shown in the F.E.B response is organized with your highest paying buyers first. This is unless you have configured your CAKE system to use rank and priority instead of buyer price. CAKE intentionally does not provide the buyer's bid amounts within our response.

How Do I Present Eligible Buyers To The Consumer?

Page owners will determine the user experience. For instance, they will determine when in their funnel it is appropriate to fetch and display the eligible buyers on page, how many buyers to display, in what order, etc. Generally, clients tend to make this request to CAKE when they are about to display the phone number field to the consumer.

How Do I Support Lead Aggregators/Brokers With Multiple Sub-Bids?

CAKE recommends that you capture the entire response from the aggregator using the Buyer Consent Name Token (see next section for details). As the page owner, you are then responsible for parsing through this entire response to extract the individual bid ids (referred to as a sub-bids). On the consent post, pass the CAKE buyer contract id for the aggregator and a comma to delineate multiple aggregators. Within each aggregator, use a colon symbol to delineate the sub bid id and a pipe to separate multiple sub bid ids. 

Example: 

• ckm_consent_id=123:ABC|DEF,456,789:HIJ

Interpret as:

• Buyer contract id 123, sub bid ids ABC & DEF
• Buyer contract id 456 (no sub bids)
• Buyer contract id 789, sub bid id HIJ

In the buyer's delivery method, use the token #sub_bid_id# to map the associated value back to the buyer. 

Example:

• Mapped on buyer contract id 123 will return value ABC,DEF (comma separated)
• Mapped on buyer contract id 456 will return a null value
• Mapped on buyer contract id 789 will return HIJ

What is Consent Hierarchy?