revenuecat-identify-user

Link app authentication users to RevenueCat identities via logIn and logOut.

58|5|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/RevenueCat/ai-toolkit --skill revenuecat-identify-user
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: revenuecat-identify-user
Source: https://github.com/RevenueCat/ai-toolkit/tree/main/revenuecat/skills/revenuecat-identify-user
Command: npx skills add https://github.com/RevenueCat/ai-toolkit --skill revenuecat-identify-user

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keep RevenueCat subscribers aligned with your app’s authentication users so entitlements and purchase history map to the right person instead of a temporary anonymous identity.

Core Features & Use Cases

  • Log in identity linking: Switches from the $RCAnonymousID: placeholder to your stable appUserID using logIn, including after purchases were made while anonymous.
  • Account switching & logout: Ensures correct identity transitions by calling logOut for identified users and then logIn for the next user.
  • Platform-specific wiring: Provides the correct logIn/logOut patterns for iOS, Android, Kotlin Multiplatform, Flutter, and React Native.

Quick Start

Tell the skill to identify the current signed-in user by calling RevenueCat logIn with the stable appUserID after your auth system confirms the session.

Frequently Asked Questions about revenuecat-identify-user

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync app authentication users with RevenueCat identity?

Sync app authentication users with RevenueCat identity by replacing the default anonymous appUserID with a stable appUserID via logIn after your auth system confirms the session. This ensures entitlements and purchase history map to the correct person.

What happens to RevenueCat purchases made while anonymous when a user logs in?

Purchases made while anonymous are preserved when transitioning to an identified user. The logIn method switches from the $RCAnonymousID placeholder to your stable appUserID, linking the existing purchase history and entitlements to the correct identity.

Does RevenueCat logIn and logOut work on Flutter and React Native?

RevenueCat logIn and logOut work across iOS, Android, Kotlin Multiplatform, Flutter, and React Native. The platform is detected from project files, and platform-specific wiring patterns are applied for correct identity transitions.

What's the best way to handle account switching with RevenueCat subscriptions?

Handle account switching by calling logOut for identified users first, then logIn for the next user. This ensures correct identity transitions and prevents entitlement mapping errors during multi-account switching scenarios.

What IDs should I avoid using as RevenueCat appUserID?

Avoid using email addresses, phone numbers, or sequential IDs as your RevenueCat appUserID. These violate guardrails and can cause identity mapping issues. Instead, use a stable internal identifier from your authentication system.

Why should I not call RevenueCat logOut while the user is anonymous?

Calling logOut while anonymous is unnecessary and can cause identity issues. LogOut is designed for identified users to properly transition between accounts. Anonymous users should use logIn directly to switch to a stable appUserID.