Hi,
i know that Corona changed already the IDFA for iOS
now as there is the new Google Policy I also like to ask if
all Ad Plugins like AdMob, InMobi are also compliant with the new Google Policy??
Thanks
Chris
Chris, do you have a URL where we can read about this?
Thanks
Rob
got this from applovin:
As you may know, Google released an updated Developer Content Policy that restricts the use of identifiers for advertising purposes to only the Google Advertising ID. Google has said that it will begin to enforce the policy as of August 1, 2014.
AppLovin has released an updated SDK that complies with this change (and also requires Google Play integration as per Google’s new policy) and we noticed that you are possibly running a version of our SDK prior to our compliant v5.4.0. If you submit an app updateAugust 1 or later with an old SDK, Google will likely send you a notice given it pulls Android ID as well.
Note that this is an industry wide event similar to Apple’s iOS changes to IDFA and you should check with ALL your third party providers to confirm no use of Android ID in their latest SDK’s.
Additionally, there are lots of other performance enhancements here particularly around the use of video and the UX of our ads and updating will naturally allow you to take advantage of improved performance.
We look forward to continued growth and if any questions as always, don’t hesitate to reply here directly or speak with your dedicated rep.
at this point… is there any development for a AppLovin AdPlugin???
thx
chris
Thanks Chris. I’ve passed this on to Engineering. Just as an FYI, the AdMob V2 plugin is compliant with this change.
Rob
Hi Rob / Corona team,
With August 1st just around the corner, it would be extremely helpful to get some transparency about where all of the (relevant) plugins stand with respect to Google’s new policy. I’ve been following the forums, and while there’s been discussion for some plugins (e.g., Vungle, AdMob), there’s no discussion or clarity on several others (e.g., Sponsorpay and many others).
More generally, I think Corona should provide a mechanism for us to know what versions of third-party SDKs are being linked into our projects on each platform. A simple page (similar to the daily build page) would be perfect. That way, we could cross-reference the version listed there with the third-party website to figure out whether we’re compliant with the new policy (and any other things we might want to check).
Thanks!
- Andrew
I will pass this on to the team, but with regards to 3rd party products, have you tried contacting them at their website’s “Contact Us” page? Different vendors monitor the forums at their discretion and I’m not sure how practical it is for us to track the information you’re requesting.
Rob
+1 - What Andrew said.
Rob, it’s a troubling realization that CL doesn’t have much insight into what the 3rd party plugin providers are doing under the hood, but surely CL would know more than we lowly customers do. The info Andrew described is so basic; what version of an SDK is being linked into our project? If there’s no way to find that information on this site or in the plugin docs (where it belongs, imo), and the provider isn’t present on these forums to answer such basic questions, then there are bigger problems with the plugin ecosystem than I thought.
Thanks Rob. I’ll try the Contact Us option, but in the end that’s not the most scalable solution (many Corona developers would be doing that). A more scalable solution would be to let (or better yet, encourage or even require) the vendors to indicate what version of their SDK is being included via the plugin. They could do this on the documentation page for their plugin or a separate, dedicated page that shows all plugins. Presumably, when they update the plugin, the push it to Corona (since I think Corona hosts many of the plugins). It doesn’t seem like it would be too hard to require, in that process, that they include some versioning information that’s made visible to the community.
- Andrew
Chris, do you have a URL where we can read about this?
Thanks
Rob
got this from applovin:
As you may know, Google released an updated Developer Content Policy that restricts the use of identifiers for advertising purposes to only the Google Advertising ID. Google has said that it will begin to enforce the policy as of August 1, 2014.
AppLovin has released an updated SDK that complies with this change (and also requires Google Play integration as per Google’s new policy) and we noticed that you are possibly running a version of our SDK prior to our compliant v5.4.0. If you submit an app updateAugust 1 or later with an old SDK, Google will likely send you a notice given it pulls Android ID as well.
Note that this is an industry wide event similar to Apple’s iOS changes to IDFA and you should check with ALL your third party providers to confirm no use of Android ID in their latest SDK’s.
Additionally, there are lots of other performance enhancements here particularly around the use of video and the UX of our ads and updating will naturally allow you to take advantage of improved performance.
We look forward to continued growth and if any questions as always, don’t hesitate to reply here directly or speak with your dedicated rep.
at this point… is there any development for a AppLovin AdPlugin???
thx
chris
Thanks Chris. I’ve passed this on to Engineering. Just as an FYI, the AdMob V2 plugin is compliant with this change.
Rob
Hi Rob / Corona team,
With August 1st just around the corner, it would be extremely helpful to get some transparency about where all of the (relevant) plugins stand with respect to Google’s new policy. I’ve been following the forums, and while there’s been discussion for some plugins (e.g., Vungle, AdMob), there’s no discussion or clarity on several others (e.g., Sponsorpay and many others).
More generally, I think Corona should provide a mechanism for us to know what versions of third-party SDKs are being linked into our projects on each platform. A simple page (similar to the daily build page) would be perfect. That way, we could cross-reference the version listed there with the third-party website to figure out whether we’re compliant with the new policy (and any other things we might want to check).
Thanks!
- Andrew
I will pass this on to the team, but with regards to 3rd party products, have you tried contacting them at their website’s “Contact Us” page? Different vendors monitor the forums at their discretion and I’m not sure how practical it is for us to track the information you’re requesting.
Rob
+1 - What Andrew said.
Rob, it’s a troubling realization that CL doesn’t have much insight into what the 3rd party plugin providers are doing under the hood, but surely CL would know more than we lowly customers do. The info Andrew described is so basic; what version of an SDK is being linked into our project? If there’s no way to find that information on this site or in the plugin docs (where it belongs, imo), and the provider isn’t present on these forums to answer such basic questions, then there are bigger problems with the plugin ecosystem than I thought.
Thanks Rob. I’ll try the Contact Us option, but in the end that’s not the most scalable solution (many Corona developers would be doing that). A more scalable solution would be to let (or better yet, encourage or even require) the vendors to indicate what version of their SDK is being included via the plugin. They could do this on the documentation page for their plugin or a separate, dedicated page that shows all plugins. Presumably, when they update the plugin, the push it to Corona (since I think Corona hosts many of the plugins). It doesn’t seem like it would be too hard to require, in that process, that they include some versioning information that’s made visible to the community.
- Andrew