Experiment - iPad/iPhone Survey for new user coming from DMA Choice Screen

[data-sync-user]

We need to trigger a survey for users coming from choice screens… but not all choice screens, what we call “choice screen 2” (Please see https://developer.apple.com/support/browser-choice-screen/  

“Developers of browsers on the choice screen will have access to a new set of data, available via an API in App Store Connect, about their browser’s performance on the choice screen. This data will include items such as selection rates on the choice screen and information about default selection. Developers should contact their Apple representative or [email protected] for more details.” (https://mozilla.slack.com/archives/C05RASG40R3/p1724349033290529 )

Android work (as reference): https://mozilla.slack.com/archives/C06DF8U7H19/p1719954735654389

┆Issue is synchronized with this Jira Spike

[data-sync-user]

➤ Norberto Andres Furlan commented:

From Nimbus team: “..In the ios client find some way to programmatically identify that a dma choice screen was used, record that somewhere in memory, when we construct the ios targeting context, include some variable like 'dmaChoiceScreenUsed': bool, and then later when we target something like version==... & channel=... & dmaChoiceScreenUsed"

[data-sync-user]

➤ Norberto Andres Furlan commented:

Not possible. Apple APIs doesn’t provide this information. Chloe MacKie

[data-sync-user]

➤ Chloe MacKie commented:

Thanks Andy and team

[data-sync-user]

➤ Nishant Bhasin commented:

More info as an FYI:

Seems like there is nothing in the report for us. Which means there are two reasons for it a) Either we are missing a crucial information on how to get this report but I have tried multiple methods

• Using custom python script - Returns nil
• Using a library to fetch this information - Returns nil
• Doing it raw via command line - Returns nil

b) The reports actually are nilI case of b) I am curious to know why that is as Firefox iOS has been a default browser for almost an year so we should be getting some reports here.Also the API is not easy to work with like I mentioned before.One has to first generate a report for which they need an Admin key (which is absurd) as Admin key gives someone access beyond their requirement and then you need another key (likely for Data Science) to fetch these reports. These reports are not easy to fetch and infact took me a day and an half to know what exactly it is we are looking for. Even then after doing both a) and b) and not entirely sure where the problem is. Is it with Apple itself or we are doing something incorrect on our end.Regardless I am getting a nil response for both Browser Choice Screen Engagement and Default Browser Usage

Browser Choice Screen Engagement Browser Report ID: r173-9e51ae36-fa2e-42b9-adfb-1c994a675cc8 SEGMENTS RESPONSE Start instance response = AnalyticsReportInstancesResponse(data: [], links: AppStoreConnect_Swift_SDK.PagedDocumentLinks(this: "https://api.appstoreconnect.apple.com/v1/analyticsReports/r173-9e51ae36-fa2e-42b9-adfb-1c994a675cc8/instances", first: nil, next: nil), meta: Optional(AppStoreConnect_Swift_SDK.PagingInformation(paging: AppStoreConnect_Swift_SDK.PagingInformation.Paging(total: Optional(0), limit: 50))))Default Browser Usage Browser Report ID: r165-9e51ae36-fa2e-42b9-adfb-1c994a675cc8 SEGMENTS RESPONSE Start instance response = AnalyticsReportInstancesResponse(data: [], links: AppStoreConnect_Swift_SDK.PagedDocumentLinks(this: "https://api.appstoreconnect.apple.com/v1/analyticsReports/r165-9e51ae36-fa2e-42b9-adfb-1c994a675cc8/instances", first: nil, next: nil), meta: Optional(AppStoreConnect_Swift_SDK.PagingInformation(paging: AppStoreConnect_Swift_SDK.PagingInformation.Paging(total: Optional(0), limit: 50))))If Apple requests a response here then I can work with them although you can clearly see the first: nil and next: nil means we get nothing.

[github-actions[bot]]

This issue has been automatically marked as stale. Has the issue been fixed, or does it still require the community's attention? Please leave any comment to keep this issue opened. It will be closed automatically if no further update occurs in the next 30 days. Thank you for your contributions!