| Macro | Description | Example Value | Applicable For |
|---|---|---|---|
| {timestamp} | A decimal string, based on the current timestamp (in seconds and microseconds in the UNIX epoch). | 11999990.77 |
|
| {random} | A 10 character alpha-numeric random string value. | babcdefe72 |
|
| {clickurl} |
|
<a href="{clickurl}http://atti.velti.com/is/fb/434262/web.htm?random={timestamp}" target="new"><img src="http://atti.velti.com/wbrs/inject2?cid=434262&random={timestamp}"/></a> See details below |
|
| {bannerid} |
|
1234567 |
|
| {campaignid} |
|
1234567 |
|
| {site_id} |
|
9999 |
|
| {partner_id} |
|
8c9fa541f3a5a0c5 |
|
| {width} | Provides the width of the banner image served. | 320 |
|
| {height} | Provides the height of the banner image served. | 50 |
|
| {format} |
|
iphone, OR android, OR wap |
|
| {ip2lat} |
|
18.5333 |
|
| {ip2long} |
|
73.8667 |
|
| {ip2zip} |
|
411045 |
|
| {TARGET_xxx} where xxx is the custom target parameter name |
|
The value is exactly as sent by the app |
|
| Macro | Description | Example Value | Applicable For |
|---|---|---|---|
| {numeric_sdk_version} |
|
269 |
|
| {adtype} |
|
banner OR interstitial |
|
| {device_connection} | For iPhone client SDK implementation, returns the network connection type-wifi or cellular. | wifi OR cellular |
|
You can search multiple creatives by entering creative id's comma separated. Maximum limit is 100.
The Private Auction Checkbox lets users define how restrictive the terms of a Deal ID are for each bidder it applies to.
When checked, it implies bid responses from a bidder will be accepted only if they conform to the bid requirements defined by the respective Deal ID that the private auction is associated with. Else, that bidder's response is rejected.
When unchecked, it means bid responses from that bidder will be accepted even if they don't conform to the bid requirements defined by the Deal ID associated with that private auction.
To see Comparision chart user has to click the checkbox and click on GO button.
By default the dates of previous trend will be loaded based on the start and end dates of current trend. whenever user changes them the previous dates will be recalculated.
Please ensure that the date difference of previous trend should be same as current trend.
Filters created will be visble in all the views where they can be supported.
Please update and save the already created filters to make them visible in all the views where they can be supported.
ALL : Use "ALL" to apply tech fee for all agencies/countries/domains without any breakdown.
ROTA : Use "ROTA(Rest of the Agencies)" to apply tech fee for agencies other than those for which tech fee is exclusively configured
ROTW : Use "ROTW(Rest of the World)" to apply tech fee for countries other than those for which tech fee is exclusively configured.
ROTD : Use "ROTD(Rest of the Domains)" to apply tech fee for domains other than those for which tech fee is exclusively configured.
A Seat ID is a unique identifier that helps target specific buyers that reside on a bidding platform. These need to be specified within the Exchange, DSP or ATD when targeting these buyers. The Deal ID will be sent only to the specific seats for a bidder.
A Deal ID is a unique identifier that defines a set of special terms - such as a specific bid floor price - between a seller and one or more bidders. Creating a Deal ID is similar to creating a private auction, but the Deal ID must be linked to one or more auctions.
The Deal ID is a unique identifier that defines a set of special terms, such as a different bid floor price, between a seller and more or more bidders. Creating a Deal ID is similar to creating a private auction, but the Deal ID must be linked to one or more auctions.
The application bundle identifier (BundleID) is a unique ID for your application and is a value set by application developers. It is represented in reverse DNS notation and is CASE SENSITIVE. Make sure you enter this exactly as in your application.
To obtain the correct bundleID, request it from the advertiser's application developers. For android, this is the same as Package name used by developers in the project. For iOS, this is also set in the application process and can also be found in iTunes Connect under: Manage apps, <app name>, in the Identifiers section, labeled as Bundle ID. An example BundleID is: com.mdnewsnow.ipad
Select the required site status. Disabling a site removes it from the Edit Linked Sites list, but is included in all applicable reports.Thus, all campaigns linked to the disabled site are automatically delinked.
Test sites shouldn't have any production traffic if selected.
In case you select Test sites, ensure that they don't have any production traffic.
A passback site serves as a bucket to capture all impressions coming from the lower priority banners for a given site. This is done to only include the non-passback sites in the calculations of the fill rate, impressions, eCPM, and the revenue values in the summary information in the Home tab at the top of the page, since including both passback and non-passback sites can delude these figures.
If you do NOT want this separation to happen in the Home tab, do NOT check this option for any of your sites. Otherwise, check this box only for your sites designated as passback.
A passback site serves as a bucket to capture all impressions coming from the lower priority banners for a given site. This is done to only include the non-passback sites in the calculations of the fill rate, impressions, eCPM, and the revenue values in the summary information in the Home tab at the top of the page, since including both passback and non-passback sites can delude these figures.
Check the Enable box if you wish to link this banner to a passback site. Use the dropdown menu to find and select a passback site to link it to. Only sites marked as passback will be shown in the dropdown.
Auto Expand flag works in tandem with the Overlay flag.Enabling the Overlay flag would also enable the Auto Expand flag.This is the default behaviour, user may choose to override it by only disabling the Overlay Ad flag.
Enter a relevant site name. A good name can be to combine the publisher name with the device type, banner size, application section, creative type, operating system, and platform.
For example:
[PUBLISHER][DEVICE][SIZE][APP SECTION][CREATIVE TYPE][OS][PLATFORM] = [TestPub][Smartphone][Banner][Home][Standard][iOS][App]= TestPub_SMT_BNR_HM_STD_iOS_APP
Note: To delete a site, contact adsupport@admarvel.com
Select all the ad sizes supported by the specified site.
Note:
Selecting the ad display(s) permitted allows us to identify the way you envision your banner to be executed on the site.
Banners may be executed as an image, expandable, interstitial, interstitial with leave behind...etc. Even if your site is an iPhone app, you can specify if retina ads are allowed.
The summary of all this information will be helpful when you group or categorize your sites.
To maximize an ad campaign performance, select the business verticals that best represent the site's audience.
The Blocked Ad Category Profile option provides pre-defined profiles of blocklist categories, so that when an option is selected, a certain set of blocklist categories are automatically selected.
To update what categories get selected for each profile, please contact AdMarvel support.
Select the relevant target audience groups of the site.
Select the relevant target audience groups of the campaign.
The Admarvel platform supports 3rd party Pixel tracking at campaign level. Publishers can enter a url in the Admarvel UI from a 3rd party and Admarvel will fire a pixel to the 3rd party URL when an ad is rendered. With this method the 3rd party's impression count should closely match the impression count available in the Admarvel UI.
The Admarvel platform supports 3rd party Pixel tracking at the campaign and banner level. Publishers can enter a url in the Admarvel UI from a 3rd party and Admarvel will fire a pixel to the 3rd party URL when an ad is rendered. With this method the 3rd party’s impression count should closely match the impression count available in the Admarvel UI.
This is your internal ID (optional).
Link the site to existing site groups, if applicable.
The "Default RTB Site Settings" configuration defines both the Bid Floor Setting and the Bidder
Blocklist Settings for any site that is missing both of these pieces of information AND is not
linked to any inventory.
Keep in mind that the sites will reflect the Bid Floor Setting and Bidder Blocklist Settings of Inventory
thay are linked to. However , you can still override an inventory's individual values for each site by
going to the Edit Site page for a particular site.
By selecting a targeting template, a previously saved targeting configuration can be reused.
Prefix is a unique key used to associate a provider to the enrichment parameter.
All the Standard AdMarvel macros are also supported in Custom parameter value.
But, instead of enclosing macros in curly brackets, enclose them in @@.
For example, use macro @@random@@ instead of {random}.
if Max Supply Price by Country not defined then global Max Supply Price will overide.
You can add QPS by publisher. The sum of publisher QPS should be less than or equal to Global QPS value.
Warning:Selecting this option will automatically override the existing prices for this Inventory Property with the default prices.You won't be able to recover the previous price settings after this change.Please contact an administrator to change the default pricing.
Click OK if you want to proceed with using default prices.Click CANCEL to exit without making changes.
Supports banner delivery to Android applications using the AdMarvel SDK.
Supports banner delivery to Android applications using the AdMarvel SDK.
Suitable for non-standard banner sizes. Note: AdMarvel does not automatically detect and target compatible devices.
An HTML-based banner uses basic creatives and tags. For example: ATLAS, DFA, or a custom tag.
Native advertising refers to ads that have been adapted to look and behave like the site or application where it resides, as a means to improve the performance of the ad.
A small file size is recommended (less than 1MB) for an SDK interstitial video banner, so that it can load quickly even with slow connection speeds.
Video formats allowed are H.264 and MP4.
iOS Retina banners target iOS devices that support retina displays.
The viewable size is 320x50 (actual size is 640x100 for the SDK version).For Mobile Web the viewable size is 300x50 (actual size is 600x100).
Note: AdMarvel does not automatically detect and target compatible devices.
Make sure to select the correct Banner Subtype.
For uploading banners from Medialets when using the AdMarvel SDK to deliver the ads. The important fields that need to be defined here is the Medialets App ID, which usually would come from a Medialets contact that worked on the apps and SDK integration. The Ad Id is the unique name/banner that lives in the Medialets ad server infrastructure.
Ideal when multiple creatives are available and resolution targeting is available.
MMA Standard Image Banner:
Ideal when multiple creatives are available and resolution targeting is available.
Recommended for use when targeting devices ranging from feature phones to medium range smart phones.
MMA Extended Image Banner:
Ideal when multiple creatives are available and resolution targeting is available.
Recommended for use when targeting devices ranging from feature phones to high end smart phones.
Supports banner delivery to Android applications using the AdMarvel SDK.
At a user's discretion, an advertiser can append the SMS sent by that user with a text ad, provided the total message is not more than 160 characters.
A text banner that requires the text to be displayed as a banner.
VAST stands for Video Ad Serving Template. It's the IAB's standardized format for tracking video ads.
VAST provides a standard XML-based ad response for in-stream video for on-demand video players where the ad response is parsed prior to play.
Any Targeting options selected here will be applied to any traffic associated with this Deal ID, and will override any targeting options set for the banner or campaign associated with this traffic.For example,if you target a Deal ID to the United States Location,and apply this Deal ID to a live banner,then bidders will receive bid requests with this Deal ID when the ad requests are coming from devices in the United States.
Standard Banner: To be used when only 3 images are available (Large, Medium, Small)
Extended Banner: To be used when 4 images are available (XL, Large, Medium, Small)
Video Ad Formats
Video ads fall into three large categories:
- Linear ads
- Non-linear ads
- Companion ads
AdMarvel supports linear ads.
Linear ads appear before, after, or during a break in the video content (otherwise known as pre-roll, post-roll, or mid-roll).
Video Ads Tracking
Tracking Impressions: Unlike display ads, where an impression is counted once the ad is requested, video ad impressions aren't counted until the video ad starts playing. Counting the video ad impression later ensures a more accurate impression count in the event that the user navigates away from the page due to a slow connection speed, a change in interest, or other reasons.
Tracking Events: The Internet Advertising Bureau (IAB) defines a number of tracking events that must be fired as video ads are played. Admarvel will classify VAST videos based on tracking events:
- Simple: It's a linear ad compatible with all iOS and Android SDK versions
- Advanced: It's a linear ad compatible with all iOS and Android SDK versions Greater or Equal to 2.3
- Pass Through: It's a linear ad compatible with all iOS and Android SDK Version. This VAST subtype is exclusive for AdMarvel partners (video AdNetworks). Nothing in the video can be customized. Only the Video URL is required.
See below the tracking events per VAST video subtype supported by AdMarvel
| Tracking Event | Description | Simple | Advanced | Pass Through |
|---|---|---|---|---|
| Start | Number of impressions where the video was played. Event is logged once per view. If a user stops play and restarts it, the restart isn't counted. | Yes | Yes | No |
| Midpoint | Number of times the video reached its midpoint during play. Event is logged once per view. For example, if a user watches 20 seconds of a 30-second ad clip, then restarts the clip and watches it to completion, the event is counted once. However, if a user watches 10 seconds of a 30-second ad clip, then stops and exits, no midpoint event is counted. | No | Yes | No |
| Third Quartile | Number of times the video played to 75% of its length. | No | Yes | |
| Complete | Number of times the video played to completion. Event is logged once per view. If a user restarts the clip, it's not counted again. For example, if user plays 30-second clip for full 30 seconds, event is logged. If user replays clip full 30 seconds, event isn't logged again. If, however, user plays 20 seconds of clip then stops and exits clip, no event is logged. | No | Yes | No |
| Pause | Number of times user paused ad clip. Event logged once per view. If user repeatedly starts and pauses ad clip, it's not counted again. | No | Yes | No |
| Resume | Number of times the user unpaused the video. | No | Yes | No |
| Mute | Number of times video player was in Mute state during play of ad clip. If player is muted before ad plays, it's counted the same as if user mutes player while ad plays. Event is logged once per view. If user mutes ad clip multiple times during play of ad, it isn't counted again. | No | Yes | No |
Campaign wrap up reports are reports created after a campaign ends that summarize the performance of the campaign. These reports cover the entire length of the campaign and segment the information by impressions and unique users for the following categories:
AMO is Admarvel's automatic revenue optimizer for mediated networks. By checking a traffic zone for AMO, the system will show the adnetwoks eligible for AMO. AdMarvel will automatically perform the mediation process for all the adnetworks checked for AMO. Uncheck AMO to perform a manual mediation.
These are the possible Enable AMO values:
AMO percentages get calculated automatically by the system based on the algorithm used to realize the best yield for the ad request.
Non AMO percentages get calculated by the system based on the ad network allocation weight, entered by the user.
This category is used to specify the placement dimensions. The significance of the selection is more about size type (dimension aspect ratio) rather than specific pixel dimensions. Multiple sizes (more than one at a time) may be selected concurrently.
Specifies the way the banner is going to be executed. Multiple execution types (more than one at a time) may be selected concurrently.
The following macros can be used
| Macro | Description | Example Value |
|---|---|---|
| {timestamp} | A decimal string, based on the current timestamp (in seconds and microseconds in the UNIX epoch). | 11999990.77 |
| {random} | A 10 character alpha-numeric random string value. | babcdefe72 |
| {PHONE_HEADER_USER_AGENT} | User Agent. | Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_0_1 like Mac OS X; en-us) AppleWebKit/532.9 (KHTML, like Gecko) Version/4.0.5 Mobile/8A306 Safari/6531.22.7 |
| {PHONE_HEADER_REMOTE_ADDR} | IP Address. | 174.252.6.52 |
| {TARGET_AGE} | The custom target parameter passed for AGE. | 21 |
| {TARGET_GENDER} | The custom target parameter passed for GENDER. | F |
| {TARGET_UNIQUE_ID} | Mandatory target param-device unique ID. | 1bef50453858d31 7a5471087aaf1614a |
| {site_id} |
|
9999 |
First look is a means of giving specific bidder preferential treatment for a particular auction.
When the bidder responds with a Deal ID, as long as they respect the terms of their Deal Id, they will always win the bid, even if they are not the highest bidder in their auction.
If they don't respond to the bid request, then the system will pick from the remaining bid responses.
Because First look bidders are guaranteed to win the auction if they bid, First look bidders always use First Aucton Type.
First look is a means of giving specific bidder preferential treatment for a particular auction.
When the bidder responds, as long as they respect the terms, they will always win the bid, even if they are not the highest bidder in their auction.
If they don't respond to the bid request, then the system will pick from the remaining bid responses.
Because First look bidders are guaranteed to win the auction if they bid, First look bidders always use First Aucton Type.