Meta OAuth is required for launch

Creative Tagger's Strategy workspace depends on connected Meta performance. The launch customer flow requires approved read-only OAuth, not manual file uploads.

The important distinction is simple: Creative Tagger does not need write access to a user's ad account. It needs ad-level performance so it can match spend, CTR, thumb stop, hold rate, CPA, ROAS, destination URLs, and conversion data back to analyzed creatives.

The Meta submission should stay narrow: request ads_read, show the read-only connection, show the synced Strategy matrix, and make clear that Creative Tagger does not create campaigns, edit budgets, publish ads, or write back to Meta.

What to request

Permission: ads_read.
Use case: pull Ads Insights and ad metadata for custom creative analytics and reporting.
Access level: Advanced Access/App Review for customers who are not app-role users.
Business Verification: complete if Meta requires it for the app.

What the screencast should show

Meta reviewers need to see the permission actively used inside the app. The review video should be short and literal:

Log in to Creative Tagger with reviewer test credentials.
Open Connect and click Connect Meta.
Complete the Meta OAuth dialog showing ads_read.
Return to Creative Tagger and show the account status as connected.
Click Sync Latest and show ad-level performance loading into Strategy.
Open the Strategy matrix and show CTR, thumb stop, hold rate, spend, CPA, ROAS, and next-test recommendations.

Keep the submission tight. Do not request ads_management for V1. Creative Tagger's launch flow is analytics-only.

Production readiness

Privacy Policy URL is live.
Terms URL is live.
Data deletion contact or URL is available.
OAuth redirect URI is exactly https://api.creativetagger.ai/auth/meta/callback.
Production has META_APP_ID, META_APP_SECRET, META_REDIRECT_URI, META_GRAPH_VERSION, and META_TOKEN_ENCRYPTION_KEY.

Where this shows up in the product

Once Meta is connected and synced, the dashboard Strategy screen lights up with prebuilt and custom reports. The strategist can answer questions against the same performance memory and turn winning or missing combinations into briefs.

This is now a launch gate: if native Meta OAuth is not approved and configured, Creative Tagger should not launch the public customer flow.