Customers and customer details
Find InAppify customers by identifier and review access, subscriptions, consumable purchases, transactions, attributes and customer history in the dashboard
A customer is an app user within a specific project, not a developer or dashboard collaborator. The identifier sent by your app must match the customer you inspect.
Find a customer
- Select the correct project and open Customers.
- Search by customer identifier and apply status filters if needed.
- Open a customer row for details.
If a customer is missing, check the project, identifier, and SDK identification. Use transactions to locate purchases by financial identifiers.
Customer access and details
Review customer identifiers, registration source, registration time, and current status. The entitlement area shows recorded access. Subscription history is not equivalent to active access: a recorded period may have expired.
Use the appropriate tab:
- Subscriptions: review periods, associated apps, and entitlements.
- Consumable purchases: inspect purchases with separately tracked consumption or delivery.
- Financial transactions: review associated payments and follow the transaction guide.
- Attributes: inspect data usable in targeting; a known attribute name does not imply every customer has a valid value.
- History: customer-specific history, not project-wide team activity.
Grant access and query a store
Grant entitlement manages access; it does not record a financial purchase or refund money. Verify the customer, entitlement and duration before confirming. The corresponding permission is required.
Grant a customer entitlement
- Choose Grant entitlement in the customer's details.
- Review and set the entitlement and expiration date, then confirm with Grant entitlement.
- Review the customer's entitlements after saving. This action does not create a new store purchase or bank payment.
Query a store transaction
- Choose Query a store transaction in the same customer's details.
- Supply the store purchase token and select the matching app and purchased product. They must match the real purchase; a store token is not a bank payment number.
- Choose Check and inspect the result. Submitting the request alone does not establish purchase success. Do not publish purchase tokens in public messages or screenshots.
Query a store transaction is different from rechecking a bank payment. Identify the payment source in the inquiry guide. Follow the refund guide to return funds; changing access alone is not a refund.
Multiple identifiers
Do not confuse InAppify's internal identifier, the app user identifier, and transaction numbers. Define a consistent identity policy across login, logout and reinstall, and coordinate it with the SDK. Mask personal data and tokens in screenshots and use private support tickets.