IMA HTML5 SDK: setting contentTitle, contentDuration and contentKeywords

[Mikko Koponen]

Hi,

I'm trying to figure out how to improve AdExchange fill rate by setting contentTitle, contentDuration and contentKeywords in the HTML5 IMA SDK.

To try this out, I added these parameters to the adsRequest here https://github.com/googleads/googleads-ima-html5/blob/master/simple/ads.js#L48. However, I can see no relevant changes in the VAST request or the integrator.js request when I set these, so are they passed through some other channel to AdManager? How do I go about determining if my setup is working as expected?

The reason i want to verify this is that in production I'm using videojs-ima, and the only reference to these properties in any of their documentation is in this issue: https://github.com/googleads/videojs-ima/issues/710. Looking at the source (https://github.com/googleads/videojs-ima/blob/master/src/sdk-impl.js#L240), it seems to me that the way suggested in the issue to set these parameters would be too late, since requestAds has already been called before the "ads-request"-event fires. 

Can you help me find the proper way of setting these parameters?

Thanks,

Mikko

[IMA SDK]

Hi Mikko,

An example of a correct way to add parameters to an adsRequest is in our Sample apps in Advanced - > Ads.js in requestAds function, currently at line 41. You can add contentTitle, contentDuration and contentKeywords there. If you cannot see the difference after modifying a sample app,  could you send the modified sample app project via "Reply to author"?

Regards,

Aryeh Baker IMA SDK Team

ref:_00D1U1174p._5004Q28oFEO:ref

[Mikko Koponen]

I added what I assume would be the required lines into the advanced example: 

https://github.com/mtkopone/googleads-ima-html5/blob/master/advanced/ads.js#L43

I still see none of the values in the https://securepubads.g.doubleclick.net/gampad/ads request. Or any encoded/encrypted parameters that would have gotten added when adding those properties to the adsRequest. Or any relevant changes in any of the multiple other requests that the advanced example makes. 

Please find the modified repo here: https://github.com/mtkopone/googleads-ima-html5

Regards,

  Mikko

[IMA SDK]

Hi Mikko,

Thank you for the modifications, I added that to my sample app and didn't see anything different in the ad tag sent when I used the sample ad tag. Do you have an Adx ad tag to test with? If so, could you send it via "Reply to author"?

[Mikko Koponen]

We only have AdX enabled on in our production environment, and I haven't found a way to create a test ad tag for it.

In our production environment the AdX line item participates in all ad requests. I have tested adding these parameters to the adRequest in our production codebase, and it also didn't change the ad tag sent in any way. I'm assuming *something* should get sent in the adRequest if those parameters are set.... 

So is it now a misconfiguration in my code or a problem in the IMA library? 

Or can AdX somehow access those parameters in some other way in the client? Am I looking in the wrong place by assuming it would add them to the VAST tag url? If they should be in the URL, why aren't they documented in https://support.google.com/admanager/table/9749596?hl=en so could encode them as part of the adTagUrl-parameter?

Regards,

  Mikko

[IMA SDK]

Hi Mikko,

I’m with Aryeh’s team so let me assist you here. How about adding key-value pairs into your ad tag to add parameters via cust_params keyword (more information here)? Let me know if you can use this.

However, it would be great if you could share with us a sample AdX ad tag for our test reference regarding the AdRequest content parameters.


Regards,

Sherwin Diesta IMA SDK Team

ref:_00D1U1174p._5004Q28oFEO:ref

[Mikko Koponen]

I can of course add anything into the cust_params, but i have no idea if that's the right place so AdX would pick them up, or if it is the right place then what does AdX assume that the key-names for those are, or how e.g. the contentKeywords array should be encoded into the cust_params...

As I said, only our production environment is set up with AdX-integration, so I really don't know of any way to get a sample tag that would have AdX enabled.

Cheers,

  Mikko  

[IMA SDK]

Hi Mikko,

It appears that you need support for Ad tag testing which is out of scope of this forum before testing the SDK. We don't have test tags for Adx inventory and when processing Adx inventory the SDK may send requests differently. To set up test ad tags you can get support in the Ad Manager Forum. I saw an article there about testing. When you have an ad tag that you can send to us privately, via "Reply to author", could you send it to us?

Regards,

Aryeh Baker IMA SDK Team

ref:_00D1U1174p._5004Q28oFEO:ref

[Mikko Koponen]

I have a working site running ads from both AdX and non-programmatic line-items. I have all the possible testing setup, and I've read through all of the AdManager forum troubleshooting instructions. All I wanted to know is how these parameters are supposed to propagate to AdX because I had concerns that they wouldn't.

I could senf you the ad tag that we use in production, which does serve AdX demand when it's used on a site hosted in a domain that has a valid ads.txt that AdManager has crawled and verified and matches the url parameter in the tag. But the "Reply to author"-button is dimmed even though I just set up my browser to handle mailto-links. So so much for that. 

We don't have test tags for Adx inventory...

I'd guess you don't have test tags for AdX inventory for the same reason no-one does. Such a thing doesn't exist.

when processing Adx inventory the SDK may send requests differently...

Yeah, this is the crux of my questions: In what ways it this different? When processing AdX inventory, where could I presume to see these parameters being sent over to AdManager/AdX? 

Anyway, I'm giving up on this, as it all seems way too much hassle.

--

Mikko

[IMA SDK]

Hi Mikko,

Thank you for your message. You can send the ad tag to our testing alias (imate...@gmail.com) instead, so we can continue to check on our end. We really do recommend reaching out to the Ad Manager Forum, as they might be able to give further information and insights regarding your concern.


Regards,

Sherwin Diesta IMA SDK Team

ref:_00D1U1174p._5004Q28oFEO:ref