8.4.6 Setup Price Rules/Dynamic Pricing (Feature Setting)

Version	2.119 and up
Support AdServers	N/A

1 Custom Fields as Matching Criteria: Matching Criterion
2 Price Rule Custom Matching with Multi-Select Picklists

Custom Fields as Matching Criteria: Matching Criterion

For additional flexibility within the Price Rules/Dynamic Pricing, you can configure your own custom fields as matching criteria for your price rules. Any number of custom fields or fields from the ADvendio Package can be configured as additional matching criteria.

Open or create a record with the feature setting name: Matching Criterion and Feature Name: Dynamic Pricing

If not exist yet, please create it yourself and fill in the following field values:

Feature Setting Name: Matching Criterion
Feature Name: Dynamic Pricing
Value: Is for you to configure. Please use the following syntax and don't forget the squared brackets to close in the whole string, and curly brackets for each value, and separate everything with a comma.
[{"operator":"==","field":"API Name of Field from Campaign Item (or related object)","conditionField":"API Name of the Field from Price Rule"}]

Above, in the screenshot, you can see an example of custom matching criteria for the billing category field located on the Ad Price level.
Another example is the combination of multiple fields, such as matching criteria for a custom Start and End Date:

[{"operator":"<=","field":"ADvendio__until_Date__c","conditionField":"Custom_End_Date__c"},{"operator":">=","field":"ADvendio__from_Date__c","conditionField":"Custom_Start_Date__c"}]

Please make sure that you use no whitespace or line break in the setting
You can use any field from an object related to Campaign Item, to do the objects need to be connected via Lookup / Master-Detail Field and you need to enter the entire field path.
Any of the following operators can be used: ==, !=, <, >, <=, >= Attention: not all operators can be used for all field combinations, example < will not work when comparing Picklist Fields or Checkboxes
To reduce errors, make sure the fields you compare are of the same type, and picklists have the same picklist values

Price Rule Custom Matching with Multi-Select Picklists

The new “in“ operator was added to support a price rule matching between multi-picklist fields.

To ensure accurate matching, please use the 'in' operator for multi-picklist instead of '==' in feature setting.

When you add the “in” operator then the price rule will now be applied only if all of the values selected on the price rule multi-picklist are also selected on the campaign item multi-picklist. The rule will also be applied if the campaign item multi-picklist has additional values selected, just like in the example below:

Example with a multi-picklist field for Targeting surcharges:

Geo
Inventory
Device

Previously, the system only considered exact matches when applying a price rule to a campaign item. Now a match occurs when all values from the Price Rule are selected on the Campaign Item's multi-picklist. This means that additional selections can now be made based on the provided table below:

Price Rule value	Campaign Item value	Expected behaviour

Price Rule value	Campaign Item value	Expected behaviour
Geo	Geo	Matching
Geo	Geo, Inventory	Matching
Geo, Inventory	Geo	Not Matching
Device, Inventory	Inventory	Not Matching