the ADVERTISING_IDENTIFIER_PLAIN macro

[behea...@gmail.com]

Will the SDK expand the ADVERTISING_IDENTIFIER_PLAIN macro in a tag?  This comes from the DFP set of macros.

thanks,

-dave

[Vu Chau (IMA SDK Team)]

Hi Dave,

Could you elaborate on the use case around the ADVERTISING_IDENTIFIER_PLAIN macro?  If you could let us know where specifically you'd like to see the support expanded, that'd be great.

Cheers,

Vu Chau

IMA SDK Team

[behea...@gmail.com]

Sure - I'm working with Tremor Video and their URLs require a "deviceid" arg, which they tell me is intended to be the IFDA for iOS.  In testing, i've had no issue using the IMA SDK with the tremor video service, with a "test" deviceid.   

In going live, I'll need to put in the appropriate deviceid, and it seems it should come though the macro expansion in the IMA SDK, so I don't have to handle the iFDA in my code.

Here's the test tag I'm using:

http://qtde5.ads.tremorhub.com/ad/mtag?&adCode=wwpr0&playerWidth=320&playerHeight=320&deviceid=[ADVERTISING_IDENTIFIER_PLAIN]&deviceDNT=0&appName=Be%20Heard&appBundle=com.churaonline.beheard&appCategory=music&appStoreId=947903643

I put the macro in as you see, and the ad returned works (this URL is also valid in the Google tag validator).  I'm just not 100% sure that the macro is expanded - the test ad might just work with the bracketed string as id !

thanks!

-dave

[Vu Chau (IMA SDK Team)]

Hi Dave,

I'm going to talk with the rest of the team on this, and we'll see how feasible it is to add further support for your use case.

I'll let you know when we have an update,

Vu Chau

IMA SDK Team

[behea...@gmail.com]

Thanks Vu!

I assume by this that you are also confirming that the SDK doesn't already pass the IFDA to the ad server today in some fashion.

I had (hoped!) that you would say the IFDA is already handled in some way for me.

thanks for the help!

-dave

[Vu Chau (IMA SDK Team)]

Hi Dave,

The SDK does pass the IDFA to the ad server, but we aren't doing anything special with it (which was why I asked where you'd like to see the support expanded).  We simply grab the IDFA from the device and send it to the ad server.  How the server manipulates it depends on which server you are using.

Vu Chau

IMA SDK Team

[behea...@gmail.com]

 Thanks for the clarification!  If IFDA is sent to the ad server, perhaps I'm over-thinking what is needed here.  I just need to verify that Tremor Media  is getting the IFDA.   So far, they tell me they want to receive it in the args string as deviceid=IFDA  in the URL.  Can you disclose how the IFDA is sent to the ad server, so I can see if tremor is fine with it?   

I still have the option of simply adding the deviceid=IFDA in my URL within the app.  That's fine, I have the code to do so, but our current live App doesn't have that code and I was checking to see if it might just work without running another version thru Apple.

That is, our App has no hard-coded advertising URLs  (it queries our server for them).

thanks for your help Vu, 

-dave

[Vu Chau (IMA SDK Team)]

Hi Dave,

There are a few possible scenarios.  

1. If you are not using DFP, and Tremor is the actual (and only) ad server with no redirects, since IMA simply passes the IDFA to the server, you can programmatically grab it yourself without involving IMA.  You can simply append the IDFA to wherever you need within the URL. 
2. If the traffic hits DFP first, you'd need to manipulate with the macro.  Nevertheless, the macro is expanded by the server, and not IMA.

Cheers,

Vu Chau

IMA SDK Team

[behea...@gmail.com]

Thanks Vu - looks like scenario 1 is my scenario.  I think I know what to do now.

-dave