With Apple's policies regarding the IDFA (the Identifier for Advertisers), a few minor updates should be considered before continuing to run the remarketing campaigns.
Campaign deliveries and user tracking on the mobile app are done through data such as push tokens, user events, attributes, etc., which are collected through Insider's Mobile SDK. Insider utilizes mutually agreed identifiers such as email, phone number, and unique user ID to identify users. If none of these identifiers is integrated, Insider's systems generate an identifier for the users, which has no value outside the Insider database.
IDFA comes into play only if Insider uses its Remarketing product. This product shows ads on Google and Facebook to users via the IDFA identifier. This means that IDFA and Remarketing differ from Insider's mobile product's remaining capabilities and features.
Apple's policy targets precisely the IDFA & Remarketing. To collect IDFA from users, applications need to get their consent just as they do for push opt-in. Without this consent, users will not have their IDFAs shared with Insider and hence will not be eligible for Remarketing. This policy does not affect your processes if you do not use the Remarketing product.
For our customers who use the Remarketing product, Insider has an SDK method that needs to be integrated manually by the customers' developer teams in addition to Insider's standard integration. This method sets the IDFA collection ON or OFF at the user level. This means that Insider's SDK does not collect the IDFA by default, and this collection shall be enabled by the customer with an extra integration. If a user consents to IDFA sharing, this method can be used to turn on the IDFA collection for the user and vice versa if they decide to opt out of the IDFA collection.
Additional note for Google 3rd Party Cookie Policy Act
Regarding Google's policy about cookie usage, mobile app SDKs and features do not use any kind of cookies. Insider uses direct app integration to collect and use data; hence, Insider's collection behaves as a first-party that receives data upon trigger rather than getting it from a stored cookie data pool. This policy has no current effect on Insider's mobile app features.