Skip to content

feat: adding oauth as apple adsearch integration#1399

Open
umbi-svalt wants to merge 4 commits intomainfrom
umb/update-adsearch-docs
Open

feat: adding oauth as apple adsearch integration#1399
umbi-svalt wants to merge 4 commits intomainfrom
umb/update-adsearch-docs

Conversation

@umbi-svalt
Copy link

@umbi-svalt umbi-svalt commented Feb 23, 2026

Motivation / Description / Changes introduced

We are introducing Apple Search Ads OAuth as the primary advanced setup path and need the docs to match the current in-app behavior.

How the App will behave is:

  • Projects with no Apple Search Ads integration (or currently on Basic) are guided to Advanced via OAuth only.
  • Projects already using legacy Advanced credentials continue to see the legacy credential fields, plus a migration banner that recommends moving to OAuth.

Changes introduced

  • Removed the previous advanced credential-based documentation
  • Added Advanced integration OAuth setup guide

Current docs
New docs:
Apple Search Ads & RevenueCat Integration | In-App Subscriptions Made Easy – RevenueCat.pdf

IMPORTANT: This needs to be merged only after the FF on the related Frontend changes is removed/fully routed to the new OAuth flow

Links to discussion, or Linear ticket (if applicable)

Google Doc
Figma Design

Additional comments

@umbi-svalt umbi-svalt marked this pull request as ready for review February 25, 2026 09:06
@umbi-svalt umbi-svalt requested a review from a team as a code owner February 25, 2026 09:06
Copy link
Contributor

@RPallas92 RPallas92 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good 🙏

Should we add a small note mentioning what happens to existing Advanced integrations (e.g. they will see a banner to migrate but current setup will continue working)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants