Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

    Sign In
    • Home
    • Connecting Tools
    • API

    Understanding "Needs Review" Statuses

    Contact Us

    If you still have questions or prefer to get help directly from an agent, please submit a request.
    We’ll get back to you as soon as possible.

    Please fill out the contact form below and we will reply as soon as possible.

    • Getting Started
      New here Configuration and Connection Guides
    • Academy and Learning Resources
      Learning Resources - Best Practices Academy
    • User Guides
      AI What's New Platform Status and General FAQs Homepage The Dashboard Location Hub Review Management Messages Social Locator + Pages Analytics Directories Mobile App 'Near Me' 360
    • Connecting Tools
      Connection Troubleshooting API
    • Org Settings
      Users Billing API Keys Webhooks
    + More

    Table of Contents

    Why Does a Listing or Location Need Review? Needs Review Statuses and Resolution Guide

    The "Needs Review" (NR) status in our system indicates that a location or a listing is encountering an issue that requires manual intervention or inspection to proceed. This status is crucial for maintaining data accuracy and ensuring successful synchronizations with external directories.

    Understanding the different types of NR and the necessary actions will help you resolve these issues efficiently.


    Why Does a Listing or Location Need Review?

    The issues can be broadly categorized into:

    Location-Specific Issues: Problems related to the core location data itself, preventing the start of the synchronization process.

    Listing-Specific Issues: Problems encountered when trying to interact with a specific external listing (e.g., publishing, updating, or claiming).


    Needs Review Statuses and Resolution Guide

    The following table details the possible Needs Review statuses, their reasons, and the steps required for resolution:

     

    Needs Review Type

    Category

    Reason for the Status

    What Should Be Done

    CANNOT_START_SYNC

    Location Specific

    The location has insufficient or incomplete data, or it has just been created, preventing the start of the sync process.

    Client action required

     

    1. Check Location Data: Ensure all mandatory fields (Name, Address, Phone, etc.) are filled. 

    2. Review Location Status: Confirm the location is fully set up and activated in the system.

    NORMALIZATION_FAILED

    Location Specific

    The location's address or core details cannot be standardized or verified (e.g., an unresolvable or ambiguous address).

    Client action required

     

    1. Verify Address: Check the address against reliable mapping services (e.g., Google Maps). 

    2. Correct Address: Update the address to a standardized, verifiable format.

    CLEANSING_FAILED

    Location Specific

    An external data source (e.g., an API endpoint) explicitly reported that it cannot process or "cleanse" the provided location data, typically with an INVALID_DATA action.

    Client action required

     

    1. Review Error Details: Examine the specific error message from the directory. 

    2. Adjust Data: Modify the location data based on the directory's requirements and retry.

    See full guide here

    FIELD_INVALID

    Listing Specific

    One or more fields in the location data contain invalid data (e.g., a name with too many special characters, an improperly formatted phone number).

    Uberall review & action issues

     

    1. Inspect Invalid Fields: Review the location data fields flagged for being invalid. 

    2. Correct Data: Edit the field(s) to adhere to data standards and retry the sync.

    MANDATORY_FIELD_MISSING

    Listing Specific

    A field required by a specific directory (even if optional elsewhere) is missing from the location data (e.g., a description is mandatory for a directory).

    Client action required

     

    1. Identify Missing Field: Determine which field is required by the directory. 

    2. Update Location Data: Fill in the required field for the location.

    CONFLICT

    Listing Specific

    A conflicting listing exists in the system with the exact same identifying information (e.g., same listing ID and URL), indicating a potential duplicate active listing.

    Uberall review & action issues

     

    Investigate Duplicates: Find the other active listing with the identical details. 

    REJECTED

    Listing Specific

    An external directory responded with an unexpected, unhandled rejection error that prevents an update or creation. This may or may not be related to a specific field.

    Uberall review & action issues

     

    1. Analyze Directory Response: Review the exact error message from the directory (e.g., "rejected name because xyz"). 

    2. Escalate (if needed): If the rejection reason is unknown or unhandled by our code, a developer may need to update the system to handle this new rejection type.

    CATEGORY_NOT_MATCHED

    Listing Specific

    The category associated with the location is not successfully matched or accepted by the target directory, thus preventing the listing from being updated.

    Uberall review & action issues

     

    Uberall regularly reviews category mapping. If you see this issue, you can report it to Uberall.

    NOT_MY_LISTING

    Listing Specific

    The customer or user has manually flagged the current external listing as "not my listing," indicating an incorrect match or association.

    Uberall review & action issues

     

    Contact Uberall to resolve this case (these are added on client request and are rare)

    SUGGESTED_LISTING

    Listing Specific

    The system or the client has suggested this listing as a potential match or a possible duplicate that needs manual verification.

    Uberall review & action issues

     

    1. Manual Inspection: Review the suggested listing and the associated location data. 

    2. Uberall process these to Accept or Reject the matches. These are only edge cases where further review are needed.

    CLEANSING_REQUIRED

    Listing Specific

    The specific directory requires an additional data "cleansing" step before it can accept the location data, which our system is not currently performing automatically.

    Uberall review & action issues

     

    Uberall is still busy processing cleansing. These will be cleared in 24-48 hours, unless the cleansing or normalisation have failed. 

    review status understanding

    Was this article helpful?

    Yes
    No
    Give feedback about this article

    Related Articles

    • Google Attributes With The API
    • Basic Single Sign-On
    • Locations File Data Input and Type
    • SAML 2.0 Single Sign-On
    • API - Rate Limits
     

    Copyright 2025 – uberall.

    Expand

    English (US)
    US English (US)
    FR French
    DE German
    ES Spanish
    IT Italian
    JP Japanese