Where to access iosAdvertisingIdentifier

Solar2D Monetization (in-app purchases, ads, etc.)
#21

I agree, it would be great to have access to this again for those of us doing our own ad integrations (such as a server intermediate like rune7 mentioned).

Similarly, it would be great to have access to the Google AID for the same reason.

It seems the current thinking is to restrict all Corona developers from accessing these identifiers because of a concern that they would be misused.  But it would be better to let the each developer decide how to use them in compliance with Apple and Google’s policies rather than prevent everyone from using it.

  • Andrew
#22

Google Advertiser ID is also a must since August. its also applies to current Admob plugin.

neither google nor apple forbid using these values. they encourage using it, for the right purposes. 

its good to have them out of the general compilation, but they must appear on some very simple attribute plug-in for advertising! 

Just FIY, all the current ad networks you can link to or even the native ones that offer their jave SDK, are all part of a chain where you as publisher gets the scraps after each mediator took his piece, at some you may be getting only 30% of the value of your inventory. The large publishers use mostly direct deals. If we want to get the most of what we have, we must implement our own solution and therefore its a must for us to have all the fields our competitors have.

#23

We are including this functionality in our upcoming Utilities plugin.

#24

This info is essential and must be provided by Corona team. It was provided before and then removed which is a severe degradation. Its also being used by iAds and adMob repsective plug-ins. Exposing it again should be a no brainer.

Utilities plugin may be beneficial to some, but unless you provide it as free plugin for corona lab, it’s not a solution. I have no wish to begin increasing operational costs with premium plug-ins. we have enough costs as it is, we try to ramp up our revenues instead… 

#25

It will be about $30. We don’t get paid to make these plugins so unfortunately we can’t release them for free. 

That’s the scoop. :>

#26

I wish you luck with your plug-ins. Advertising info, however, is not premium stuff and should be provided as a base plug-in by corona.  

#27

Rune7 and others - we understand some of you need access to the identifiers. We want to provide that access as quickly as possible, but we also have to think ahead and do what is best in terms of architecture. Since these identifiers have changed in the past and will probably be subject to change in the future, we think the best way to expose them is going to be via plugins. 

In the very short term, it will probably have to be through a premium plugin, as Gremlin has stated. Later on we may be able to move it to a free plugin.

#28

We don’t have an argument that these values belong in a plug-in. I don’t think you realize the severity of the issue at hand. We have live games using these fields! How are we expected to update our ad supported game on android which needs Android advertiser ID starting August 1st??? 

We expect to get a solution from corona as soon as possible to cover the degradation of the system.info API. You made a quick, half baked change to comply with Apple guidlines regarding usage of the advertising ID. Now you need to return the SDK to its previous state.

Note that these are just fields, already in use in iAds an Admob plugins which you do support and comply to latest guidlines. Having them exposed as well in an advertising data plugin can probably be completed including full testing within a day. you should give this a proiority over other nice to have items (which comprise most of what was added during 2014 so far). I understand your need to show more features, but in software development, there are lines you must not cross. Degrading APIs is a huge red flashing line. Note that even apple did not retire its unique Id before having a solid replacement and also game another year for all publishers to comply. 

Any future requirement from the app stores will anyhow be restricted to this plug-in. For the time being, we do not expect further modifications.

I can write my own engine for particles using your current API, but I can’t write one to get these ad fields. As a multi-platform solution, the minimum you are expected to, is to expose the most of each platform APIs you support. Ease of use addons, such as particles, composer, editor etc. can certainly come from a 3rd party.

#29

Hey everyone - there is now a plugin available that exposes the identifiers:

http://docs.coronalabs.com/daily/plugin/advertisingId/index.html

#30

There seem to be a problem accessing that page.

#31

rune7 - That is very strange. Sorry about that.

I’m not sure what happened, but someone from the team will look at it early tomorrow (it is midnight here right now)…

#32

Ok, it should be working again:

http://docs.coronalabs.com/daily/plugin/advertisingId/index.html

#33

Good, can see it now.

Please note that we also need the previously called parameter iosAdvertisingTrackingEnabled from the device.

This is required by apple when using the advertising id.

On google its called isLimitAdTrackingEnabled and is available as part of the same AdvertisingIdClient.Info

#34

It’s great news that this plugin is now available, but I agree with rune7 that we also need iosAdvertisingTrackingEnabled (iOS) and isLimitAdTrackingEnabled (Android) so that we can use the advertising identifiers in according with Apple/Google policy.

Thanks!

  • Andrew
#35

Done! The great Danny has now added that as soon as he heard it was missing.

#36

Well done corona team! we love your ability to respond quickly when its important. 

we will begin testing early next week but I expect no real issues here.

#37

Agreed, thanks to the team for implementing this and turning it around quickly!

  • Andrew