If you're using the EDQ Record Detail component to validate emails, it's possible to make use of the Response objects which are returned from our Experian Email Validation API. The result and metadata objects contain additional information about the returned email, such as confidence level, verbose detail and domain type. This is enabled through configuration of Touchpoints.

Setting up Touchpoints to return additional data

  1. Click on App Launcher. Type EDQ Global Settings in the Quick Find box, and select it.

  2. Select Touchpoints from the left-hand menu.

  3. Click the New button found in the top right to create a new Touchpoint configuration for your Salesforce object.

  4. Choose Email for the Touchpoint type, then select your object and email field within that object.

  5. Activate the optional Passive validation feature should you wish to use it.

    New Email Touchpoint

With your email field configured you can now decide which metadata you want to retrieve and which fields on your object you want this to be mapped to.

You can now create as many mappings as you require. For each mapping you first select from the list of possible metadata elements from our API and then select a field from the Salesforce object chosen for your Touchpoint. For a full list of attributes and their descriptions refer to our Email Validation API documentation.

Email metadata mappings

Unwanted mappings can be removed using the cross icon to the right of the mapping and further new ones added using the New metadata mapping button.

Once all the mappings have been configured, click the Save button to save your Touchpoint configuration.

Testing your Touchpoint mappings

  1. Make sure all the fields that were mapped in your Touchpoint have been added to the Page Layout for the relevant Salesforce object.
  2. Edit a record for the Salesforce object you want to test and try to validate an email address using an EDQ component.
  3. If the validation is successful, check that the mapped fields are populated with the additional data you were expecting.

Handling of missing metadata

If you mapped an attribute which doesn't exist for the validated email address, the mapped object field won't be populated when an address is returned following validation.

To make this visible to administrators for debugging purposes we utilize our package's frontend logging which appears in your browser's Developer Console. Errors will be logged at the following levels.

  • INFO level when an attribute is missing for the validated email address