Skip to main content
The Customers page shows user-level data collected through the SDK and connected integrations.

​
Customer list

Use the customer list to review:
  • User ID.
  • Subscription status.
  • Autorenewal status.
  • Total spent.
  • First seen date.
  • Ad network and campaign filters.
  • Purchase-state filters.
  • Test user filters.
Use Test users → Test only when you want to isolate QA traffic from production users.

​
Test users

Open a customer profile when you need to mark one SDK user ID for testing.
  • Add test user marks the current SDK user ID as a test user.
  • Remove from test users restores normal targeting and reporting behavior for that user.
  • Test users are useful for Remote UI QA, release checks, and one-off purchase debugging.

​
Customer details

Open a customer profile to review the timeline for a single user. Use it when you need to answer questions such as:
  • Did the SDK create a user ID?
  • Did a purchase event arrive?
  • Was the user attributed to a source?
  • Which app events did the SDK send?
  • Did Remote UI capture protection affect this user?
  • Is this user currently matched to a test device?
  • Were postbacks sent for this user?
The profile can also show attribution resolution, attribution debug payloads, and external attribution records. Use them when a campaign, network, ad group, or provider identifier does not match what you expected.
Customer data depends on SDK initialization. If a user is missing, check that the app build uses the correct SDK token.