Submit a Ticket My Tickets
Login  Sign up

Condition Formulas Explained on Buyer Contracts

This document outlines Condition Formulas on Buyer Contracts.

Condition Formulas will examine lead data for the purpose of "conditionally" posting specific fields based on the exact content of the lead field in comparison to the formula.

Condition Formulas are based on SQL formulas, which are similar to excel.

Fields from your Vertical can be wrapped in "#" symbols to evaluate the data.

Let's take a look at an example below.

1. This formula will evaluate whether #zipcode# is equal to "55555". Because that data type is a "number" in the vertical, the SQL formula here does not need single quotes like the condition formula for the "state" parameter. If the condition formula equates to "True", then that parameter and value will be passed to the buyer on the post.  If it does not equal "55555", this field will not be passed to the Buyer.

2. This formula is depicting how you don't need to use tokens only referring to the parameter you're evaluating. This parameter is going to check the #zipcode# token from the vertical, to evaluate whether it should be sent to the buyer or not. In this example, if zipcode=55555, CAKE Basic will deliver the City to the Buyer.

3. This condition formula is representing what happens if your using a token for a "string" data type. The only difference here is when the token is used, the token needs to be wrapped in single quotes. Number data types do not need single quotes, while the rest of the data types do (including string, bool, date, and list).

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.