WIS Platform Guide: Reliable influencer statistics come from official platform interfaces, creator authorization and transparent source records—not from guessed numbers or unrestricted account scraping. This guide explains the permission model World Influencers Summit is building around.
Influencer analytics access works at two levels. First, a social platform reviews and approves an application and the specific permissions it requests. Second, each creator chooses whether to connect an account through OAuth and grant those approved permissions. App approval alone does not unlock every influencer’s private analytics, and a creator’s consent does not let an app collect data beyond its approved scopes.
That distinction matters to creators, agencies and brands. It is the difference between a credible, auditable creator-intelligence product and a database of numbers with unclear provenance. For the World Influencers Summit, the goal is to pair public, cited research with creator-authorized profile data so readers can see what a metric means, where it came from and when it was last updated.
What is influencer analytics access?
Influencer analytics access is permission to retrieve defined account, audience or content metrics through a platform’s official developer products. Some profile facts may be public and available through an app-level credential. Deeper channel analytics generally require the account owner to sign in and authorize the application.
OAuth is the standard authorization flow behind the familiar “Connect your account” button. The creator signs in on the platform—not on the third-party website—reviews the requested permissions and approves or rejects them. The platform then returns a limited authorization token to the application. The creator’s password is never shared with the application.
Public data, authorized analytics and submitted evidence
| Data route | Typical examples | Permission model | How it should be labeled |
|---|---|---|---|
| Public platform data | Public profile identity, published videos, visible counts | Official API access or a public source, subject to platform terms | Platform-sourced, with retrieval date |
| Creator-authorized analytics | Channel reports, audience activity, account-level performance | Approved app plus creator OAuth consent | Creator-authorized and platform-verified |
| Creator-submitted evidence | Media kits, screenshots, campaign results | Creator or representative submits the material | Self-reported, with evidence date |
| Editorial research | Industry reports, platform announcements, market trends | Public primary or reputable research sources | Cited analysis; not a live account metric |
These routes should never be blended into one unlabeled score. A professional ranking methodology records the source type, metric definition, observation date and any limitations. That is the standard WIS is applying to its influencer rankings and research products.
How platform permission works, step by step
- The organization creates a developer application. It describes the product, business entity, website, privacy policy and intended use of platform data.
- The application requests only necessary scopes. A read-only analytics product should not ask for publishing, messaging or account-management permissions it does not use.
- The platform reviews the use case. Review can require a working product, test credentials, a screen recording, business verification and explanations of data storage and deletion.
- The creator initiates connection. The creator clicks a platform-specific connection button and is redirected to the platform’s authorization screen.
- The creator grants or denies permissions. The consent screen shows the requested access. Some platforms allow users to reject individual scopes.
- The application exchanges the authorization code. The secure server receives a short-lived code and exchanges it for tokens. Tokens must be protected and should never appear in public pages, analytics logs or source code.
- Data is retrieved and labeled. The site stores only required metrics, their source and retrieval time, then displays them with a clear verification status.
- The creator can disconnect. Revocation and deletion paths must be easy to find and must stop future collection.
YouTube: channel analytics require creator authorization
YouTube separates public resource data from private channel analytics. The YouTube Data API can provide supported public channel and video resources within project quota. The YouTube Analytics API requires OAuth 2.0 authorization and can return reports for the authorized channel or content owner.
A read-only implementation should use the smallest appropriate scopes, such as youtube.readonly and yt-analytics.readonly, rather than account-management or monetary scopes. Google’s web-server OAuth guide documents the authorization-code flow and offline access needed for scheduled refreshes. Public applications requesting access to certain user data may also need OAuth verification, and YouTube projects that need more quota can be subject to a quota and compliance audit.
Instagram and Facebook: professional-account access and App Review
Meta’s developer platform uses app permissions and access tokens to control what an integration can read. Instagram integrations are designed around the supported account types and products described in the official Instagram Platform documentation. Depending on the product and use case, access to professional account information or insights can require the appropriate permissions, a connected Facebook asset, business verification and Meta App Review.
The practical rule is simple: request only the read permissions that power a visible feature, demonstrate that feature during review and never describe a metric as platform-verified unless it was actually returned through the approved integration for the connected account.
TikTok: scopes are approved for the app and authorized by the user
TikTok makes the two-level permission model explicit. Its Scopes Overview states that approval for a scope does not by itself provide access to a user’s data; each user must authorize the application. For creator profiles, the Display API supports profile and video-display use cases.
The current TikTok scopes reference maps basic identity to user.info.basic, additional profile details to user.info.profile, follower and other profile statistics to user.info.stats, and public video access to video.list. TikTok’s User Info API documentation also specifies which profile fields correspond to those scopes.
X: app-only public access versus user-context authorization
X distinguishes app-only and user-context authentication. According to the official Getting Access guide, a Bearer Token is used for supported read-only public-data requests, while OAuth credentials are used for requests made in a user context. The OAuth 2.0 overview explains app-only Bearer Token access and user authorization. Available endpoints, usage limits and pricing should always be checked before a production integration is designed.
What creators should see before they connect
- The exact platform and permissions requested.
- Which metrics will be collected and how frequently they will refresh.
- Whether the data will be public, aggregated or visible only to the creator.
- How long tokens and metric history will be retained.
- How to disconnect, revoke access and request deletion.
- A direct link to the privacy policy and terms of use.
- A contact route for privacy or data-quality questions.
A trustworthy connection screen should also explain what the application will not do. For a read-only verification product, that normally means no posting, no messages, no password collection and no sale of private creator analytics.
What businesses can learn from permissioned creator data
Follower totals alone are rarely enough for a serious partnership decision. When a creator chooses to share authorized analytics, brands may be able to evaluate documented reach, content consistency, audience response and change over time—subject to what each platform makes available. That creates a better basis for sponsorship discovery than copied profile counts or unexplained third-party estimates.
WIS intends to preserve the provenance of every important figure: platform, metric, retrieval timestamp, authorization status and methodology. The purpose is not to expose private dashboards. It is to help creators present credible evidence and help businesses identify relevant voices for partnerships, research and the World Influencers Summit in New York.
The WIS verification model
The planned WIS creator-data program will use three clear labels:
- Platform-sourced: a public value retrieved through a permitted official interface.
- Creator-authorized: a value retrieved for an account after the creator granted the required OAuth scope.
- Creator-submitted: evidence supplied by the creator or an authorized representative and identified as self-reported.
Editorial articles and market reports remain a separate layer. They use named public sources, link readers to original materials and state the limits of the analysis. Explore the latest work in WIS Insights.
Frequently asked questions
Can an approved app access every influencer’s analytics?
No. Approval gives the application permission to request specific scopes. Private or account-level analytics still require the individual creator to authorize access, and the data remains limited to the granted scopes and supported endpoints.
Does a creator give the website a social-media password?
No. In a correct OAuth flow, the creator signs in directly with the platform. The application receives a limited token, not the creator’s password.
Can access be revoked?
Yes. Creators should be able to disconnect through the product, and platforms provide controls for revoking authorized applications. The application should stop scheduled collection after revocation and follow its stated deletion policy.
Are rankings based only on follower count?
They should not be. A useful ranking explains its methodology and can consider reach, engagement signals, publishing activity, topical relevance, momentum, verification status and data freshness. Metrics from different sources must be labeled rather than treated as interchangeable.
Official sources and further reading
- Google for Developers: YouTube Data API overview
- Google for Developers: YouTube Analytics API reference
- Google for Developers: OAuth 2.0 for web server applications
- Google for Developers: YouTube quota and compliance audits
- Meta for Developers: Instagram Platform
- Meta for Developers: App Review
- TikTok for Developers: Scopes Overview
- TikTok for Developers: Display API Overview
- TikTok for Developers: Scopes Reference
- X Developer Platform: Getting Access
- X Developer Platform: OAuth 2.0 Overview
Build a credible creator profile with WIS
Are you a creator who wants to be considered for the index and the New York summit? Nominate an influencer or submit your profile. Are you a platform, agency, analytics company or brand building the creator economy? Review WIS sponsorship and partnership opportunities.