There is an issue that affects any publisher or advertiser using Testflight to test iOS builds that incorporate Tapjoy. Namely, each time a Testflight-distributed app asks for the the Identifier for Advertisers (IDFA), it will get a different IDFA. Normally, IDFA remains constant for a device until a user resets it manually, which most users never do. But when a Testflight build asks for the IDFA from the operating system, it doesn’t get the "real" IDFA: it gets a "fake" IDFA that changes each time the app asks for it.
- The same videos and offers will be seen repeatedly, regardless of prior viewing or completion. Every time an app asks for content, the IDFA will be different. Apple’s rules require that we "respect" changes in IDFA, and therefor our system will treat the new IDFA as a new user.
- Frequency capping will not work, as each request will be treated like a "first" request.
- Setting a device as a Test Device in the dashboard for purposes of seeing test offers won’t work, as the test device is identified via IDFA.