---
title: "US phone numbers"
date: "2019-02-06T09:35:45+00:00"
summary: "Find and format US phone numbers correctly with our guide for Acquia Web Governance scans. Improve consistency across your website."
image:
type: "page"
url: "/web-governance/us-phone-numbers"
id: "fe232bfe-7722-44d0-84a7-b5b1696c7e88"
---

Introduction
------------

This article provides information on how to add a pre-made US Phone Number policy to the Web Governance scan.

Instructions
------------

How to add a US phone number policy.

1.  From the Web Governance _Domain Overview_, click **Select Domain**. The _Domain Overview_ page opens.
    
    ![The location of the Select Domain button on the landing page.](https://acquia.widen.net/content/3f9af850-740d-47b4-a5b5-3de73f77ad39/web/Mon_LandingPage-SelectDomain.png)
    
2.  Click **Open** on the same row as the domain name. 
    
    ![The location of the Open button on the same row as a domain on the Domain Overview page.](https://acquia.widen.net/content/f6593aa0-6ed8-4fbb-a0ba-2eff48d52d63/web/Mon_Domain-DomainOverview-OpenButton.png)
    
    The _Dashboard_ for the domain opens.
    
    ![The Domain Dashboard with sections for several active modules.](https://acquia.widen.net/content/1f5bcdac-5405-4063-afdc-fabbd0811e16/web/WebGov_DomainDashboard-LandingPage.png)
    
3.  Click the Global Policies Overview button (mallet icon) on the top menu bar.
    
    ![The Global Policy Overview button on the top page menu bar.](https://acquia.widen.net/content/773c313e-353d-4f74-8968-823b4fd53480/web/WebGov_MainMenu-GlobalPolicyOverview.png)
    
    Alternatively, click on the header of the _Content Policies_ section.
    
    The _Global Policies_ page opens.
    
    ![The Global Policy Overview button on the top page menu bar.](https://acquia.widen.net/content/773c313e-353d-4f74-8968-823b4fd53480/web/WebGov_MainMenu-GlobalPolicyOverview.png)
    
4.  Click **Add new policy**.
    
    ![The location of the Add New Policy button on the top right of the page in line with the page header.](https://acquia.widen.net/content/878672ed-926a-4686-848b-462ccc2ec8c9/web/WebGov_Policies-AddNewPolicyButton.png)
    
    The _New_ _Policy_ page opens.
    
    ![Mon_Policies-NewPolicy-List.png](https://acquia.widen.net/content/44e17ffb-5ea7-4b7b-8a28-08aa47e0660a/web/Mon_Policies-NewPolicy-List.png)
    
5.  Click **Create your own Policy**. See below for examples.
    
    For more information, see the user guide article:
    
    [Create a custom policy](https://docs.acquia.com/acquia-optimize/admin/setup/configure?cid=811e7).
    
6.  Assign rule operators. See the _Rule operators_ section in this document for a list of available rule operators.
7.  Assign rules. See the _Rules_ section of this document for a list of available rules.
8.  Click **Save** to save the changes. A dialog box opens.
    *   In the dialog box, enter the policy **Name** (required) and **Note** if needed and then click **Save**.
    *   From the options at the top of the page, select **+Add rule to the policy**. Repeat the steps above to add as many rules as needed.
    *   Click **Save**. The _Policy List_ is open and the new policy is present. A Policy scan begins automatically.

Rule operators
--------------

This section provides a list of available rule operators.

*   **Starts with**: Policy will search for any snippet starting with the inserted text.
*   **Contains**: Policy searches for any instances of the inserted text (single word).
*   **Contains words**: Policy searches for multiple words. Use commas to separate the words.
*   **Contains sentence**: Policy searches for any instances of the inserted sentence or text.
*   **Ends with**: Policy will search for any snippet ending with the inserted text.
*   **Equal**: Policy searches for an exact match for the inserted text or value. Example: “Monsido” - match. “About Monsido” - no match.
*   **Regex**: Use regular expressions to define what should be searched for.
    
    Note
    
    Regular Expressions in source-code exclusions are not 100% compatible with Web Governance Policies. The languages are different (Java and Ruby).
    
*   **Conforms with**: Use regular expressions to define the correct structure or form of the inserted value.
*   **Less than**: Find any results less than the inserted value.
*   **Less than or equal**: Find any results less than or equal to the inserted value.
*   **Greater than**: Find any results greater than the inserted value.
*   **Greater than or equal**: Find any results greater than or equal to the inserted value.
*   **(Meta header) Date age greater than**: Find meta tags older than the inserted value. Choose the time interval that matches the way your meta tag dates are written.
*   **(Meta header) Date age less than**: Find meta tags younger than the inserted value. Choose the time interval that matches the way your meta tag dates are written.
*   **CSS selector**: Policy will search for the inserted CSS selector.

Rules
-----

This section provides a list of available rules.

*   **Page HTML**: Search for text in the entire domains html.
*   **Page URL**: Set a rule for internal page URLs.
*   **Text**: Search for text excluding CSS and HTML tags.
*   **Page title**: Search for text in the page title (title is not the header).
*   **Page title length**: Define when the rule should apply for the title.
*   **Heading text**: Search for text in headers (h1,h2,h3,h4,h5,h6).
*   **Heading text length**: Define when the rule should apply header texts.
*   **Meta header**: Search for meta header tags, that matches query.
*   **Meta header length**: Define when the rule should apply for meta headers.
*   **Link text length**: Define when the rule should apply for link texts.
*   **External link count**: Define when the rule should apply for external links.
*   **File size**: Search files across selected domains.
*   **Image size**: Search for images across selected domains.
*   **Image text**: Search for images with this name.
*   **Image text length**: Define when the rule should apply for image texts.
*   **Readability level**: Search for text that is in compliance with a school degree.

Custom examples
---------------

The Policies module can be used to find US phone numbers that are formatted in different ways.

A phone number policy can be set up to instruct the scan to locate US telephone numbers that are NOT formatted in the following way: **(123) 567-7890**. Below are some examples of numbers that violate the policy:

*   123-456-7890
*   123 456-7890
*   123 456 7890
*   123-4567890

For more information, see the user guide article:

[Create a custom policy](https://docs.acquia.com/acquia-optimize/admin/setup/configure?cid=811e7).

Note

Regular Expressions in source-code exclusions are not 100% compatible with Web Governance Policies. The languages are different (Java and Ruby).

Additional resources
--------------------

If the policy you need is difficult to create, contact [Support](mailto:support@monsido.com) for assistance.