- Using Tags: this option is available for Address Capture, Email Verification and Phone Verification
- Using APIs: this option is available for all Loqate products and services
The main focus of this article is on Tag and API integrations, although we’ve included some information about
third-party integrations too, and a link out to the specific documentation.
Use cases
You know your business best, and what your requirements are. Here are a few examples though of possible use cases, and which of the Tag or API integration option might be best for each:Business Type | Specifics | Recommended option |
---|---|---|
Financial business | Strictly regulated | APIs |
Large ecommerce business | Requires considerable customisation | APIs |
Very small business | Uses simple web forms | Tag |
Small business | Uses cloud-based tools for creating forms | Tag or APIs |
Tag Integrations
The simplest way of setting up Address Verification, Email Verification and Phone Verification is by using the Tag method, which uses automatically-generated code snippets that you can insert into your website to set these services up. This method is designed for simple webforms, allowing you to set up standard configurations via your Loqate account. Pros:- Speed: you can get started quickly and easily
- Simplicity: there’s no need for technical know-how, as the functionality comes from our JavaScript solution and CSS
- Customisation: unlike API integrations, you don’t have as much control over how your integration works as it will always be based off our JavaScript and CSS
- Security: adding JavaScript to your website, while an effective way of adding new functionality, does come with some security considerations, and as such may not be appropriate for all circumstances. See our Security article for more information
API Integrations
All Loqate products can be integrated using our APIs, which are also available for Address Verification, Email Verification and Phone Verification for more flexible integrations. Pros:- Control: you’re not constrained by any existing integrations or ways of working, and you don’t need to rely on our preset JavaScript or CSS
- Customisation: you can shape your customer journey however you see fit
- Complexity: API integrations require technical knowledge and resources
- Speed: it takes time to implement and test API integrations