Google Customer Match connection
Explanation:
According to the Adobe documentation, some destinations require email addresses to be hashed using SHA256 algorithm before they can be used as target identities. These destinations include Facebook, Salesforce Marketing Cloud, Linkedin Matched Audiences, and Google Customer Match. Reference: https://experienceleague.adobe.com/docs/experience-platform/destinations/ui/destination-actions.html?lang=en#hashing-email-addresses

According to the Adobe documentation, Profiles > Browse is where a Real-Time CDP Business Practitioner can go to search for Profiles by Merge Policy in the UI. Profiles > Browse allows the user to search for individual profiles or groups of profiles based on various criteria, such as identity value, namespace, dataset, or merge policy. The user can also view the profile details and timeline for each profile. Reference: https://experienceleague.adobe.com/docs/experience-platform/profile/ui/browse.html?lang=en#searching-for-profiles

According to the Adobe documentation, I2 is a type of identity label that indicates data that is indirectly identifiable, such as hashed email addresses or phone numbers. These datasets can be shared per company policies, as they do not contain directly identifiable data, such as I1 or 11 labels. Reference: https://experienceleague.adobe.com/docs/experience-platform/data-governance/dule/dule-overview.html?lang=en#identity-labels

According to the Adobe documentation, attributes are fields that describe profile characteristics or traits, such as demographic information, preferences, or interests. Attributes can be dragged onto the segment builder canvas to define segment rules based on attribute values or ranges. In this case, the practitioner can drag an attribute that indicates the state of residence and set it to California. Reference: https://experienceleague.adobe.com/docs/experience-platform/segmentation/ui/segment-builder.html?lang=en#attributes

According to the Adobe documentation, DULE labeling is a framework that allows applying data usage labels (DULs) to data fields based on their usage category (Descriptive, Underlying, Linked, or Extracted). DULs can be applied at the schema level, which means they will propagate to all datasets and fields that use that schema. Reference: https://experienceleague.adobe.com/docs/experience-platform/data-governance/dule/dule-overview.html?lang=en#dule-overview