Update AWS Entity Resolution integration doc for public ADX listing #378
Conversation
Customers can use the public ADX listing instead of the private offers
Use AWS Data Exchange screenshot from repo
Update instructions for processing both email and phone numbers
asloobq
changed the title
| @@ -98,9 +98,10 @@ Send your UID2 contact the AWS account ID that you'll use for your UID2 integrat | |||
|
|
|||
| ### Subscribe to UID2 on AWS Data Exchange | |||
|
|
|||
| Currently, you need to send your request via your UID2 contact. Then, you'll receive a custom invitation to the UID2 private service listing on AWS, as shown in the following example, and must accept the invitation to continue. | |||
| Visit the UID2 page on the AWS Data Exchange using this [link](https://aws.amazon.com/marketplace/pp/prodview-66zqls7iqsm6o?sr=0-4&ref_=beagle&applicationId=AWSMPContessa#offers) and click 'Continue to Subscribe'. | |||
There was a problem hiding this comment.
Visit the Unified ID 2.0 Identity Resolution page on the AWS Data Exchange and click Continue to Subscribe.
|
|
||
|  | ||
|
|
||
| <!-- To participate in UID2 on the Amazon Data Exchange Marketplace, subscribe to the UID2 service. See [Unified ID 2.0 Operator on AWS](https://aws.amazon.com/advertising-marketing/solutions/uid2/). --> |
There was a problem hiding this comment.
Can we delete this also? Looks as though it was a placeholder for this new content?
| @@ -138,7 +139,7 @@ When your initial account creation and setup are done, the next step is to creat | |||
| The following steps are a summary of actions you'll take in the AWS Entity Resolution user interface. For additional details and instructions, see [Creating a matching workflow with UID 2.0](https://docs.aws.amazon.com/entityresolution/latest/userguide/create-matching-workflow-provider.html#create-mw-uid) in the AWS Entity Resolution documentation. | |||
|
|
|||
| :::note | |||
| UID2 supports either email or phone number for UID2 generation. However, in AWS Entity Resolution, if both values are present in the schema mapping, the workflow uses the email and treats the phone number as a pass-through field. If your data includes a mix of emails and phone numbers, the best approach is to create a separate workflow for each, with separate schema mappings. In this scenario, go through the following steps twice—create one workflow for emails and a separate one for phone numbers. | |||
| UID2 supports both email and phone number for UID2 generation. However, in AWS Entity Resolution, if both values are present in the schema mapping, the workflow will duplicate each record in the output. One record will use the email for UID2 generation and the second record will use phone number. If you don't prefer this duplication of records in the output and if your data includes a mix of emails and phone numbers, the best approach is to create a separate workflow for each, with separate schema mappings. In this scenario, go through the following steps twice—create one workflow for emails and a separate one for phone numbers. | |||
There was a problem hiding this comment.
UID2 supports both email and phone number for UID2 generation. However, in AWS Entity Resolution, if both values are present in the schema mapping, the workflow duplicates each record in the output. One record uses the email for UID2 generation and the second record uses phone number. If your data includes a mix of emails and phone numbers and you don't want this duplication of records in the output, the best approach is to create a separate workflow for each, with separate schema mappings. In this scenario, go through the following steps twice—create one workflow for emails and a separate one for phone numbers.
(just use present tense instead of future. Also switched the sequence of the two list items)
| @@ -153,7 +154,7 @@ To create the matching workflow, first sign in to the AWS Management console, op | |||
| |0001|Test 1|test1@uidapi.com|1/1/90| | |||
| |0002|Test 2|test2@gmail.com|1/2/78| | |||
|
|
|||
| NOTE: There can be only **one** email or phone number field per record. If email is present, phone number is treated as pass-through. To process phone numbers, create a separate workflow. See details earlier in this section. | |||
| NOTE: If you have both email and phone numbers in the same record, the workflow will duplicate each record in the output. If you don't prefer this, then the best approach is to create separate workflow for each. See details earlier in this section. | |||
There was a problem hiding this comment.
NOTE: If you have both email and phone numbers in the same record, the workflow duplicates each record in the output. If you don't want this, the best approach is to create a separate workflow for each. See details earlier in this section.
(again, just using present tense plus fixing "don't prefer" wording)
asloobq
deleted the
aaq-UID2-2162-update-entity-resolution-data-exchange
branch
1] Customers can use the public ADX listing instead of the private offers
2] Updated guidance on generating email and phone numbers in the same record