IMA SDK HTML5 referer issue

[Евгений Везелев]

Hello.

I'm using IMA SDK HTML5 for playing ads - and I have to show in my ads statistics referers.

But when I'm using imasdk.googleapis.com/js/sdkloader/ima3.js - the VAST url is being called throw http://imasdk.googleapis.com/js/core/bridge3.133.0_en.html - so the link is a referer for my ads. 

But I need my web page url is to be a referer. How can a do this?

[Binny Patel (IMA SDK Team)]

Hi Евгений,

Would you be able to provide a test page, so we can see the same issue you're facing? 

Thanks,

Binny Patel

IMA SDK Team

[Sebastian Bombitzky]

We faced the same problem.

You can reproduce it with the sample vast in the vastinspector: https://developers.google.com/interactive-media-ads/docs/sdks/html5/vastinspector

The Referer in the Request Headers is https://imasdk.googleapis.com/js/core/bridge3.140.1_en.html

Best regards

[Евгений Везелев]

We have fixed this issue already.

We call this library from our domain name, so it looks like https://my-domain-name.com/js/core/bridge3.140.1_en.html

In this way you will see correct referrer.

--
You received this message because you are subscribed to a topic in the Google Groups "Interactive Media Ads SDK" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ima-sdk/Uw30ImwdBlw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ima-sdk+unsubscribe@googlegroups.com.
To post to this group, send email to ima...@googlegroups.com.
Visit this group at https://groups.google.com/group/ima-sdk.
For more options, visit https://groups.google.com/d/optout.

[Yury Pavlotsky (IMA SDK Team)]

Hi,

The referrer can be found in the 'url' query string parameter. Also, you shouldn't host the SDK or related files yourself, since it is automatically updated and expects to be loaded from the proper domain.

Thanks,

Yury Pavlotsky

IMA SDK Team

On Tuesday, August 23, 2016 at 10:27:49 AM UTC-4, Евгений Везелев wrote:

We have fixed this issue already.

We call this library from our domain name, so it looks like https://my-domain-name.com/js/core/bridge3.140.1_en.html

In this way you will see correct referrer.

[Han Soso]

Hey Yury,

can you give me an example of the 'url' query string parameter?

Cheers,

Dennis

[Yury Pavlotsky (IMA SDK Team)]

Hi Dennis,

If you look at our Video Suite Inspector, when you test the sample ad there, you can see that when the ad is requested, there will be a url parameter passed along that looks like this:

url=https%3A%2F%2Fdevelopers.google.com%2Finteractive-media-ads

Which will be the referrer URL.

Thanks,

Yury Pavlotsky

IMA SDK Team

[Deebu Jacob]

Hi Yury,

Is there a way to pass the web page URL in request headers? When I use IMA SDK HTML5, referrer in request headers is always "http://imasdk.googleapis.com/js/core/bridge3.147.1_en.html" for VAST instead of hosting page url.

Thanks,

Deebu

[Yury Pavlotsky (IMA SDK Team)]

Hi Deebu,

The referrer is in the 'url' parameter of the request headers.

Thanks,

Yury Pavlotsky

IMA SDK Team

[Dennis Leven]

Hey Yury,

I was able to find the referrer. (see appendix)

My question now is since this information is provided to you(!) how shall we receive this information in our adserver?

Cheers,

Dennis

[Vu Chau (IMA SDK Team)]

Hi Dennis,

Since you are asking about ad serving's side of things, the DFP support forum would be able to assist you with it.  The team on this forum is only providing support for strict SDK inquiries.

Thanks,

Vu Chau

IMA SDK Team

[billy miranda]

Hi , 

We are having same issue, we have a iframe embed which contains video with an ad.  

We are passing the page (page.A) domain as value for "URL"macro, but whenever we the the page.A called from via iFrame from different domain,  the referrer changes value to the page where iframe is hosted.

[Chris Feldman (IMA SDK Team)]

Hi Billy,

How are you passing the host page's URL to the url parameter? Please share code snippets, or a test page and we can help you debug the issue.

Regards,
Chris Feldman
IMA SDK Team

[billy miranda]

Hi Chris, 

It took me long because i thought it was fixed but until now we are getting some glitches, here is how we set parameters

https://pubads.g.doubleclick.net/gampad/ads?sz=640x480&iu=/[some_id]/Herdaily&impl=s&gdfp_req=1&env=vp&output=vast&unviewed_position_start=1&url=http%3A%2F%2Fdomain.com%2Fslug%3Fpage.html&description_url=http%3A%2F%2Fdomain.com&correlator=

