Ad Position Placement
Introduction
The Ad Position Placement (f42_dispo__AdPosCatalog__c) defines the quantitative availability of placements per issue.
Availabilities bring together ad formats, issues and placements. This object stores information about which placement can be sold in which format and how often per issue.
First, the maximum availability is determined for each placement and issue.
After the initial implementation, executed bookings, booked entries, and reservations will be written on the record by using Roll-Up Summary to automatically update the remaining capacity within a formula field.
While placements in printed products are physically limited (only one booking is made for each placement), the availability on digital products are quoted according to clicks (CPC) and views (CPV, AI). This means that, in addition to recording individual bookings, digital products must also record this so-called volume.
Explanation
The availability controls how often a placement may be sold per issue. This can be limited accordingly by setting limits. The field "availability" calculates how much inventory is left on this basis:
Object Structure
Salesforce setup
The object “Ad Position Placement” is already available as a tab. New records can be added with a few links:
Only a few details are required to create a new placement option:
Field (with example) | Explanation |
---|---|
The availability (lookup relationship) refers to this placement | |
The availability (lookup relationship) refers to this publication | |
The availability (lookup relationship) refers to this issue | |
Physical limit, number of allowed prints | |
Number of permitted bookings, this may differ from the print limit. |
Most of the other field values on the availability record are automatically created and updated using lookup and calculation fields, providing a general picture of initial quantity, reservations, bookings and remaining availability.
Technical Description
The Ad Position Placement object has the central function in the MediaVelox AdSales process. It has a master-detail relationship to the two detail objects Booking (f42_dispo__DispoBook__c) and Blocked Position (f42_dispo__DispoBlockedItems__c) and brings together all current valid Placement availability in the field Availability (f42_dispo__countAvailable__c)
API Name | Label EN |
---|---|
f42_dispo__AdPosCatalog__c * | Ad Position Placement |
Name | Label EN | Type | Note |
---|---|---|---|
Name | Ad Position Placement Number | Auto Number | The name of the Ad Position Placement is determined generically as an auto number. |
f42_dispo__isActive__c | Is Active | Checkbox | Only placement options marked as "active" are considered in the quotation process. |
f42_dispo__f42_AdFormatName__c * | Ad Format | Formula (Text) | Determines the ad format of the affected placement using a formula. |
f42_dispo__Issue__c * | Issue | Lookup(Issue) | Mandatory field. References the relationship to the corresponding issue. |
f42_dispo__IssueName__c | Issue Name | Formula (Text) | Optional. Displays the name of the issue. |
f42_dispo__IssuePubDate__c | Publication Date | Formula (Date) | Publication date of the mentioned issue, is determined via formula. |
f42_dispo__AdPosition__c * | Ad Position | Lookup (Ad Position) | The availability is related to this placement / ad position. |
f42_dispo__Publication__c | Publication | Lookup (Publication) | Mandatory field. References the relationship to the corresponding publication. |
f42_dispo__countAvailable__c * | Availability | Formula (Number) | Formula that indicates the actual availability of the placement by deducting the booked, blocked positions, accepted and reserved bookings from the print limit. Core statement of the formula: Physical limit of an availability - blocked positions in status reserved/posted - Booking entries in status reserved/posted.
|
f42_dispo__bookingLimit__c * | Limit Booking | Number (10, 0) | Defines a limit for the number of possible bookings. |
f42_dispo__physicalLimit__c | Limit Print | Number (10, 0) | Physical limit. The calculation of the remaining availability f42_dispo__countAvailable__c refers to this value. |
f42_dispo__reservedCountRollup__c * | Sum Reserved | Roll-Up Summary (COUNT Booking) | Number of all reserved bookings (Booking entries with status “reserved”). |
f42_dispo__confirmedCountRollup__c * | Sum Confirmed | Roll-Up Summary (COUNT Booking) | Number of all confirmed bookings (Booking entries with status “confirmed”). |
f42_dispo__DispoBookSumVolumeReserved__c | Sum Reserved Volume | Roll-Up Summary (SUM Booking) | Refers to digital products that are booked over a certain term. Here, availability is not only reflected by the number of booking entries but also by volume (e.g. booked ad impressions, clicks, etc.) The booking status is "reserved". |
f42_dispo__DispoBookSumVolumeConfirmed__c | Sum Confirmed Volume | Roll-Up Summary (SUM Booking) | Refers to digital products that are booked over a certain term. Here, availability is not only reflected by the number of booking entries but also by volume (e.g. booked ad impressions, clicks, etc.) The booking status is "confirmed". |
f42_dispo__AmountBooked__c | Amount Booked | Roll-Up Summary (SUM Booking) | Specifies the net sales of confirmed bookings. |
f42_dispo__AmountReserved__c | Amount Reserved | Roll-Up Summary (SUM Booking) | Indicates the expected turnover of the reserved bookings. |
f42_dispo__sumMovableReserved__c | Sum movable reserved | Roll-Up Summary (COUNT Booking) | Number of all booking entries with status "reserved" that can be moved to another issue. |
f42_dispo__sumMovableBooked__c | Sum movable booked | Roll-Up Summary (COUNT Booking) | Number of all booking entries with status "reserved" that can be moved to another issue. |
f42_dispo__blockedCount__c * | Sum Blocked Positions | Roll-Up Summary (COUNT Blocked Position) | Number of existing blocked positions with booking status "reserved". These are also deducted from the availability. |
f42_dispo__blockedCountBooked__c | Sum Blocked Bookings | Roll-Up Summary (COUNT Blocked Position) | Number of existing blocked positions with booking status "confirmed". These are also deducted from the availability. |
f42_dispo__blockedSumReserved__c | Volume of Block Positions Reserved | Roll-Up Summary (SUM Blocked Position) | Refers to digital products whose availability is also measured in volume. |
f42_dispo__blockedSumBooked__c | Volume of Block Positions Booked | Roll-Up Summary (SUM Blocked Position) | Refers to digital products whose availability is also measured in volume. |
f42_dispo__Theme__c | Topic | Text (255) | Optional specification of a subject area |
f42_dispo__Description__c | Description | Long Text Area(32000) | Optionally, a description can be entered here. |
f42_dispo__PublicationName__c | Publ. Description | Formula (Text) | If required, this field gives the description of the publication the issue is assigned to. |
f42_dispo__TransactionLimit__c | Transaction Limit | Number (18,0) | Regarding digital publications: With the transaction limit you can optionally restrict the bookable quantity to a value smaller than the actual availability. |
f42_dispo__PreventOverbooking__c | Prevent Overbooking | Checkbox | Verhindert das Überbuchen der Verfügbarkeit bei digitalen Publikationen. |
f42_dispo__AllowOverbooking__c | Allow Overbooking | Checkbox | Regarding digital publications: With the transaction limit you can optionally restrict the bookable quantity to a value smaller than the actual availability. |
Note, the fields marked with * are included in the availability check calculation in the quotation process.
Volume vs. Bookings
For date-based issues ad position availability, the number of bookings is equal to the number of booked placements. For each placement, a single Booking is created (for example: two 1/1 pages in the January issue are two separate bookings).
For issues for which availability can be booked variably over a certain period of time (time-period-based), an additional parameter is required: the booked volume.
For example, over the duration of the January issue of a digital magazine, I can reserve a subset of 30,000 AdImpressions from the maximum availability of 100,000 AdImpressions for a customer. In this case, of course, no 30,000 individual bookings are generated. Instead, a single booking with a volume of 30,000 AdImpressions. This value is then stored in the corresponding fields Sum Reserved Volume or Sum Confirmed Volume when the quote is marked as reserved or confirmed.
Related Topics
Availability check: Real-time query of available placements in the quotation process
Block Position Rule: How are blocking notices generated when bookings limit the availability of other placements?
Dispatch book / Bookings: After the quotation process, bookings are entered into the object Booking and can be managed from there.