Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

Defining Matching Criteria

...

For example, the Price Rule below would be applied to Campaign items which are in a Media Campaign with business Type Rebate in Kind, based on the Ad Spec news.com_Homepage_Banner and capped at 100 Clicks per 1 hour.Image Removed

...

Predefined Matching Criteria

You can create your price rules to be as specific or as broad as you want using the relevant matching criteria.

Matching Criteria

Source / Additional Information

Advertising Medium

Source: Ad Spec

Placement

Source: Ad Spec

Ad Spec

Source: Campaign Item

Ad Type

Source: Ad Spec

Ad Price

Source: Campaign Item

Business Type

Source: Media Campaign

Media Type

Source: Site

Media Differentiation

Source: Ad Type

Media Segment

Source: Placement

Days Until Start Date

Applies the Price Rule to Campaign Items which are starting within x amount of days. 

For example, you enter a value of 20, the Price Rule applies to Campaign Items where

the From

the From (Date) is in 20 days or less (counting from the current day)

Legal Entity

Source: Media Campaign

Content

Source: Campaign Item

AdServer ID Category

Source: AdServer ID / Connection

Id

ID

AdServer ID / Connection

Id

ID

Source: Selected AdServer ID / Selected Connection

Id

ID

Info

If you would like to define a list of Connection Ids as matching criteria for your Price Rule please take a look in the row below.

List of AdServer IDs/Connection

Ids

IDs in the junction object called "Connection

Id

ID Price Rules Assignment".

Source: Selected AdServer ID / Selected Connection

Id

ID

As of version 2.147 a new object "Connection Id Price Rules Assignment"

 was

 was created to link a list of Connection IDs to your Price Rules as matching criteria.

Info

Please take note that the logic to match the Campaign Item with the Price Rule is that all Connection

Ids

IDs are handled with a logical "Or" statement so that at least one of the Connection IDs needs to be assigned to your Campaign Item in order to match the Price Rule to it.

 If

 If the AdServer

Id

ID/Connection

Id

ID lookup mentioned above is filled, the list of Connection

Ids

IDs will be ignored.

AdServer ID Type / Connection Id Type

Source: AdServer ID

Frequency Capping

Source: Campaign Item

Info

If set to true, the Price Rule applies to Campaign Items which have Frequency Capping set using the Frequency Capping field on Campaign Item. 

FC Quantity

Source: Campaign Item

FC Every

Source: Campaign Item (FC Ad served every)

FC Unit

Source: Campaign Item (FC Period)

Day & Time Targeting

Source: Campaign Item

Info

If set to true, the Price Rule applies to Campaign Items which have day & time targeting set using the Day & Time Targeting field on the Campaign Item. 

Custom Matching Criteria

Version 2.119

It is now possible to You can create your own custom matching criteria for your Price Rules. In order to do this, your Salesforce Administrator will need to set up the relevant matching criteria. For more information, see 8.4.6 Setup Price Rules/Dynamic Pricing (Feature Setting).

...

As of version 2.119, the package header is leading in the matching of Price Rules. This means that when creating Price Rules, it is possible to configure whether these rules are package-relevant and you can treat your inventory different differently whether it is part of a package or not.

Once a rule is matched to a Package Header, all components in the Package will also have the price rule applied. No non-package relevant Price Rules will be applied 

|

For example

  • I have Price Rule A which

    is matching 

    matches the Ad Spec for Package Header A (marked as Package Header relevant) (Applied)

  • I have Price Rule A.2 which

    is matching

    matches the Placement for Package Component A.2 (Not Applied)

  • I have Price Rule B.2 which

    is matching

    matches the Ad Price for Package Component B.2 (Applied)

  • I have no valid Price Rule which is matching for Package Header B

Below you can see an example of how the above price rules are applied to Packages A & B.  LucidchartpageCount2autoUpdatefalsealignlefttyperichautoSize1macroIde080162d-d345-4a52-86a9-b410bb2977b5instanceIdConfluence:7754241159pageswidth700documentIda4cdbcb7-372b-400f-8e31-657138cec7efdocumentTokena4cdbcb7-372b-400f-8e31-657138cec7ef|105874146|701235211|X4S5ZfeM11X8Ed8fhBbuOZdxday36OtYU3fkcjRCHsI=updated1575467519498height500

...