In this tab, users can manage the mapping rules of a specific Advertiser. The mapping rules allow the user to set or change values in the request being sent to the advertiser.
These rules are supporting setups done in other platforms/systems that need to be reflected in the requests being sent to the advertiser or they are created for the purpose of enriching the original data being sent in the requests.
On the creation of an advertiser or edit of an advertiser (edit icon on the actions column), you can define mapping rules from the 'Mapping Rules' tab in the advertiser's details form.
- Go to the 'Mapping rules' tab: Here you can define the mapping rules for your Advertiser.
This utility enables you to customize your mapping per the advertiser you can also choose to activate the 'All Partners' switch on the rule and the rule will be relevant to all advertisers. - The 'Incoming' property will be the dimension of the incoming request that needs to be matched to a value. The 'Target' property is the incoming request property that will hold the value. For example: for the incoming property 'Bundle' the target property that will be set up will be 'Placement'. Then after defining the incoming property and the target property and the relevant filters of the mapping if exist you can insert the relevant mapping by pasting the values separated by commas or uploading a CSV file.
- For example, you can map domains/bundles to placements. Each Domain/Bundle value will have the corresponding placement value. When the request will be sent to the advertiser the relevant placement value will be there for their matching.
- Users can add a value of ‘$_other_$’ to a data record:
This value is a special property that will catch all values that are not specified.
Be aware that by doing so this rule will not act as an allow list. - A bulk replacement action is available when you need to replace a specific TO value in all data records of a mapping rule.
- All entities Mapping Rules will be executed before Advertisers' specific rules.
Remember to add data records to your mapping rules. When you create a mapping rule for Domain or Bundle without associating the mapping rule to data records, you effectively pause your Advertiser activity.
Incoming properties
Bundle
Domain
Target property
Placement
If you wish to add incoming or/and target properties to your account mapping rules please contact support.
Additional available incoming properties:
ALL_REQUESTS
This rule will match all incoming requests, and can only contain one data record
APP_ID
APP_NAME
BID_FLOOR
COUNTRY
DEAL_ID
DISPALY_MANAGER
DISPLAY_MANAGER_VERSION
MEDIA_TYPE
PLACEMENT
PRICE
PUBLISHER_ID
SITE_ID
SITE_URL
SOURCE
STORE_URL
VIDEO_PLACEMENT_TYPE
VIDEO_PLCMT
SUPPLY_PARTNER_ID
WSEAT
Additional available target properties:
APP_ID
APP_NAME
AUDIO FEED TYPE
BID_FLOOR
BLOCKED_ADVERTISERS
BLOCKED_APPS
BLOCKED_ATTRIBUTES
BLOCKED_CATEGORIES
CONTENT_GENRE
CONTENT_RATING
COUNTRY
DOMAIN
DEAL_ID1
DISPALY_MANAGER
DISPLAY_MANAGER_VERSION
INVENTORY_PARTNER_DOMAIN
HEIGHT
MEDIA_TYPE
NATIVE AD UNIT
NATIVE CONTEXT
NATIVE CONTEXT SUB TYPE
NATIVE LAYOUT ID
NATIVE PLACEMENT TYPE
OS
PRICE
PUBLISHER_ID
SITE_ID
SITE_URL
SOURCE
STORE_URL
VIDEO_PLACEMENT_TYPE
VIDEO_PLCMT
SCHAIN
WIDTH
WSEAT
1 Deal ID
The format for the Deal ID is: id|price|seat
If you need more than one seat: id|price|seat1,seat2,seat3
If you need to set more than one deal, use the "$" sign to separate between the deals.
Example: my_sp_deal|3.3|234$my_sp_deal_2|0|34,23
Per this example, Gamoshi will create two private deals:
First deal
name : my_sp_deal
price: 3.3 and
Seat: 234
Second deal
name : my_sp_deal_2
price: auction price
Seat: 34,23
Be advised: The Price and Seat are not mandatory
Pricing rules:
If the price is set to 0 or nothing: The price will be the same as the bid request for the specific demand.
If the price is set to > 0 : The deal price will be whatever the define value is.
If the price is set to < 0 (aka -1): The price will be the bidfloor price.