-
Notifications
You must be signed in to change notification settings - Fork 509
Support "App-Install Tracking" by default on iOS #17
Comments
I like this, only don't know about the implications. I.E. can an app which doesn't want or can't (i.e. apps for children which need to comply with COPPA) use tracking disable it? |
I don't know any scenario a user don't want to know how often someone opened his app trough facebook. This code-change is only for tracking installs. (COPPA is something for the US, correct me if I don't know anything about your laws) If you have a campaign for example, you can see how many times users installed your app trough facebook advertisement. Does this interfer with any laws or face any privacy issues? |
COPPA is a children privacy protection law. I'm not from the US either! |
I just read a few lines about that. If you ask me, tracking installs should not violate against any children laws? Every single site on this planet has google analytics integrated, I think tracking installs isn't something that violates against laws, but I'm not a lawyer of course. |
Yeah, thinking more about it, kids aren't allowed to have Facebook accounts and if the user doesn't have an account, the tracking does not send personally identifiable information. |
Excatly. Facebook is 13+ nearly wordwide. But the tracking does not obtain any person identifiable informations. It's just "date of install" and "type of device", and time how long app is in use (android, iOS). The code in my example is for iOS only and has to be integrated in android also. iOS: Android: Very easy thing. And as even facebook mention, "Logging app activations as an App Event enables almost all other functionality and should be the first thing that you add to your app." |
ping |
pong |
Hi @jeduan, thanks for updating this! What about android btw? Is this working there as expected? |
Support "App-Install Tracking" by default on iOS ccsoft/cordova-facebook#69
Applauding your efforts to update: What are your plans for this version? #4
The text was updated successfully, but these errors were encountered: