Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 58 Next »


Introduction

Adding Verve ad tags to your mobile application is quick and easy.

We support three kinds of integration

  • We offer an SDK for integration into your mobile apps
  • We offer server-side integration via an API
  • We offer javascript ad tags for integrating into Mobile WAP/Web sites.

SDK Integration

Talk to your publisher services representative for access to our SDK.

Server-Side Integration

Our AdCel API provides a server-side method of integrating with publishers.

Talk to your publisher services representative for provisioning of your production service on our API.

Mobile WAP/Web Integration

Mobile WAP/Web Integration is the simplest form of integration that Verve Wireless supports.

Verve has two kinds of tags that you may use for your integration.

The first is a simple call to a hosted javascript file. It looks like this:

<script>
vrv = document.vrv || {};
vrv.b = 'sampletag';
vrv.p = 'ptnr';
vrv.c = '999';
</script>
<script src="http://c.vrvm.com/pass/vrv/adtag/vervetag.js"></script>

For normal client-side integration, simply insert your Verve Ad Tag where you want your ad to appear.

In general, Verve prefers you to use the actual verve tag as opposed to the simplified Javascript wrapper tag because it will incrementally reduce latency of ad serving to host the tag directly on your page.

For a client-side integration using DFP Mobile, some minor changes should be made.

Required parameters

There are three parameters that are required in every tag.

Parameter

Name

Description

p

Portal keyword

Portal keyword. This is a Verve-assigned value identifying the distribution portal on which the advertisement is being displayed. In most cases, a mobile website accessed directly using the publisher's hostname is on the default portal (keyword: "def"). The portal will change if the site is accessed through a mobile carrier's "deck". Mobile client applications are typically segregated by platform (e.g., iPhone, BlackBerry, Windows Mobile, etc.) using portals.

b

Partner (publisher) keyword.

This is a Verve-assigned value identifying the publisher of the mobile content. Note that there's a one-to-one relationship between a mobile site and a publisher. For example, for the Daily Planet's mobile site, the partner keyword might be "dailyplanet".

c

Content Category

Content category ID. This is an integer which identifies the type of content available on the page for which an ad is requested. For example, a page of sports news will have one category ID, while a page of movie reviews will have another.

If you set the "category" variable to a value in our Ad Category Codes this provides us with metadata about the content type for the impression that allows us to serve higher value ad inventory. A list of acceptable category values can be found in the AdCel API.

Optional Parameters

If your application/platform captures accurate location or advertiser ids, passing this data on the request can greatly increase the monetization of your inventory. Simply insert the parameters you wish to pass in the request in your ad tag as show below. Your account manager will create a custom tag for your specific integration. For a list of additional available parameters, read more here: AdCel API.

Here are the most valued parameters:

  • Lat and long parameters should be sent as decimal values. For example, lat: 40.759110, long: -73.985163 resolves to Time Square New York city. 
  • ui advertiser id includes idfa, google id, or android id.  
  • uis advertiser id source specifies the id type you are passing. Refer to this section to understand the uis mapping: User Identifier Guidance. If you cannot properly set a uis value, please talk with your account manager for alternate ways to pass this data.
  • hwmdl is the hardware model of the user's device. This information is only exposed to applications. For example a hardware model of 'A1432' refers to the iPad mini, first generation.
<script>
vrv = document.vrv || {};
vrv.b = 'sampletag';
vrv.p = 'ptnr';
vrv.c = '999';
vrv.lat = '<INSERT_LATITUDE_HERE>';
vrv.long = '<INSERT_LONGITUDE_HERE>';
vrv.ui = '<INSERT_ADVERTISER_IDENTIFIER>';
vrv.uis = '<INSERT_ADVERTISER_IDENTIFIER_SOURCE>';
vrv.hwmdl = '<INSERT_HARDWARE_MODEL>';
</script>
<script src="http://c.vrvm.com/pass/vrv/adtag/vervetag.js"></script>

Testing and Certification

Testing and certification involves a combination of validating on mobile web and app as well as various flavors of interstitials and video formats.

MMA

To create a tag that returns a banner every time, the following values should be used:

  • b=sampletag
  • p=ptnr
  • c=999

By changing the category ("c") to "888", you will get a Celtra rich media banner rather than a static image. Using this, you can test a wide range of possible Verve responses.

