When you requested to open an account with us you provided us with information about your company/business. These details are in the Account section. It is your responsibility to make sure your company/business details, contact details and payment details are all up to date.
You must keep your company details up-to-date at all times (as required in our standard AdServing Factory Exchange Agreement). This is not just for legal issues, but it is also important for urgent notifications. In our system the Account Owner is referred to as the Administrator. This is also the user that is the official company representative. The Administrator can update company details as follows:
Please note that ID relates to how we recognise your account within our system. ID cannot be edited or updated
We need your payment details in order to pay you. It is entirely the responsibility of the Administrator to accurately input the payment details. Only the Administrator account has the authority to input or change beneficiary details. Please remember we operate a self-billing process, so DO NOT SEND US AN INVOICE. You can download your invoice to us in the Payment Section.
To input or update beneficiary details please follow these steps:
* Required fields under the Bank Details section may differ for different countries
AUX is designed to accommodate either single or multiple users in the same account based on a permission and security tree. AUX works for single-site Publishers, multi-site Publishers as well as Networks and Sales Houses. Reporting and trafficking privileges can be defined on a user, campaign and site basis. Therefore, you can use many users for different sites yet keep your account and billing details safe.
You can see an example for a three website account below:
In order to update user details please follow the instructions below:
The account Administrator can request additional Users to be added to the account. Only the account Administrator can request additional users. The request is made via a Support Ticket raised via the user interface. The Support Ticket must include the new user details (name and email address) as well as desired access privileges for the new user.
See part 7.1: Raising a Support Ticket of this User Guide to find out how to raise a Support Ticket.
Publishers can access buyer demand for all devices with AdServing Factory’s AUX. A publisher may use either responsive site design or specific sites for mobile and desktop. AUX provides demand for standard image, video and native formats as below:
|Ad Formats Available|
|Standard Image Ads||Video Ads||Native Ads|
|All standard IAB desktop formats||Desktop (in-stream and out-stream)||Desktop (in-stream and out-stream)|
|All standard IAB mobile formats||Mobile (in-stream and out-stream)||Mobile (in-stream and out-stream)|
We use the latest IAB and technical standards for image, video and native ads (HTML5, VAST 2.0, VPAID 2.0, MRAID 1.0). Video ads are natively integrated into our platform or can be served from third-party ad systems with standard VAST 2.0 wrappers. We work with VAST 2.0 and VPAID 2.0 tags. AdServing Factory also provides a free hosted video ads platform that works with the most popular video players: JW Player, Flow Player and VideoJS.
Sites refers to your websites (responsive, desktop or mobile), e.g. http://abctestsite.com. You may add new Sites any time. Once you have created a new Site it will not become Active (i.e. made available to buyers on AUX) until it has been activated by AdServing Factory Customer Support. Please note that while a Site may be Active, it still may take up to 7-days to be approved by all our demand partners (i.e. full demand for any Site may take up to 7 days).
Sections refer to the different type of pages in your website, e.g. Homepage and Article Page. Since many publishers want to handle the homepage differently from other pages in terms of both placements and reporting. A publisher may then implement a different set of tags for the homepage than for other pages. This will enable a better breakdown in reporting. If you wish to have additional Sections please contact AdServing Factory Customer Support via your login. Please note that it is NOT mandatory to configure a Section and can be left as Unspecified.
Zones refer to the placements, e.g. Halfpage (300x600) or Top (728x90). In AUX, Zones are predefined within your account and are selected from a drop-down menu. If you wish to have additional Zones because you did not find a suitable format within the drop-down menu please contact AdServing Factory Customer Support via a Support Ticket (see Section 7.1: Raising a Support Ticket).
In order to see all your Sites, and related Sections and Zones in your account, please follow these steps
If you want to see more details of your website or even change some fields, please follow these steps:
* Status cannot be updated from the user interface. If you wish to delete a Site please contact AdServing Factory Customer Support via your login.
If you would like to add new Site to your AUX account please follow these steps:
Click Save button to complete process
Click Save & Open Site button to display site detail page after creating the new site
Click Save & Open In a New Window button to display site detail page in a new window after creating the new site.
When a new Site is created the Status will be Suspended until Customer Support has approved it (usually within 48 hours) . If you wish to activate it urgently please contact AdServing Factory Customer Support via your login.
You can easily display a Section by following these steps:
If you want to add new section or update it as out of use, please contact us.
You can easily display a Zone by following these steps:
If you want to add new Zone or update it as out of use, please contact us.
Summary of our pre-defined zones:
AdServing Factory Ad Tags are HTML code that is put into directly into publisher’s Site or ad server. AdServing Factory Ad Tags are used to call our AUX server to request an ad
In order to display Single Ad Tag page:
From this page, you can update your preferences and advanced settings for the Ad Tag. Please check 2.5.3 Advanced Ad Tag Preferences chapter for further information
You can easily create an AdServing Factory Ad Tag by following these steps:
After generating the Ad Tag for the selected Section and Zone, you can specify tag type as either Standard or VAST Video.
Then, all you need to do is to copy the Ad Tag and paste it to your website code or ad server
Please contact AdServing Factory Customer Support via your login if you need help with this.
You can add following specialities to you tag just putting ticks to related options:
You can add passback function easily by following these steps:
In order to prevent passback loops, please avoid recursive output of the AdServing Factory tag on your adserver passback request.
A possible configuration for Google DFP using specific macros is as follows:
Please note the key-value setting (exchange = AdServingFactory) within the "Targeting" parameter. This implies having the "exchange" key in DFP and setting a delivery restrinction on the AdServing Factory campain (exchange != AdServingFactory).
By doing so, you will ensure that once the impression is being passed back in DFP, it will not deliver the AdServing Factory ad tag again for the same impression, thus avoiding the passback loop. Note that you can however use other key-value pairs that you may already have.
AUX comes with an advanced tag generator and tagging options designed to assist with fast implementation of tags. There is a Bulk Ad Tag option that creates tags for all Zones (placements) so they do not have to be created one-by-one. This is a time saving feature. The Ad Tags created using the Bulk Ad Tag feature are the same as if they were created one-by-one.
If you want to generate Bulk Ad Tags, you need to click Bulk Ad Tags button when creating new ad tag.
The IAB’s Ads.txt project is the latest initiative for improving transparency in programmatic advertising by allowing publishers to declare authorized partners to sell their inventory. By creating your ads.txt file, you can protect your inventory from domain spoofing and unauthorized sellers.
Ads.txt is not mandatory but is highly recommended. It provides protection by giving DSPs a simple way to check if inventory from a particular source has been authorized by the domain owner.
In order to setup ads.txt for AdServing Factory authorization you must copy the following lines (please include the #AdServing Factory AUX comment) into your domain's ads.txt file (http://yourdomain.com/ads.txt).
#AdServing Factory AUX adunity.com, 1000001, RESELLER indexexchange.com, 183775, RESELLER openx.com, 537101597, RESELLER contextweb.com, 558315, RESELLER, 89ff185a4c4e857c
Please implement on all your sites/domains where AdServing Factory AUX ad tags are trafficked. Also, please consider that the ads.txt file can include multiple authorized partners within the same exchange/hub.
AUX is connected to over a hundred demand sources including the biggest and most reputable in the market. However, even the biggest DSPs have problems with fraud and malware. This is why we constantly check for malware, spoofed landing pages, unidentified creative attributes and various other hidden dangers. AdServing Factory uses automated systems to continually scan demand from our partners to identify and neutralise malware and other fraudulent activity. We also employ a combination of robust validation processes and technology to vet new demand sources
However, there are still times when a publisher will want to filter out advertisers for commercial and editorial reasons. This is why we developed our Brand Safety features. Aside from the obvious issue of ad quality there are several common situations where a publisher would want to block specific advertisers. These are listed below.
|When it is appropriate to block advertisers|
|1||When the advertising breaks editorial policies, e.g. blocking fast-food ads on a dieting/healthy eating site.|
|2||When the advertiser is a competitor, e.g. blocking ads for subscriptions to a financial news site, on a site in the same sector with the same subscription business model.|
|3||When the advertiser is already a direct buyer of media, i.e. stopping a direct advertiser’s ability to buy cheaply on the open market when they are buying on a premium/ guaranteed basis.|
|4||In order to avoid poor quality ads, such as ads for "miracle cures" and "get-rich-quick schemes"|
We believe that the more control the Publisher has in accepting or rejecting advertisers the better. AdServing Factory provides this control. We have two features under Brand Safety: one is to make a custom block/blacklist against specific advertisers and the other is to make a make custom block/blacklist by category.
Ad Preview shows the ads served to a publisher's site (both image and video ads) in a single place. This not only provides evidence of the quality of the creatives but also provides the bid range for each creative
In order to access Ad Preview:
* These screens can be filtered by site if required.
Each ad preview window, there are:
Publishers can block/blacklist specific advertisers by domain with an additional option to block all sub-domains too. The Advertisers that are blocked are shown on the blacklist but can be reinstated any time with a single click to unblock.
In order to block an advertiser:
Many advertisers flag their category based on IAB Quality Assurance Guidelines contextual taxonomy. AUX uses these flags to identify and potentially block categories of advertisers
In order to block an advertiser category please follow these simple steps:
Each ad impression is a unique event and AUX can maximise the value of each one. Two important things we can do to maximise the value of ad impressions are: firstly dynamically vary the bid-floor; and secondly if necessary utilise a soft bid floor. AUX’s dynamic bid floor technology is called Dynamic Lift. AUX’s soft bid floor technology is called Soft Bid Floor. These two tools can be enable by the publishers under Auction Intelligence control panel (shown below), which is under the Auction Settings (shown below) which is accessible via the right menu.
Dynamic Bid-Floor refers to a programmatic seller-side technique to maxmise revenue for the publisher in a real-time auction by varying the bid floor dynamically. AUX’s dynamic bid-floor technology is called Dynamic Lift. Dynamic Lift automatically changes the bid floor in order to come close to what is calculated to be the maximum price a buyer is willing to pay. This price can be above or below the Base Bid Floor. Dynamic Lift is enabled and adjusted by publishers. AdServing Factory recommends that publishes enable Dynamic Lift and set allow bids at least 50% below Base Bid Floor.
Soft Bid-Floor refers to a programmatic seller-side technique to maxmise revenue for the publisher in a real-time auction by accepting bids below the Base Bid Floor. Soft Bid Floor is enabled and adjusted by publishers. AdServing Factory recommends that publishes enable Soft Bid Floor and set allow bids at least 20% below Base Bid Floor.
Base Bid-Floor is reference bid-floor that the publisher sets. AdServing Factory recommends that the Base Bid Floor should be set at the level of expected eCPM for that Zone provided that Dynamic Lift is enabled and the lower limit of the Dynamic Lift setting is at least 50%. If the lower limit is not set to at least 50% of Base Bid Floor then the Base Bid-Floor should be set at a rate below expected eCPM for that Zone.
Dynamic Lift is not enabled by default. It can only be enabled by the publishers. Dynamic Lift significantly improves floor price efficiency because it automatically varies bid floor for each impression in real-time in order to maximise sale price. Dynamic Lift is enabled and adjusted by publishers to suit their particular market conditions and to optimise for different types of sales targets and business goals
In particular Dynamic Lift solves a common problem for publishers: selling inventory at below market value. This happens in situations where there are only one or two bidders for a particular impression (often just one serious buyer and one low-value opportunist buyer). Given the rules of the Vickery Auction (second price auction), the highest bidder wins, but only pays the bid floor price (plus one cent) or the second-highest bid, whichever is highest
Therefore, in many cases the bid-floor effectively becomes the sale price. Hence the ad inventory becomes undervalued and the benefits of an auction market evaporate. This market inefficiency problem is illustrated below.
There are three main reasons why this is such a common problem. Firstly programmatic buying is driven by targeted audience data, so if the audience is not a match for the campaign there is no. Secondly, campaign pacing by DSPs means they do not always bid for audiences they are interested in. Thirdly, many DSPs understand these market dynamics and bid at below market rates to exploit arbitrage opportunities (i.e. buy low and sell high).
The only way to correct this market failure is to adjust the bid floor on an impression-by-impression basis to match or get very close to real market value. This is what Dynamic Lift does. Dynamic Lift automatically adjusts the price floor towards real market rates and makes a significant improvement to publishers’ revenues as shown below.
Dynamic Lift technology combines analyses of the real-time bid landscape together with an analysis of both bid quality and bid density on a user basis. This analysis creates new bid floors in real-time depending on current market conditions and historic demand for any given audience/inventory
Auction Settings is where Base Bid Floor can be set for each Zone and where Auction Intelligence control panel is located. The Auction Intelligence Manager control panel is where Dynamic Lift and Soft Bid Floor can be enabled and adjusted.
In order to display Auction Settings page where Base Bid Floor can be set for each Zone:
Auction Settings is where Base Bid Floor can be set for each Zone
In order to set the Base Bid Floor for a Zone to display Auction Settings page where Base Bid Floor can be set for each Zone and:
Dynamic Lift is not enabled by default. To enable Dynamic Lift follow these steps:
Once Dynamic Lift has been enabled the Lower Bid Floor Limit can be set. By default it is set to 50%. In most scenarios AdServing Factory recommends that it remains at 50%, but the publisher may change it. To adjust this setting please follow these steps:
Once Dynamic Lift has been enabled Strategy can be adjusted. By default strategy is set to Fill. To adjust this setting please follow these steps once Dynamic Lift has been enabled:
Fill Strategy optimises the Dynamic Lift technology to maxmise fill. This means it aims to fill as many ad impressions as possible with auction wins.
Revenue Strategy optimises Dynamic Lift technology to maxmise revenue. This means it aims to maximise overall revenue.
Balanced Strategy provides an even balance between Fill and Revenue Strategies.
Soft Bid Floor is not enabled by default. To enable Dynamic Lift follow these steps:
Once Soft Bid Floor has been enabled the Lower Bid Floor Limit can be set. By default it is set to 50%. In most scenarios AdServing Factory recommends that it remains at 50%, but the publisher may change it. To adjust this setting please follow these steps:
AdServing Factory provides some of the most transparent and detailed reporting in the industry.
The Open Auction programmatic market is still a black box for most Publishers. Publishers simply do not know who is buying their media and how much they are paying. In contrast, AUX provides full visibility with market-wide and bid level insights. Using AUX reporting tools a Publisher can evaluate demand across multiple dimensions: advertiser, Zone, geo and even bid-range. This valuable insight can be used to better inform sales strategy.
Reporting on AUX is divided into two areas and each has its own dashboard: Revenue (for market demand and revenue focused reporting) and Reporting (for inventory focused reporting).
* Requests means the total number of impressions that have been successfully received by AdServing Factory.
** Win Rate means the percentage of requests that are sold.
You can track the inventory of your site/s in detail. Further reports are available under AUX Traffic Viewer.
The AUX Inventory Dashboard provides an instant visual feedback on the performance of a Publisher’s ad inventory. This dashboard highlights and compares the key inventory related metrics: impressions, requests* and win rate**. Various charts break these down by time, site and zone. Charts can be filtered to show the publisher network or on a site-by-site basis.
Below the charts is a table showing raw traffic numbers with a detailed breakdown. There is also a link for the AUX Traffic Viewer reports
AUX Traffic Viewer is where a publisher can define and download any reports about their network, individual sites or placements
* Requests means the total number of impressions that have been successfully received by AdServing Factory
** Win Rate means the percentage of requests that are sold
In order to access the AUX Traffic View page please following step:
The AUX Traffic Viewer is designed to show as many or as few columns as needed. These reports can include details of eCPM; revenue; wins/sold impressions, clicks, country/geo and passbacks.
Forecasts is where a publisher can see how many ad impressions of different types are forecast to be available for a future time period. The forecast calculation is based on historic traffic. If the publisher has reserved impressions for this future time period, these are also shown. These Forecast Reports can include a breakdown by site; zone and country.
* Requests means the total number of impressions that have been successfully received by AdServing Factory.
** Win Rate means the percentage of requests that are sold.
The AUX Revenue Dashboard is designed to provide immediate analysis of the market demand for a publisher’s inventory as well as trend and historical sales performance. This is achieved with charts comparing key commercial performance data sets. Together these charts provide a powerful analysis of the bid landscape facing the publisher and the relative ad sales performance of Sites and Zones (placements) over last 14 days.
AdServing Factory invoices and collects revenue on an on-going basis from numerous media buyers in several different currencies and at different billing cycles. The payments from media buyers are aggregated and processed before being paid onto you. See below the main points of our payments process:
Self-Billing: AdServing Factory operates a self-billing process. This means we invoice ourselves on your behalf every calendar month. DO NOT SEND US AN INVOICE. You can download your invoice to us in the Payment section of the AUX. See section 6.5 Download Invoice.
VAT: If applicable invoices will include VAT. You must provide AdServing Factory with your VAT number if you have one. If your company is based in the RO the VAT invoice to AdServing Factory will be charged at 19%. If the your company is based in another EU country the VAT invoice will have VAT zero-rated and the sale will be classed as a despatch between EU countries.
Calendar Month: AdServing Factory works on a calendar month basis for all invoices, billing and payments.
Commission: AdServing Factory takes a sales Commission of 20% on the value of programmatic sales on AUX. This sales commission is taken before the amount displayed on the Revenue Dashboard. This means that the money amount shown on the Revenue Dashboard is that amount that will be paid to you.
60 Days: Revenue generated on AUX is paid in 60 days from the end of the relevant calendar month. For example, revenue generated for the month of January will be paid at the end of March.
Pending Payment: A Pending Payment is a payment that is due to be paid to you for a given calendar month. Pending Payment for a given month may differ from the estimated amount as shown on the Revenue Dashboard depending on whether AdServing Factory received expected payment from media buyers. An alert email is sent by AdServing Factory to Publisher to inform the Publisher that a payment is pending. Typically the Pending Payment is made within 7 days of email notification.
Estimated Revenue: Estimated Revenue is the revenue we have estimated that you have earnt from AUX. The reason why it is estimated is because there are sometimes differences between our programmatic sales records and the programmatic sales records of media buyers. Once we have confirmation of the agreed amount to be paid by all the media buyers for a given month we can then make this a Pending Payment. Unfortunately, some media buyers do not make a final confirmation for several weeks.
Open Balance: Open Balance refers to all estimated revenue owed to you over the 60-day billing cycle
You can view any Pending Payments and Estimated Revenue in the Revenue Dashboard.
Estimated Revenue for the current month is shown in the Revenue Dashboard (below). All revenue in the Revenue Dashboard is Estimated Revenue.
You can view any Pending Payments in the Revenue Dashboard, under the Revenue Schedule in the Revenue column.
All you past payments are listed under Received Payments on the Payments page of the AUX user interface.
In order to display the Payments page where the list of payments can be found please follow the below instruction:
All your past payments are listed under Received Payments on the right side of the Payments page as shown below.
Invoices can be downloaded from the list of Received Payments on the Payments page.
In order to download an invoice please follow the below instructions:
If you have a problem, you can easily create a Support Ticket to tell us about it. To raise a Support Ticket please follow these steps.
To submit it, please click Submit Ticket button
If you want to add more details, please click Add More Details button.
* If you selected to add more details, Ticket Detail Page will be open automatically.
If you want to add details to your ticket, you can do it on ticket detail page by clicking Add More Detail button when you are creating the ticket or you select the ticket from table in Support tab.
When you finish editing your ticket, please don’t forget to click Send button.
You can easily track all tickets created from your account in Support page. Also, you can filter items by their title, category, status, creation date, last update date and user name as well.
Cookiebot is a cookie and online tracking consent solution that complies with the consent and information requirements of the EU ePrivacy Directive 2009/136/EC and the General Data Protection Regulation (GDPR).
Cookiebot is a self-serve cloud service provided by the ePrivacy company Cybot.
Cookiebot follows the common guide on obtaining consent for cookies which applies to all EU Member States:
For more information about Cookiebot, please click here.