Skip to main content

Dashboard Guide

The PrivateAV Dashboard is your central hub for managing API keys, monitoring analytics, and configuring webhooks.

:::tip Related Resources

Getting Started​

Access your dashboard at https://portal.privateav.com.

First Time Setup​

  1. Create Account: Sign up with your business email
  2. Verify Email: Check your inbox for verification
  3. Create API Keys: Generate your first key pair for integration

Dashboard Sections​

Overview​

Your dashboard home page shows:

  • Usage Metrics: Verification counts and success rates
  • Quick Actions: Links to Analytics, API Keys, and Billing
  • Account Status: Current plan and usage

Analytics​

View aggregate verification insights and trends:

  • Key Metrics: Verification attempts, total verifications, conversion rates
  • Verification Trends: Volume and conversion rate over time
  • Time Range: 24 hours, 7 days, 30 days, or custom date range
  • Device Analytics: Usage breakdown by device type with conversion rates
  • Geographic Distribution: Top locations by verification volume
  • Outcome Breakdown: Completed, failed, in progress, and abandoned attempts
  • API Key Filtering: View metrics for specific API keys or key pairs

Analytics focuses on high-level trends and performance metrics. For individual verification records, use the Verifications page.

Verifications​

Browse, search, and filter individual verification sessions.

Search:

  1. Enter an externalUserId or Session ID (UUID)
  2. Click Search to find matching sessions
  3. Leave blank to browse all sessions in the selected range

Filters:

FilterOptions
OutcomeCompleted (Success + Failed), Success only, Failed only
ModeAll, L1, L2
DeviceAll, Desktop, Mobile, Unknown
CountryDynamically populated from your verification data
Time RangeLast 24h, Last 7 days, Last 30 days, Custom
API KeyAll keys, specific key pair, or individual key

Results table:

  • Session ID — Click to copy full ID
  • External User ID — Click to copy (if provided)
  • Timestamp — Date and time of verification
  • Device — Desktop, Mobile, or Unknown
  • Country — User's country (from geolocation)
  • Mode — L1 or L2
  • Outcome — SUCCESS or FAILED

API Keys​

Manage your integration credentials:

  • Publishable Keys (pk_...): For client-side SDK
  • Secret Keys (sk_...): For server-side API
  • Key Pairs: Created together for security

Integration Tools​

Ready-to-use code examples:

  • Frontend Integration: Simple client-side implementation
  • Server-side Integration: Complete backend workflow
  • Multiple Languages: Node.js, Python, PHP examples
  • Framework Support: React, Vue, Angular

Configuration​

Manage your verification settings across four tabs:

Verification​

  • Verification Mode: Choose L1 or L2. See Verification Modes for details.
  • Challenge Age: Age threshold for L1 mode (25-99). Users estimated at or above this age pass without ID.

Domains​

Restrict which domains can use your API keys:

  • Root domains (e.g., example.com) automatically include all subdomains (www.example.com, shop.example.com, etc.)
  • Subdomains (e.g., www.example.com) match exactly—they do not include the root domain
  • Leave empty to accept requests from all domains (default)

Enter domains without https:// or trailing slashes.

Webhooks​

Configure event notifications. See Webhooks for setup.

Emblem​

Enable or disable the Emblem integration for portable age verification accounts.

Billing​

Owners and administrators can manage subscriptions, view usage, and access Billing → Invoices and billing details.

  • Paid invoices are created from verified billing activity. Free accounts, unconverted trials and test payments do not receive paid invoices.
  • Invoice PDFs are attached to billing emails. Recipients do not need a dashboard account.
  • When a provider's original invoice still shows its original amount due, a separate payment confirmation records the verified settlement and zero remaining balance. Keep both PDFs. The original invoice is unchanged; do not pay it again. Later refunds and credits appear separately in invoice history.
  • Leave the primary billing email blank to use the account administrator, initially the owner. A primary email replaces that destination. Additional recipients and an administrator copy are optional. The page shows the saved effective recipients.
  • Business name, billing address and tax ID are optional billing details, separate from login and payment details. Changes apply to future invoices. Contact support for a correction to an issued invoice.
  • Invoice history shows service periods, settlement and issue dates, amounts, balance due, downloads and email status. History remains available after cancellation. Historical documents may appear without a new email.
  • “Accepted by email provider” does not confirm recipient delivery. Bounced, failed or unresolved messages need attention. Use resend to request another copy; an unresolved previous attempt may still arrive.
  • A payment still being reconciled may not have a PDF yet. If a completed payment is missing or a correction is needed, contact support with the payment date and provider reference. Do not pay again to obtain an invoice.

Payment methods and subscription collection remain with the provider shown in the account. This invoice workflow does not change prices, collection or usage limits.

Team​

Manage your team with role-based access control:

Roles​

RoleDescription
OwnerFull account access. Can manage billing, delete the account, and assign any role including Owner.
AdminFull product access. Can manage team members and billing, but cannot delete the account or modify Owner roles.
MemberDay-to-day access. Can view analytics, manage API keys, and view configuration and webhook delivery health. Cannot change configuration or webhooks, access billing, or manage team.
ViewerRead-only access. Can view analytics and reporting data only.

Permissions by Role​

PermissionOwnerAdminMemberViewer
Analytics✓✓✓✓
API Keys✓✓✓—
View configuration and webhooks✓✓✓—
Change configuration and webhooks (endpoints, signing secrets, test, resume, redeliver)✓✓——
Billing✓✓——
Invite members✓✓——
Change roles✓✓*——
Delete account✓———

*Admins cannot modify Owner roles.

Managing Members​

  • Invitations: Invite team members by email with a required role selection
  • Role Changes: Owners and Admins can change member roles inline from the team list
  • Activity Tracking: View last active timestamps for all members

Account Settings​

Manage your account:

  • Account Information: View email and role
  • Account Deletion: Secure account removal with confirmations

Key Features​

Webhook Testing​

Test webhook endpoints directly from the dashboard:

  1. Configure webhook URL in Configuration
  2. Select events to receive
  3. Use test button to send sample events
  4. Verify your endpoint receives events correctly

Responsive Design​

The dashboard works on all devices:

  • Mobile-friendly interface
  • Touch-optimized controls
  • Consistent experience across platforms

Getting Help​

Email: support@privateav.com

Include session IDs and error messages for faster support.

Paid invoice history retains the original document when a payment is refunded or credited. Related refund confirmations and provider credit notes appear as invoice updates with their own downloads. A refund and its credit note can describe the same adjustment; do not add them together. Pending or failed refunds remain labelled with their actual status.

For PayPal, save the correct billing identity, open the invoice's identity correction action, and provide a reason. This creates a linked correction PDF while preserving the original invoice. Use resend when you want to email the invoice and correction. Contact support for a Stripe invoice correction.

An email accepted by the mail service is not yet confirmed delivered. If an attempt has an unknown outcome, review it before resending; the previous message may still arrive. Recipient recovery resends only to the selected current billing recipient and records the request in invoice history.

Changing recipients redirects automatic email that has not yet been submitted; messages already in progress may still arrive. A queued resend to an explicitly selected recipient is canceled when that recipient is removed. Adding a recipient does not email the historical backlog. Use the selected-recipient action to send a past invoice to a corrected address. You can close recovery for a removed failed destination while retaining its original email outcome.