Persona logoPersona Help Center
ArticlesCommunityAcademyDeveloper Docs
Menu icon

Articles

Getting started
Dynamic Flow (Inquiries)
Verifications
Accounts
Transactions
Reports
Introduction
Key Concepts
Using Reports
Features
Cases
Workflows
Graph
Lists
Marketplace and 3rd-Party Integrations
Team and permissions
For end users
Security, privacy, and compliance

Get help now

Submit a request
Reports
Introduction
Key Concepts

Reports Overview

About Reports

Enrich identity profiles

Reports provide additional information about an end user beyond what they submit directly in an Inquiry. Inquiries collect information directly from an individual, while Reports pull information from authoritative data sources. These authoritative data sources include credentials, attestations, records, logs, investigations, and analyses. Adverse Media Reports may also include articles.

Stay compliant, prevent fraud

Organizations who use Reports through Persona often need additional information about an individual before completing their identity verification process. Common use cases include KYC/AML compliance and fraud prevention.

Report types

Persona offers many types of Reports, including:

If there is a Report type that you'd like to use and don't see listed here, please contact our support team. We'd love to chat.

Get started

Reports are available to customers on a paid plan. Pricing for each Report varies depending on the Report type and the plan that your organization is on.

To get started using Reports, please reach out to your Customer Success Manager or contact the Persona support team.

