Connected-Stories Ad Tag is an HTML5 file (or a short JavaScript code) used to serve ad units to publishers' digital properties. Once the ad unit is loaded on client page, Connected-Stories can start to collect data and forward the most-appropriate content to the users, depending on their state and behavior.

Ad tags are automatically generated in the backend system and can be distributed through any ad server. In the case of using Doubleclick For Publishers, Ad Tags can be uploaded and scheduled in a campaign line item.

When an Ad Tag is rendered on the page as an impression, it communicates back to the Connected-Stories cloud to determine user's state within the customer journey workflow, based on user data and/or user interactions.

Connected-Stories units work in Full-Redirect. This means that the ad server that is trafficking Connected-Stories units support CSS, JS, and AJAX calls to external servers. This is particularly important when putting together your media plan for your next campaign since some key Connected-Stories features might not be working as planned.

Table of Contents

SUPPORTED AD TAGS TYPE:

Html5 Package
JavaScript
VAST / VPAID url
MRAID
Click Tracker and Impression Pixel
3rd Party Trackings

HTML5 PACKAGE

Zip file that contains the minimum resources to load an Ad Unit, mainly HTML5 files and assets.

Supplementary assets and dynamic functions are loaded directly from the Connected-Stories cloud.

This type of Ad Tag can be used to deliver a standard iAB unit.

JAVASCRIPT TAG

This Ad Tag provides a higher level of interaction on the Ad Unit, for example an Expandable Unit.

It can be delivered with DFP macros for tracking capabilities.

VAST / VPAID URL

VAST and VPAID are standard iAB protocols used to deliver an Ad Unit on compliant Video Player.

Connected-Stories with a VAST url can deliver a simple preroll/midroll/postroll on the target video player.

Further, with a VPAID url, Connected-Stories can deliver rich content with interaction.

MRAID

MRAID, or “Mobile Rich Media Ad Interface Definitions,” is the common API (Application Programming Interface) for mobile rich media ads that will run in mobile apps.

This is a standardized set of commands, designed to work with HTML5 and JavaScript, that developers creating rich media ads use to communicate what those ads do (expand, resize, get access to device functionalities such as the accelerometer, etc.) with the apps into which they are being served.

Below a sample of a code generated by Connected-Stories for a JavaScript Ad Tag:

Connected Stories JS Ad Tag

<script id="htv_unit_exp" src="https://connected-stories.hypertvx.com/app/iol/formati/fif_loader.js?cb=%%CACHEBUSTER%%&cuu=$$%%CLICK_URL_UNESC%%$$">>
<noscript>
<a href="%%CLICK_URL_UNESC%%http://connected-stories.hypertvx.com/target.html" target="_blank"><img src="https://connected-stories.hypertvx.com/app/iol/formati/collapsed_image.jpg" border=0 width=970 height=60></a>
</noscript>

CLICK & IMPRESSION TRACKING

When full redirect is not supported by the publisher, tracking pixel and click command tags can be associated to a format hosted on the publisher's servers and trafficked directly through them.

This way you can get a full picture of your campaign even if they are not Connected-Stories formats.

Below a sample of a code generated by Connected-Stories for tracking pixel and click command:

3RD PARTY TRACKING

To provide full transparency to clients, Connected-Stories allows 3rd party external tracking to be associated with each format trafficked. That provides an extra layer of data stored directly on the client's databases in addition to the ones provided by Connected-Stories analytics.

Below an example of both click command and tracking pixels. Click commands are placed as click through url since they already contain the landing page within the code.

Ad Trafficking