Profiles/CRM

Profiles is a CRM for your users. With Profiles, you can:

  1. Find specific users by profile ID, customer user ID, email, or transaction ID.
  2. View the user’s event timeline, including billing issues, grace periods, and other events.
  3. Analyze user’s properties such as subscription state, total revenue/proceeds, and more.
  4. Grant the user a subscription.

イベントフィードのイベントはダッシュボードに届くまでに遅延が発生します。新しいプロファイルや属性の変更はすぐに反映されない場合があります。

profiles.webp

To understand how Adapty creates and links user profiles, see How profiles work.

Finding users

In the Profiles list, you can search for a specific user by:

  • Profile ID: Adapty’s internal identifier for the user (also called Adapty ID).
  • Customer user ID: Your app’s identifier for the user, if you’ve set one.
  • Email: The user’s email, if sent as a custom attribute.
  • Transaction ID: The store transaction ID from a purchase.

Click any row to open the user’s full profile.

Subscription state

In the Profiles list, you can filter and sort users by subscription state. The state values are:

ユーザーの状態説明
Subscribedユーザーは自動更新が有効なアクティブなサブスクリプションを持っています。
Auto-renew offユーザーは自動更新をオフにしましたが、サブスクリプション期間の終了までプレミアム機能にアクセスできます。
Subscription cancelledユーザーはサブスクリプションをキャンセルし、完全に終了しました。
Billing issueサブスクリプションまたはトライアル終了後に請求の問題が発生し、ユーザーに課金できませんでした。
Grace periodサブスクリプションまたはトライアル終了後の課金試行時に請求の問題が発生したため、ユーザーは現在グレース期間中です。
Active trialユーザーはトライアル期間中のアクティブなサブスクリプションを持っています。
Trial cancelledユーザーはトライアルをキャンセルし、アクティブなサブスクリプションはありません。
Never subscribedユーザーはサブスクリプションを開始したことがなく、トライアルも利用したことがない無料ユーザーです。

User attributes

ce8df4d-CleanShot_2023-06-26_at_20.32.232x.webp

You can send additional user properties to Adapty using the SDK.

By default, Adapty sets:

PropertyDescription
Customer user IDAn identifier of your end user in your system.
Adapty IDInternal Adapty identifier of your end user, called Profile ID.
IDFAThe Identifier for Advertisers, assigned by Apple to a user’s device. Requires App Tracking Transparency (ATT) permission on iOS 14+. Not available on Android.
CountryCountry of your end user.
OSThe operating system used by the end user.
DeviceThe end-user-visible device model name.
Install dateThe date when the user was first recorded in Adapty:
  • The date the user was created.
  • If the user installed your app before you integrated Adapty, the install date reflects the date of their first transaction.
  • If applicable, the date provided during a historical data import.
Created atThe date the user was created.

Send at least your internal user ID or user email. This lets you find users by these identifiers in the Profiles list.

After you install the SDK, Adapty automatically collects user events from the payment queue and displays them in the user profile. The attributes in the table above are collected automatically — you do not need to send them.

Custom attributes

In the Attributes section of a profile, you can see custom attributes set via the SDK or API. You can also assign attributes manually using the Add attribute button.

378c1fb-add_attribute.webp

Granting a subscription

In a profile, you can extend an active subscription or grant a user lifetime access to an access level — without requiring them to make a purchase.

b1d74fd-edit_paid_access_level.webp

This is most useful for:

  • Compensating a user after a billing or support issue.
  • Running manual promotions or beta programs.
  • Testing subscription flows without a real purchase.

To grant access, open the user’s profile, go to the Access levels section, and click Edit. Set the expiration date and save. The expiration date must be in the future and cannot be decreased once set. Adjusting it for active subscriptions does not affect ongoing payments.

Granting access does not create App Store or Google Play purchase events. The user’s event feed and analytics will differ from a real purchase flow.

You can also grant access programmatically using the Grant access level API method.

Sharing paid access between user accounts

Access sharing history

When access levels are shared or transferred, the user’s profile shows a link to the connected profile — the profile that shared access, or the profile that received it. To view the connected profile, in the user’s Profile, click the link next to the access level.

profile-access-level-origin.webp

Next steps