...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Intégration pubs sur les Apps iOS et Android
Google on mis à jour les kits d’intégration publicitaire pour les plateformes iOS et Android pour facilité et optimiser l’intégration publicitaire avec les apps mobiles.
Intégration des SDK de Google Doubleclick:
...
Liens pour l’intégration des bannières publicitaire avec Doubleclick
- Android : https://developers.google.com/mobile-ads-sdk/docs/dfp/android/quick-start
- iOS : https://developers.google.com/mobile-ads-sdk/docs/dfp/ios/quick-start
Liens pour l’intégration des vidéos publicitiaire avec Doubleclick
- Android : https://developers.google.com/interactive-media-ads/docs/sdks/android/v3/
- iOS : https://developers.google.com/interactive-media-ads/docs/sdks/ios/v3/
- Player en Flash : https://developers.google.com/interactive-media-ads/docs/sdks/flash/v3/
- Player en HTML5 : https://developers.google.com/interactive-media-ads/docs/sdks/html5/v3/
Point Important dans l’intégration bannières:
- Il est important d’intégrer les “Costum targeting” pour les bannières [Android] [iOS]
- Il est important d’intégrer les 2 formats possible pour les téléphones “Multiples ad sizes” (320x50 et 300x250) [Android] [iOS]
- Si disponible, il est important d’intégrer le géolocalisation [Android] [iOS]
- Il est imporant d’intégrer un interstitiel à l’ouverture de l’app. [Android] [iOS]
Point Important dans l’intégration vidéos:
- Il est important d’intégrer les “Costum targeting” pour les bannières [Android] [iOS]
- Il est important d’intégrer les formats companions si disponible pour les tablettes “CompanionAdSlot” () [Android] [iOS]
- Il est important de bien spécifier la langue dans le SDK vidéo pour “fr” [Android] [iOS]
- Il est important de configurer le click de redirection du vidéo en mod “willOpenInAppBrowser” [iOS]
- Pour Android, il est important d’intégrer le “Google Play service SDK” en plus du IMA SDK [Android]
Règle pour la création des Adunits:
Intégration Bannières :
Avec le SDK de Google :
La nouvelle intégration des pubs bannières avec le SDK de Google, nous donnera plusieurs nouvelles fonctionnalités dynamiques et beaucoup plus de contrôle et flexibilités pour la programmation des pubs.
Format de bannières à utiliser pour Android et iOS:
Tablette : 300x250 | 728x90 | interstitielle (Portrait 768x1024 | Paysage 1024x768) | 320x60
Téléphone : 320x50,300x250 | interstitielle (Portrait 320x480) | 320x60
Les pubs sont intégré dans les pages et non en catfish.
Le langage à utiliser : fr
Intégration Vidéo :
Avec le IMA SDK de Google :
La nouvelle intégration des pubs vidéos avec le IMA SDK de Google nous donnera plusieurs nouvelles fonctionnalités dynamiques et beaucoup plus de contrôle et flexibilités pour la diffusion des pubs.
Format vidéo à utiliser Android et iOS:
Tablette : 852x480
Téléphone : 852x480
Pub Compagnon à utiliser pour Andoid et iOS
Tablette : 728x90
Téléphone : Aucun
Le Mode d’opération du SDK est : Ad rules
Le langage à utiliser : fr
Feed MRSS id:
- Tou.tv : cmsid=823
- Radio-Canada.ca : cmsid=1303
Adunit ID pour les tests en DEV :
Vous devez absolument utiliser les adunit1 suivant pour tout vos tests. Ce adunit vous retournera des pubs tests sans en affecter la production.
- Aplication : Adunit1 = raca.dev.app.tou.tv
- Site web : Adunit1 = raca.dev.tou
Radio-Canada
- Aplication : Adunit1 = raca.dev.app.rc.ca
- Site web : Adunit1 = raca.dev
Plusieurs scénarios ont été créés pour voir si certaines fonctionnalités sont opérationnelles
Scénario1 (cap de fréquence de 1 au 5 minutes sur tous les pubs ‘bannière, vidéo, interstitielle’)
- Pub indiquant Cap de 1 au 5 minutes
Scénario2 (Géolocalisation sur tous les pubs ‘bannière, vidéo, interstitielle’)
- Pubs indiquant Geo-Montreal ou Geo-Toronto ou Geo-Québec ou Geo-autre villes
Liste des paramètres spécifique aux apps mobile Tou.tv et Radio-Canada.ca
Voici le tableau illustrant les paramètres à utiliser dans les appels vers le serveur publicitaire DFP Premium. La colonne « Param » indique le nom complet de la variable (keyvalue) et la colonne « Meta/Exemple » indique la provenance des valeurs possible à intégrer et/ou des exemples.
Param | Description | Meta/Exemple | Platforme | Custom/adunit |
|---|---|---|---|---|
rcsection | Nom de la section | rc.section | SRC & TOUTV | adunit |
rcgsection | Nom d’un groupe de sections | rc.groupesection | SRC & TOUTV | adunit |
rcsegment | Valeur du segment | rc.segment | SRC & TOUTV | adunit |
rcpagesegment | Valeur d’une page d’un segment | rc.pagesegment | SRC & TOUTV | adunit |
sEmi | Titre de l’émission | rc.emission | SRC & TOUTV | custom & adunit |
sSai | Numéro de la saison de l’épisode. | rc.saison | SRC & TOUTV | custom |
sEpi | Numéro de l’épisode | rc.episode | SRC & TOUTV | custom |
rccollection | Nom de la collection | rc.collection | TOUTV | custom |
rcliste | Valeur de la liste | rc.liste | TOUTV | custom & adunit |
ctype | Type de connection | Exemple (wifi, broadband, 3g, 4g, etc.) | SRC & TOUTV | custom |
position (bannière seulement) | Position de la bannière dans un “line-up” | Exemple {nom du lineup-numéro} (nouveaute-1) | SRC & TOUTV | custom |
lineup (bannière seulement) | lineup = (position du lineup)- (position de la pub dans le lineup) | Exemple (1-1, 1-2, 1-3, 2-1, 2-2, 2-3...) | TOUTV | custom |
rctelco | Nom du Telco | rc.telco | TOUTV | custom |
length (video seulement) | Duré du contenu en secondes | Exemple (222, 1245, etc.) | SRC & TOUTV | custom |
resume (video seulement) | indique si l’utilisateur est en resume | Exemple (true) | SRC & TOUTV | custom |
avdif (video seulement) | Vidéo en Direct ou Différé | Valeur fix pour tou.tv (differe) | SRC & TOUTV | custom |
styp (video seulement) | Type de source (vidéo ou audio) | Valeur fix pour tou.tv (video) | SRC & TOUTV | custom |
Questions et réponses
Voici la liste des questions posé lors de l’intégration des SDK Mobile, Apps et Flash
RESUME functions
Question about too how can we integrate RESUME functions on Flash player:
To disable showing video ad for the user who resume the content, you may use the “Manual ad break” functionality and disabling the automatic playback of Ad Breaks. Here is the link { https://developers.google.com/interactive-media-ads/docs/sdks/flash/v3/ads#manualAdBreaks }from the Developers console which helps you in implementing this function in SDK. You can float this doc to your developers and they will be able to help you in setting this up. You can disable the automatic playback of ad breaks to prevent the SDK from playing ad breaks until you want them to play. Please make sure that you let the SDK know when you’re ready for the ad break to play.
To give you a background about how this works: once the SDK has loaded an ad break, it will fire an AD_BREAK_READY event. When your player is ready for the ad break to start, you can invoke the adsManager.start() function.
Question about too how can we integrate RESUME functions on mobile Apps player:
Manual ad breaks aren’t currently supported in-app. My best recommendation now is to consult your Developers so that when a user leaves and comes back, the adsManager.stop() function is able to detect the activity. Here is a link from the Google { https://developers.google.com/interactive-media-ads/video_features_and_sdk_versions }Developers guide for reference.
Skip button HTML5
Question about the language in the HTML5 SDK IMA.
We have activate the skip ad button into our VAST, but, our content is in
french, so how can we receive the french label for the Skip ads button?
And into the other SDKs, I know we can add a specific language for video
ads from adsense, how can we enter this settings in the HTML5 SDK?
- In order to change the language for the skip label, you can use the setLocale() method like so:
- google.ima.settings.setLocale('fr');
- If you set it up correctly, you should see that the language of the skip button will change.
Integrate Mid-roll
We have problem to play video ads mid-roll in my video
call. I can see only pre-roll and post-roll, but, in my video contents, I
have set mid-roll ads. Can you explain how can we integrate mid-roll in our
SDK IMA for HTML5?
- I took a look at your ad tag and to ensure that midrolls work with Ad Rules, you'll also need to include two additional parameters. These parameters are "cmsid" and "vid." These are important because DFP needs to know the piece of content to understand the cue points and the duration of the content. Information on cmsid and vid: Content Targeting
- Example of modified tag:
- http://pubads.g.doubleclick.net/gampad/ads?sz=852x480&iu=/6642/raca.dev&ciu_szs=728x90&impl=s&gdfp_req=1&env=vp&output=xml_vast2&unviewed_position_start=1&url=http://ici.tou.tv&correlator=2343543235234&cust_params=duration%3Dvery-long&cmsid=823&vid=108548
- If you take the tag above and place it in your URL address bar and hit enter/return, you'll see that midrolls are present along with your prerolls and postrolls. If you need to refresh the page, you'll have to change the correlator value. The "vid" and "cmsid" are taken from the ids associated with your content source and video id in DFP
Timeout:
How can we manage the Timeout errors? Actually, when we have a
timeout, the SDK, do nothing and we need to close the apps and reload. Not
a good way.
- In terms of the Timeout errors, typically when an error is thrown, you'll be able to listen to the event. If you are listening to the event, you can then handle the event in the way you want. Are you currently listening for the timeout error event?
Language:
How can we change the language on the skip ads button
into the video ads? We want it in french. We use the language setting into
the apps and use FR but not working for the button.
- You can set the language for the skip ads button by using the setLanguage() method found in the ImaSdkSettings(). For Android:SetLanguage() For iOS: language
Countdown:
The downcounter for the ads, it is possible to have the
total pods countdown and not just for the unic ads? And it is possible to
activate or disable this option?
- If you are looking for the adpod information, you can use "getMaxDuration()" under AdPodInfo in order to get the time for the entire pod of ads. Example: AdPodInfo
No URL:
When we don't have any URL, it is possible to let know to
the video player, this ads is not clickable, and so, don't showing the
button for the redirections?
- For creatives without a clickthrough URL, the SDK does not have an inherent method to provide the functionality that you are looking for. You'll have to implement your own solution for this, which is custom and out of our scope of support.
Playing contents after ads played:
We get a problem with our integration of video ads. We are using the
IMA HTML5 SDK Version 3 for our HTML5 player.
The problem is, after all ads are finish to play, we need press again on
the play button to start playing the content.
We have check in documentation and we didn't find anything about this
problem.
- In terms of documentation, you may want to look into this: https://developers.google.com/interactive-media-ads/docs/sdks/html5/v3/ads#mobilevideo
- Basically, for certain environments such as iOS, the video elements must be click initiated. What that means is that if you only depend on CONTENT_RESUME_REQUESTED to resume your content, the content will not resume. You'll have to call load() when the user plays the video so that the video content is ready to resume once the ad has finished.