Anonymous Sign-in
Enable anonymous sign-ins to reduce friction for new users and improve conversion rates by allowing them to try your product without providing signup credentials.
Tokenized Paywalls Only: Anonymous sign-ins are only available for tokenized paywalls. Learn more about paywall tokenization.
Conversion Boost: Anonymous sign-ins can improve login conversion rates up to 30–80%.
Overview
Anonymous sign-ins allow you to create temporary users who haven’t signed up for your application yet. This feature:
- Lowers friction for new users to try your product
- Improves conversion rates by removing signup barriers
- Enables trial experiences without email collection
- Maintains user sessions locally on their device
How It Works
When anonymous sign-in is enabled:
- User clicks “Continue without account” instead of signing in with Google
- One-click CAPTCHA verification to confirm they are human
- Automatic account creation with trial tokens deposited
- Full API access like any signed-in user
- Local session storage preserves their account on the device
Enabling Anonymous Sign-ins
Go to Paywall Settings
Navigate to your paywall settings page in the dashboard.
Enable Anonymous Sign-in
Look for the “Anonymous Sign-in” option and toggle it on.
Tokenized Paywalls Only: This option is only available for tokenized paywalls.
Save Configuration
Save your paywall settings to activate anonymous sign-ins.
User Experience
Before Anonymous Sign-in
Users see only the Google sign-in option:
- “Sign in with Google” button
- Higher friction for trial users
- Email required to access features
After Anonymous Sign-in
Users see additional option:
- “Sign in with Google” button (existing users)
- “Continue without account” button (new option)
- Lower friction for new users
Anonymous Sign-in Flow
User Clicks “Continue without account”
The user chooses to proceed without creating a full account.
CAPTCHA Verification
A one-click CAPTCHA appears to verify the user is human:
- Simple checkbox verification
- Prevents bot abuse
- Quick completion
Automatic Account Creation
After CAPTCHA verification:
- Paywall window closes automatically
- Anonymous user account is created
- Trial tokens are deposited
- User can immediately start using the product
SDK Implementation
The exact API differs by SDK — pick your side:
Both ride on the same allow_anonymous flag in paywall settings — your dashboard configuration applies regardless of which SDK you ship.
Limitations
Anonymous User Restrictions
- Purchase Requirement: Must sign in with Google to make purchases
- Device Specific: Session tied to specific browser/device
- No Email: Cannot receive notifications or password resets
- Local Storage: Data can be lost if browser data is cleared