Introduction

Purpose

Touchpoints are used to enhance the behavior of our components in a variety of ways:

• Enable address validation when custom fields are used for addresses
• Enable the storage of the validation status in a destination field on the record itself
• Enable passive validation of address, email and phone fields when records are created from external sources, such as Web-to-Lead/Case
• Allow their integration within your own custom Lightning Web Components
• Enrich your records with additional data

Types

There are two types of Touchpoint. Choose the one that fits your use case:

• Bound - use with the EDQ Record Detail component. This Touchpoint type should be linked to a specific Salesforce object and field.
• Unbound - use with our Flows components or your own custom Lightning Web Components which aren't strictly tied to a specific Salesforce object.

The subsequent pages of this section walk you through how to configure Bound Touchpoints in a variety of cases, followed by a summary of how Unbound Touchpoints configuration differs.

Additional data

Our Validation and Enrichment APIs offer a host of additional data to compliment your addresses, emails and phone numbers. For example, you can find out a household's estimated income level or an address's geographical coordinates, an email's domain type, or a phone number's type or operator name. Touchpoints are integral to enabling this additional data.

The available data can be broken down into the groups below. The subsequent pages of this section cover how to configure each group.

• Address data
• Email data
• Phone data