Persistent Consent Link for GDPR

  1. When you select the GDPR persistent consent link, a "postPromptUI": "postPromptUI" key is included in the JSON configuration and a persistent consent link <div> and styling is included in the tag:
    <div id="postPromptUI">
    
          <button role="button" on="tap:inmobi.prompt()">
    
            <svg style="height:20px">
    
                <g fill="none">
    
                  <g fill="#FFF">
    
                    <path
    
                      d="M16 10L15 9C15 9 15 8 15 8L16 7C16 7 16 6 16 6 16 5 15 4 14 3 14 2 13 2 13 3L12 3C12 3 11 3 11 2L11 1C11 1 10 0 10 0 9 0 7 0 6 0 6 0 5 1 5 1L5 2C5 3 4 3 4 3L3 3C3 2 2 2 2 3 1 4 0 5 0 6 0 6 0 7 0 7L1 8C1 8 1 9 1 9L0 10C0 10 0 11 0 11 0 12 1 13 2 14 2 15 3 15 3 14L4 14C4 14 5 14 5 15L5 16C5 16 6 17 6 17 7 17 9 17 10 17 10 17 11 16 11 16L11 15C11 14 12 14 12 14L13 14C13 15 14 15 14 14 15 13 16 12 16 11 16 11 16 10 16 10ZM13 13L12 13C11 13 11 13 9 14L9 16C9 16 7 16 7 16L7 14C5 14 5 13 4 13L3 13C2 13 1 12 1 11L3 10C2 9 2 8 3 7L1 6C1 5 2 4 3 4L4 4C5 4 5 3 7 3L7 1C7 1 9 1 9 1L9 3C11 3 11 4 12 4L13 4C14 4 15 5 15 6L13 7C14 8 14 9 13 10L15 11C15 12 14 13 13 13ZM8 5C6 5 5 7 5 9 5 10 6 12 8 12 10 12 11 10 11 9 11 7 10 5 8 5ZM8 11C7 11 6 10 6 9 6 7 7 6 8 6 9 6 10 7 10 9 10 10 9 11 8 11Z" />
    
                  </g>
    
                </g>
    
            </svg>
    
            PRIVACY
    
          </button>
    
        </div>
    
          </amp-consent>
    
    
  2. To change persistent consent styling, target #postPromptUi button in your CSS. This example adds the persistent consent button to the lower right of your page:
    #postPromptUI button {
               background: #368bd6;
               color: white;
               padding: 5px 15px;
               border: none;
               outline: none;
               display: flex;
               align-items: center;
               position: fixed;
               right: 0;
               bottom: 0;
               border-radius: 3px 0 0 3px;
               max-height: 30px;
               max-width: 110px;
               cursor: pointer;
    }
    

geo-location for CCPA or GDPR in EEA

An <amp-geo>  block will be included in the InMobi CMP AMP Tag if you configure GDPR (TCFv2) consent collection to apply only to EEA (European Economic Area) users, or if you have CCPA configured. A geoOverride key will also be present in the JSON configuration to properly customize the CMP based on the user's location.

  1. For these cases, an <amp-geo> component is included that defines the region(s) where CCPA and/or GDPR are applicable:
    <amp-geo layout="nodisplay">
      <script type="application/json">
        {
          "ISOCountryGroups": {
            "usca": ["preset-us-ca"]  // target California only
            // "us": ["us"]           // target entire US
          }
    } </script>
    </amp-geo>
    

    The amp-geo component provides country-level geolocation.

  2. Since AMP provides geo-location, the InMobi CMP will not use its internal geo-location functionality. The CMP will assume that the user has been successfully geo-located by the amp-geo component.

    This improves the AMP CMP performance by avoiding the check-consent HTTP call in areas where it is not necessary.

CCPA (USP) functionality

The check-consent API endpoint determines that CCPA applies for users geo-located to California (or the US). If no previously given USP string (indicating the user's Do-Not-Sell choice) has been set, the CMP will set the default USP string (as the regular web CMP does) and trigger the accept consentState.

The CCPA UI will not be shown automatically (as it does when GDPR applies), but instead, the user must click on the Do Not Sell link included on the page to make a do-not-sell choice. If the user chooses "DoNotSellMyInformation" in the UI, the consentState will be set to reject.

A link to bring up the CCPA UI needs to be included:

<!-- Privacy Disclaimer -->
      <p id="disclaimer_example">
        We use cookies and other data collection technologies to provide the
        best experience for our customers. You may request that your data not be
        shared with third parties here:
        <a role="button" on="tap:inmobi.prompt()">
          Do Not Sell My Personal Information </a>
      </p>
      <!-- Privacy Disclaimer -->

If desired, this link will be hidden when CCPA is not applicable using the amp-geo-group-XXclass which is automatically set by <amp-geo> as documented here.

On This Page

Last Updated on: 05 May, 2024