Customers

The Customers page shows user-level data from 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, Account, and Ad campaign filters.
• Purchase-state filters.
• Test user filters.

Use Date range to include customers first seen on either selected date or any date between them. 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.

​

Review attribution details

Use the Attribution section to confirm how PNLight selected a source for the customer.

• Attributed means PNLight selected one source for the customer.
• Waiting means PNLight has source signals, but it is still waiting for the preferred source.
• No attribution means no source could be confirmed.
• Needs review means multiple sources conflict.

The section can show the matched campaign, ad set, and ad when that data is available. It also lists each checked source, such as PNLight click attribution or AppsFlyer attribution.

​

Review the customer timeline

Use the timeline filters to focus on subscription events, app events, system events, or postbacks. For postbacks, the timeline can show:

• Custom postback HTTP status and destination host.
• Facebook Conversions API delivery status.
• Google Data Manager delivery status.
• Delivery result, such as delivered, failed, or skipped.
• Skip or failure reason when PNLight has one.
• Facebook Dataset ID and mapped event name for Facebook Conversions API attempts.

Open the project Events page when you need the full delivery attempt details across users.