Report exports

  • Reports can be exported as CSV files allowing you to explore details about individual reports whose aggregate metrics are displayed on the Reports Overview Analytics page.
  • You can answer questions like:
    • How many reports were created within X?
    • How many reports are currently recurring?
    • How many and how often do watchlist reports return a match?
    • How often do Adverse Media reports return a match?
    • How many identity matches does a watchlist report with hits tend to return?
    • How many articles are associated with an identity match in Adverse Media reports?
    • Which email addresses and domains tend to be more suspicious?
    • Which watchlist or adverse media entities tend to get a lot of hits?
  • Things to note
    • There is an export limit of 10k reports at a time
    • The reports being exported will match what is visible on the dashboard (e.g. if filters are applied, only reports that match the filters will be exported).
      • Redacted reports will be listed in the export, but with redacted data removed
    • Once the export is complete, an email notification will be sent, and the file can be downloaded from the Exports page on dashboard.
  • Columns
    • Identifiers
      • Report ID
      • Report Link (link to the report on your dashboard)
      • Report Template ID
      • Reference ID
    • Columns for each export type

      • Report Export (report_summary.csv) should have the following fields. One row per report.

        1. ID (the report token) (type: identifier)
        2. Report Link (type: identifier)
        3. Report Template (type: identifier)
        4. Reference ID (type: identifier)
        5. Status (type: status, possible values: pending, ready, errored, redacted)
        6. Tags (type: list)
        7. Created At (type: timestamp)
        8. Last Run At (updated at, relevant for recurring reports) (type: timestamp)
        9. Type (type: report type, possible values: all report types)

      • Watchlist Export 1 (report_watchlists.csv) should have the following fields. One row per report.

        1. ID (the report token) (type: identifier)
        2. Report Link (type: identifier)
        3. Report Template (type: identifier)
        4. Reference ID (type: identifier)
        5. Status (type: status, possible values: pending, ready, errored, redacted)
        6. Tags (type: list)
        7. Created At (type: timestamp)
        8. Last Run At (updated at, relevant for recurring reports) (type: timestamp)
        9. Matched (whether or not there was a match) (type: boolean)
        10. Recurring (type: boolean)
        11. Recurrence Cadence (Days) (type: integer)
        12. Hit Count (type: integer)
        13. Dismissed Hit Count (type: integer)
        14. Total Hit Count (type: integer)

      • Watchlist Export 2 (report_watchlists_hits.csv) should have the following fields. One row per hit.

        1. ID (the report token) (type: identifier)
        2. Report Link (type: identifier)
        3. Report Template (type: identifier)
        4. Reference ID (type: identifier)
        5. Status (type: status, possible values: pending, ready, errored, redacted)
        6. Tags (type: list)
        7. Created At (type: timestamp)
        8. Last Run At (updated at, relevant for recurring reports) (type: timestamp)
        9. Primary Names (type: list)
        10. Birthdates (type: list)
        11. Sexes (type: list)
        12. Aliases (type: list)
        13. Titles (type: list)
        14. Emails (type: list)
        15. Phone Numbers (type: list)
        16. Nationalities (type: list)
        17. Birthplaces (type: list)
        18. Residencies (type: list)
        19. Citizenships (type: list)
        20. Sanctions (type: list)
        21. Warnings (type: list)

      • Adverse Media Export 1 (report_adverse_media.csv) should have the following fields. One row per report.

        1. ID (the report token) (type: identifier)
        2. Report Link (type: identifier)
        3. Report Template (type: identifier)
        4. Reference ID (type: identifier)
        5. Status (type: status, possible values: pending, ready, errored, redacted)
        6. Tags (type: list)
        7. Created At (type: timestamp)
        8. Last Run At (updated at, relevant for recurring reports) (type: timestamp)
        9. Matched (type: boolean)
        10. Recurring (type: boolean)
        11. Recurrence Cadence (Days) (type: integer)
        12. Hit Count (type: integer)
        13. Media Count (type: integer)

      • Adverse Media Export 2 (report_adverse_media_hits.csv) should have the following fields. One row per hit.

        1. ID (the report token) (type: identifier)
        2. Report Link (type: identifier)
        3. Report Template (type: identifier)
        4. Reference ID (type: identifier)
        5. Status (type: status, possible values: pending, ready, errored, redacted)
        6. Tags (type: list)
        7. Created At (type: timestamp)
        8. Last Run At (updated at, relevant for recurring reports) (type: timestamp)
        9. Name (type: string)
        10. Aliases (type: list)
        11. Birthdates (type: list)
        12. Relevance (type: list)
        13. Countries (type: list)
        14. Categories (type: list)
        15. Media Links (type: list)

      • Email Risk Export 1 (report_email_address.csv) should have the following fields. One row per report.

        1. ID (the report token) (type: identifier)
        2. Report Link (type: identifier)
        3. Report Template (type: identifier)
        4. Reference ID (type: identifier)
        5. Status (type: status, possible values: pending, ready, errored, redacted)
        6. Tags (type: list)
        7. Created At (type: timestamp)
        8. Last Run At (updated at, relevant for recurring reports) (type: timestamp)
        9. Matched (whether or not there was a match) (type: boolean)
        10. Email Address (type: string)
        11. Suspicious (type: boolean)
        12. Email Reputation (type: low, medium, high)
        13. Email Domain Reputation (type: low, medium, high)
        14. Spam (type: boolean)
        15. Blocklisted (type: boolean)
        16. Reference Count (type: integer)
        17. Deliverable (type: boolean)
        18. Free Provider (type: boolean)
        19. Domain Age (days ago) (type: integer)
        20. First Seen (days ago) (type: integer)
        21. Disposable (type: boolean)
        22. Domain (type: string)
        23. Domain exists (type: boolean)
        24. Valid Mx (type: boolean)
        25. Recent Malicious Activity (type: boolean)
        26. Recent Email Leak (type: boolean)

      • Politically Exposed Person Export 1 (report_politically_exposed_person.csv) should have the following fields. One row per report.

        1. ID (the report token) (type: identifier)
        2. Report Link (type: identifier)
        3. Report Template (type: identifier)
        4. Reference ID (type: identifier)
        5. Status (type: status, possible values: pending, ready, errored, redacted)
        6. Tags (type: list)
        7. Created At (type: timestamp)
        8. Last Run At (updated at, relevant for recurring reports) (type: timestamp)
        9. Matched (type: boolean)
        10. Recurring (type: boolean)
        11. Hit Count (type: integer)

      • Politically Exposed Person Export 2 (report_politically_exposed_person_identity_matches.csv) should have the following fields. One row per hit.

        1. ID (the report token) (type: identifier)
        2. Report Link (type: identifier)
        3. Report Template (type: identifier)
        4. Reference ID (type: identifier)
        5. Status (type: status, possible values: pending, ready, errored, redacted)
        6. Tags (type: list)
        7. Created At (type: timestamp)
        8. Last Run At (updated at, relevant for recurring reports) (type: timestamp)
        9. Name (type: string)
        10. Aliases (type: list)
        11. Birthdates (type: list)
        12. Locations (type: list)
        13. Sex (type: string)
        14. Positions (type: list)
        15. Associates (type: list)
        16. Match Types (type: list)

      • Phone Number Export 1 (report_phone_number.csv) should have the following fields. One row per report.

        1. ID (the report token) (type: identifier)
        2. Report Link (type: identifier)
        3. Report Template (type: identifier)
        4. Reference ID (type: identifier)
        5. Status (type: status, possible values: pending, ready, errored, redacted)
        6. Tags (type: list)
        7. Created At (type: timestamp)
        8. Last Run At (updated at, relevant for recurring reports) (type: timestamp)
        9. Matched (type: boolean)
        10. Phone Number (type: string)
        11. Phone Type (type: string)
        12. Phone Carrier (type: string)
        13. Risk Level (type: string)
        14. Risk Recommendation (type: risk recommendation, possible values: block, allow, flag)
        15. Risk Score (type: integer)
        16. Risk Sim Swap (type: string)

Disclaimer

Persona is not a consumer reporting agency and the services (and the data provided as part of its services) do not constitute a ‘consumer report’ for the purposes of the Federal Fair Credit Reporting Act (FCRA). The data and reports we provide to you may not be used, in whole or in part, to: make any consumer debt collection decision, establish a consumer’s eligibility for credit, insurance, employment, government benefits, or housing, or for any other purpose authorized under the FCRA. If you use any of any of our services, you agree not to use them, or the data, for any purpose authorized under the FCRA or in relation to taking an adverse action relating to a consumer application.