This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
creatives:html-en [2015/10/07 16:39] avarga [Restrictions regarding HTML banners (HTML/XHTML/HTML5 codes)] |
creatives:html-en [2016/06/06 16:47] dczipperer |
||
---|---|---|---|
Line 72: | Line 72: | ||
<code html> | <code html> | ||
- | <link type=”text/ | + | <link type=”text/ |
</ | </ | ||
Line 78: | Line 78: | ||
<code html> | <code html> | ||
- | <div style=”background: | + | <div style=”background: |
</ | </ | ||
Line 115: | Line 115: | ||
<code html> | <code html> | ||
- | <a id=" | + | <a id=" |
</ | </ | ||
Line 181: | Line 181: | ||
<code html> | <code html> | ||
- | <img alt=”” src=”[fáljnév.kiterjesztés]”></ | + | <img alt=”” src=”[file:file.name]”></ |
</ | </ | ||
Line 440: | Line 440: | ||
goAdverticum3.getZone([zone]).measure.play.fire(); | goAdverticum3.getZone([zone]).measure.play.fire(); | ||
</ | </ | ||
+ | |||
+ | ==== Time measure ==== | ||
+ | |||
+ | With the time measurement we can measure the time between a start and a stop event. This works similar to a stopwatch. If a measurement is in progress and the system gets a ’start’ command, it stops and sends the previous measurement and starts a new one. Basically it happens as we would have called the ’stop’ function and then immediately the ’start’. | ||
+ | |||
+ | ==Limits:== | ||
+ | * Maximum number of fire | ||
+ | * Minimum measurable time | ||
+ | * Maximum measurable time | ||
+ | |||
+ | === In case of HTML banner=== | ||
+ | In the example we measure the time when the banner is opened. We use the ’openTime’ measure for this. | ||
+ | Start of the time measure: | ||
+ | <code javascript> | ||
+ | // We send a message to the top window running Goa3, then indicate | ||
+ | // the calling measure | ||
+ | window.top.postMessage(' | ||
+ | </ | ||
+ | |||
+ | Finish of the time measure: | ||
+ | |||
+ | <code javascript> | ||
+ | // We send a message to the top window running Goa3, then indicate | ||
+ | // the calling measure | ||
+ | window.top.postMessage(' | ||
+ | </ | ||
+ | |||
+ | === In case of markup banner === | ||
+ | |||
+ | In our example the structure of the time measure called ’openTime’ is available in the following form after requesting the zone data. | ||
+ | |||
+ | <code javascript> | ||
+ | |||
+ | { | ||
+ | 0000000: { // The zone ID is the key and the zone has a content. | ||
+ | |||
+ | displayed: {Boolean}, | ||
+ | ... | ||
+ | node: {Object}, | ||
+ | |||
+ | measures: { | ||
+ | openTime: { | ||
+ | start: function () {...}, | ||
+ | stop: function () {...}, | ||
+ | } | ||
+ | } | ||
+ | } | ||
+ | } | ||
+ | </ | ||
+ | |||
+ | In the example we measure the time when the banner is opened. We use the ’openTime’ measure for this. | ||
+ | Start of the time measure: | ||
+ | <code javascript> | ||
+ | // Starting the time measure. | ||
+ | goAdverticum3.getZone([zone]).measure.openTime.start(); | ||
+ | </ | ||
+ | |||
+ | Finish of the time measure: | ||
+ | |||
+ | <code javascript> | ||
+ | // Stopping the time measure. | ||
+ | goAdverticum3.getZone([zone]).measure.openTime.stop(); | ||
+ | </ | ||
+ | ==== Volume measure ==== | ||
+ | |||
+ | Using the volume measure allows us to send aggregated results to the system. In contrast to the simple measure we can send a number as the parameter of the function which will be transformed into a positiv integer (int) by the system. | ||
+ | |||
+ | ==Limits:== | ||
+ | * Maximum number of fire | ||
+ | * Minimum measurable time | ||
+ | * Maximum measurable time | ||
+ | |||
+ | === In case of HTML banner=== | ||
+ | In the example we measure the result of a bubble fire game. We use the measure called ’bubbles’ for this. | ||
+ | <code javascript> | ||
+ | // We send a message to the top window running Goa3, then indicate | ||
+ | // the firing event and the value in the brackets. | ||
+ | window.top.postMessage(' | ||
+ | </ | ||
+ | |||
+ | |||
+ | === In case of markup banner === | ||
+ | |||
+ | In our example the structure of the volume measure called ’bubbles’ is available in the following form after requesting the zone data. | ||
+ | |||
+ | <code javascript> | ||
+ | |||
+ | { | ||
+ | 0000000: { // The zone ID is the key and the zone has a content. | ||
+ | |||
+ | displayed: {Boolean}, | ||
+ | ... | ||
+ | node: {Object}, | ||
+ | |||
+ | measures: { | ||
+ | bubbles: { | ||
+ | fire: function ( value ) {...} | ||
+ | } | ||
+ | } | ||
+ | } | ||
+ | } | ||
+ | </ | ||
+ | |||
+ | In the example we measure the result of a bubble fire game. We use the measuring called ’bubbles’ for this. | ||
+ | |||
+ | <code javascript> | ||
+ | // We simply fire the event. | ||
+ | goAdverticum3.getZone([zone]).measure.bubbles.fire(5); | ||
+ | </ | ||
+ | |||
---- | ---- |