[billy miranda]

What's happening is, even we set url parameter to different url it still use the header url.

Adtag Passed:

https://pubads.g.doubleclick.net/gampad/ads?sz=640x480&iu=/124319096/external/single_ad_samples&ciu_szs=300x250&impl=s&gdfp_req=1&env=vp&output=vast&unviewed_position_start=1&cust_params=deployment%3Ddevsite%26sample_ct%3Dlinear&correlator=&url=http%3A%2F%2Fvideos.lifestylepeep.com%2Fads%2FLifestylePeepV%2Flifestylepeepv

But when I check the Query String Parameters on console it changed:

http://prntscr.com/expgb3

[Chris Feldman (IMA SDK Team)]

Hi,

Thank you for following up with us. It is expected that the SDK will replace the value for 'url.' If you want to pass your own value, you can do so by specifying the 'description_url' value. The SDK will not overwrite the 'description_url.'

Let me know if you continue to have issues.

Regards,

Chris Feldman

IMA SDK Team

[billy miranda]

Hi Chris, 

Thanks for quick response , and yes we manage to override the "description_url" but when we visit the reports on google adx , it still uses the domain of the parameter "url" for column  "sites" and not the "description_url" value.

Thanks!

[Chris Feldman (IMA SDK Team)]

Hi Billy,

We're only able to deal with technical, client-side issues on this form. For serving issues, and issues with your account, you'll have to reach out to the AdX team directly.

Regards,

Chris Feldman

IMA SDK Team

[Thanh Huy Ly]

Hi IMA SDK Team,

We are facing the same problem. We use IMA SDK as a player to our video instream ads and we need to parse our domain as referrer to several ad exchanges.

However, when looking at the request headers, we always get "http://imasdk.googleapis.com/js/core/bridge3.179.0_en.html" as an referrer and not our domain that is actually displaying the video ad.

1. Referer:
   http://imasdk.googleapis.com/js/core/bridge3.179.0_en.html

We are able to parse our domain url to IMA SDK and, in turn, we parse it to the ad exchanges respective VAST tags through their respective referring url parameters,

however this is not good enough as they also check the request headers for the referrer, which contains: http://imasdk.googleapis.com/js/core/bridge3.179.0_en.html

How can we make sure that the referer in request headers show our domain url instead?

Thanks!

Best,

Thanh Huy

[Chris Feldman (IMA SDK Team)]

Hi Thanh,

Changing the referrer value in the header of an ad request is not currently supported. Ad requests are made from the SDK's iframe, which will always have "http://imasdk.googleapis.com/js/core/bridge3.179.0_en.html" as the referrer.

I recommend reaching out to your ad provider to see if it's possible to omit the referrer from your serving settings. Instead, you can pass your page URL as an query string parameter, though it sounds like you're already doing this.

Please let me know if you have any further questions.

Regards,

Chris Feldman

IMA SDK Team

[Thanh Huy Ly]

Hi Chris,

Many thanks for your fast reply!

Yes, we are already parsing our page URL as an query string parameter to the ad providers.

It seems like it's an occurring problem. Do you have any plans for making it possible to change the referrer value in the header of an ad request in the near future?

Best,

Thanh Huy

[Chris Feldman (IMA SDK Team)]

Hi Thanh,

The reason that it isn't possible to change the referrer value in your request header is a function of the way the HTML protocol behaves. This is out of the SDK's hands.

Please let me know if there's anything else you need. Thank you for reaching out to support.

Regards,

Chris Feldman

IMA SDK Team

[kevin....@sendtonews.com]

What is preventing the sdk from replacing XMLHttpRequest.prototype.send with a sequence that: postMessages to the publisher page, does the ajax request on the publisher side as an ArrayBuffer result, transfers the result back across using PostMessage, and then fires the necessary events on the XMLHttpRequest object?

[Thanh Huy Ly]

Hi Chris,

Thanks for your help!

Have a great day,

Best,

Thanh Huy

[Chris Feldman (IMA SDK Team)]

Hi All,

I'm not able to comment further on the internal workings of the SDK. I suggest following our release notes, as well as our blog. If it becomes possible for us to address this behavior, you'll be able to find more information using those resources.

Thank you for reaching out to support.

Regards,

Chris Feldman

IMA SDK Team