AWS entityresolution documentation change
Summary
Added procedural note about schema mapping creation and improved data format section readability.
Security assessment
These are general documentation improvements for workflow clarity, with no direct security implications.
Diff
diff --git a/entityresolution/latest/userguide/prepare-third-party-input-data.md b/entityresolution/latest/userguide/prepare-third-party-input-data.md index 9499c3a80..a728bf775 100644 --- a//entityresolution/latest/userguide/prepare-third-party-input-data.md +++ b//entityresolution/latest/userguide/prepare-third-party-input-data.md @@ -52,3 +52 @@ To subscribe to a provider service on AWS Data Exchange - * TransUnion TruAudience Transfer-less Identity Resolution & Enrichment - - * TransUnion TruAudience Transfer-less Identity Resolution + * TruAudience Identity Resolution & Enrichment @@ -87,5 +85 @@ LiveRamp | Yes | Ensure the following: -TransUnion | Yes | Ensure the following: - - * A [Unique ID](./glossary.html#unique-id-defn) exists for TransUnion Data Enrichment. - -###### Note +TransUnion | Yes | Ensure the following are a `string` type column in the input view: @@ -93,8 +87,2 @@ TransUnion | Yes | Ensure the following: -Pass along attributes are allowed to persist in input and output to TransUnion. Household E keys and HHID are specific to the client namespace. - * `Phone number` should be 10 digits, without any special characters such as spaces or hyphens. - * `Addresses` should be split into - * a single address line (combine address lines 1 & 2, if present) - * city - * zip (or zip plus4), without any special characters such as spaces or hyphens - * state, specified as 2 letter code 3 - * `Email addresses` should be in plaintext. + * [Unique ID](./glossary.html#unique-id-defn) is required and can be a CRM ID, a contact ID, a user ID or any unique ID. + * `Name` @@ -102,0 +91,13 @@ Pass along attributes are allowed to persist in input and output to TransUnion. + * `Address` + * `Street address1` and `Street address1` is combined into a single `Full address` line, if present. + * `City` is separated from the `Full address`. + * `Zip` (or `zip plus4`), without any special characters such as spaces, hyphens, or blanks. Use nulls if no data. + * `State` is specified as a 2-letter code in upper case. + * * `Phone` + * `Phone number` should be 10 digits, without any special characters such as spaces or hyphens. + * `Email addresses` is either plaintext or SHA256-hashed lower case strings. + * `Date of Birth` is in y`yyy-mm-dd` format. + * `Digital identifiers ` (Device IDs) can include IDs with hyphens (36-character length raw Device IDs/MAIDs/IFAs) and without hyphens (32 & 40-character long hashed Device IDs/MAIDs/IFAs). + * `IPV4` is a 32-bit IP address expressed in dotted decimal notation. For example: `192.0.2.1` + * `IPV6` is a 128-bit IP address expressed in hexadecimal notation, separated by colons. For example: `2001:db8:0000:0000:0000:0000:0000:0001` + * `MAID` (Mobile Advertising ID) is a unique, alphanumeric string assigned to a mobile device for advertising purposes. A MAID usually has 36 characters. For example: `a1b2c3d4-5678-90ab-cdef-EXAMPLE11111` @@ -107,0 +109 @@ Unified ID 2.0 | Yes | Ensure the following: + * Either `Phone number `or `Email addresses` is used in the schema, not both. @@ -114 +116 @@ Unified ID 2.0 | Yes | Ensure the following: -A specific email or phone number, at any specific time, results in the same raw UID2 value, no matter who made the request.Raw UID2s are created by adding salts from salt buckets which are rotated approximately once a year, causing the raw UID2 to also be rotated with it. Different salt buckets rotate at different times throughout the year. AWS Entity Resolution currently does not keep track of rotating salt buckets and raw UID2s, so it is recommended that you regenerate the raw UID2s daily. For more information, see [How often should UID2s be refreshed for incremental updates?](https://unifiedid.com/docs/getting-started/gs-faqs#how-often-should-uid2s-be-refreshed-for-incremental-updates) in the UID 2.0 documentation. +A specific email or phone number, at any specific time, results in the same raw UID2 value, no matter who made the request.Raw UID2s are created by adding salts from salt buckets which are rotated approximately once a year, causing the raw UID2 to also be rotated with it. Different salt buckets rotate at different times throughout the year. AWS Entity Resolution currently doesn't keep track of rotating salt buckets and raw UID2s, so it is recommended that you regenerate the raw UID2s daily. For more information, see [How often should UID2s be refreshed for incremental updates?](https://unifiedid.com/docs/getting-started/gs-faqs#how-often-should-uid2s-be-refreshed-for-incremental-updates) in the UID 2.0 documentation. @@ -120 +122,3 @@ If you already saved your third-party input data in a supported data format, you -To use AWS Entity Resolution, the input data must be in a format that AWS Entity Resolution supports. AWS Entity Resolution supports the following data formats: +To use AWS Entity Resolution, the input data must be in a format that AWS Entity Resolution supports. + +AWS Entity Resolution supports the following data formats: @@ -206,0 +211,2 @@ You can also choose **Create an IAM role** or have your administrator create the +You are now ready to create a schema mapping. For more information, see [Creating a schema mapping](./create-schema-mapping.html). +