iPad tests are also supported. To test the ipad use the following values:

  • b=sampletag
  • p=ipad
  • c=999
  • adunit=728x90 or 300x250 (depending on the ad size you would prefer returned)

There are currently no rich media banners available for iPad testing.

Expandable

Please validate that your supports our expandable format for both mobile web and app below:

Mobile Web

<script>
vrv = document.vrv || {};
vrv.b = 'sampletag';
vrv.p = 'ptnr';
vrv.c = '97';
</script> 
<script src="http://c.vrvm.com/pass/vrv/adtag/vervetag.js"></script>

APP-for both iPhone and Android apps

<script>
vrv = document.vrv || {};
vrv.b = 'sampletag';
vrv.p = 'iphn';
vrv.c = '97';
</script>
<script src="http://c.vrvm.com/pass/vrv/adtag/vervetag.js"></script>

The expandable looks like this:

 

In banner/line video for iOS apps

iOS supports playing inline video via the "allowsInlineMediaPlayback" to be set in app. Please certify if your iOS (iPhone and iPad) apps can run this creative type.

  1. Requires allowsInlineMediaPlayback to be set in app
  2. Use this test tag to be loaded in app:
<script>
vrv = document.vrv || {};
vrv.b = 'sampletag';
vrv.p = 'iphn';
vrv.c = '22';
</script>
<script src="http://c.vrvm.com/pass/vrv/adtag/vervetag.js"></script> 

Screen shots of video playing in an expanded panel:

 

Specifications:

  1. In line banner/interstitial
    1. Auto play: Yes
    2. Duration: 5-10 seconds
    3. Audio: No
  2. Expanded panel (requires user to tap on initial banner to open)
    1. Auto play: Yes
    2. Duration: 15 to 30 recommended. 
    3. Audio: Yes
  3. Example preview without using an app: http://www.vervemobile.com/test/inbannervideo/
    1. If your browser doesn't support the mime type try another browser or install the appropriate plugin for your browser.
    2. If viewing on a mobile device, this will not auto play.

Interstitial

Full Screen Interstitial

This is a test full screen static interstitial tag for mobile web. The black border will soak up all remaining space on the page. If you don't want a full screen interstitial, please take a look at the dedicated 300x250 interstitial. As a publisher, you will need to control how many interstitials you will request.

<script>
vrv = document.vrv || {};
vrv.b = 'sampletag';
vrv.p = 'iphn';
vrv.c = '999';
vrv.adunit = 'inter';
vrv.size = '320x416';
</script>
<script src="http://c.vrvm.com/pass/vrv/adtag/vervetag.js"></script>

 

The interstitial will look like this:The tag returns a javascript response similar to this: JS_Response.txt

300x250 Interstitial

Use this test tag when your inventory is running a specific 300x250 ad size.

<script>
vrv = document.vrv || {};
vrv.b = 'sampletag';
vrv.p = 'iphn';
vrv.c = '999';
vrv.adunit = 'inter';
vrv.size = '300x250';
</script>
<script src="http://c.vrvm.com/pass/vrv/adtag/vervetag.js"></script>

 

This will request will return a js response as well: JS_Response_300x250.txt

A 300x250 image will display without an expanding border that covers the full screen of the device:

Ad Formats and Size

MMA

The Verve Ad Tag will automatically sense the device requesting a page and serve an appropriately sized advertisement. Generally, Verve Ad Tags comply closely with MMA specifications and come in the following sizes:

  • 320x50
  • 300x50
  • 216x36

The supported formats are .jpg, .gif, and .png.

Caching

No caching of ads is allowed under any circumstances.

Interstitial Inventory

If you wish to display interstitial ads or have interstitial units today and would like Verve to show interstitial ads into it, please speak with your publisher services representative.

Passbacks

By default, if there was no ad available for the request, a zero-byte HTTP 200 response will be returned. Here is a sample of the headers:

Server: Apache-Coyote/1.1
Content-Type: text/plain
Transfer-Encoding: chunked
Date: Wed, 24 Sep 2008 20:44:40 GMT
200 OK

If you have a roll-over tag that you would prefer us to use, give that tag to your Verve publisher services representative and Verve will integrate that on your behalf. Verve works with many third party advertising networks - please make sure you let your Verve publisher services representative know whether you would like the benefit of these advertising partners looking at inventory before we pass the ad back to you. Adding Verve ad tags to your mobile application is quick and easy.

  • No labels