In this article, you’ll learn to setup Address Verification
Before You Begin…
Please review this article on LeadsHook Data Validation & Verification
Address verification will only work with a custom field type: address.
PLEASE ACTIVATE YOUR DECISION TREE BEFORE TESTING
How to Setup Address Verification
For address verification, we provide an integration with Google Places API.
This feature provides the ability for your decision-tree users to simply type their address. At the moment, LeadsHook reaches out to Google to start providing addresses as shown below…
STEP 1: Please go to https://accounts.google.com and login with your preferred email address to create your API access at Google.
Or create a new google account.
STEP 2: After login please follow these steps…
Click the “9-dots” icon
Click “Even more from Google”
And click “Even more from Google”…
STEP 3: You’ll end up on Google’s Products page…
STEP 4: Scroll down (you might have scroll for a screens-lengths) until you see ‘”For business”
Click the “Google Cloud Platform” as shown below…
STEP 5: A new tab or window will open and you’ll end up on https://cloud.google.com/ as shown below…
STEP 6: Create a NEW project
Click the down arrow.
Click “NEW PROJECT”
STEP 7: New Project Details
Enter a name for your project
STEP 8: Click the hyperlinked name of the project you created….
STEP 9: Create APIs
Your project name will appear shown below
Click “Enable APIs and get credentials like keys
STEP 10: Click “Enable APIS AND SERVICES”…
STEP 11: Under Maps Section, Click “VIEW ALL”
STEP 12: Open Both of These 2 APIs in their own tabs.
- PLACES API
STEP 13: Click “ENABLE” for BOTH APIs
Please note: You’ll be using the Place autocomplete feature (highlighted in yellow).
STEP 14: Create Credentials
- Click “Credentials”
- Click “Create Credentials”
- Create credential
- Click “API key”
STEP 16: Your API key is automatically created. Copy and paste this API Key or copy/paste it when you need to use it.
- You’ll see it in the dialog box and also in the grid in the background. This is your API key that you’ll use in LeadsHook.
- Click “RESTRICT KEY”. We want to click restrict key as a security precaution. It’s not necessary but is highly recommended.
STEP 17: Restrict Usage of API Key
- Add a Name for this API Key
- Select Https referrers
- Add http://*.leadshook.io/*
- Click “Save”
STEP 18: You should see the restrictions are shown below.
STEP 19: For all new accounts, Google gives a credit of $500 (or did when this article was created).
Please click “Billing”
STEP 20: Please click “ADD PAYMENT METHOD” and enter your credit card details.
STEP 21: Set alerts so you are notified of your usage.
- Click “Budgets & alerts”
- Click “Create budget”
STEP 22: Set your budget
- Add a name for your budget
- Enter a monthly spend for which you’d like to get notified
- Google will automatically send you notifications when you’ve spent 50%, 90% and 100% of the budget figure from step 2. Add more steps or remove as needed. You can use percentages over 100% as well.
- Press “Save”
Woohoo! Google part is DONE!
STEP 23: Log into LeadsHook
- Click “Admin”
- Select “Integrations”
- Click “Google Places”
STEP 24: Your Google API keys…
- Click “Add” to add a new API Key
- All of your API keys will be listed here. L
Please Note: LeadsHook allows you to add as many API keys as you want because the API is assigned at the Decision Tree level. In case you are managing traffic for numerous clients or want to see costs correctly aligned to your projects.
STEP 25: Add API Key
- Add a name (such as a client, project, business or domain)
- Add the API key from STEP 16.
- Click “Save”
You API key will be displayed as shown in STEP 24
STEP 26: Assign or Use Your API Key in a Decision Tree
You must be in editing your decision tree in the canvas.
- Click the ‘Gear’ icon
- Select Data Validation
STEP 27: Use Your Google Places Integration
- Click “Address” checkbox
- From the Dropdown select the API integration you want to use for your decision tree.
STEP 28: Test
ACTIVATE YOUR DECISION TREE
Please ensure your form has an address custom field OR you are using an address node.
You can use the same integration in as many decision trees as you want.