Google Places API
Pingtree integrates with the Google Places API to provide real-time address autocomplete and validation on your landing pages and form flows. This helps users enter accurate addresses quickly, reduces form abandonment, and improves the quality of address data in your leads.What is the Google Places Integration?
When enabled, Pingtree injects the Google Maps JavaScript SDK (with the Places library) into your campaign pages. Address input fields are enhanced with a live autocomplete dropdown, allowing users to select a verified address from Google’s global database. This eliminates typos, invalid ZIP codes, and undeliverable addresses before the lead is submitted.How It Works
- When a campaign page loads, Pingtree checks whether the Google Address API integration is enabled for that campaign and whether your account has a sufficient balance.
- If both conditions are met, Pingtree injects the following script into the page:
- Address input fields on your form are connected to the Places Autocomplete service, which queries Google’s database as the user types and presents matching address suggestions.
- When the user selects an address, the individual components (street, city, state, ZIP, country) are automatically populated into the relevant form fields.
Enabling the Integration
Configuration Path:Campaign > Single View > Integrations Tab > Google Address API
Prerequisites
- Your advertiser account must have billing enabled and a positive wallet balance. If the account balance is zero or billing is disabled, the Google Places script is not injected and the form will behave as a standard text input.
- A Google Cloud project with the Places API and Maps JavaScript API enabled.
Configuration Options
| Option | Description |
|---|---|
| Enable Integration | Toggle to activate Google Places autocomplete for all landing pages and form flows in this campaign. |
| API Key | Your Google Cloud API key with Places API access. If left blank, Pingtree uses the platform’s shared key. It is strongly recommended to provide your own key for production campaigns to avoid rate-limit sharing. |
Note: Changes to the integration settings are applied to the campaign and all associated Webflow2 variations automatically.
Getting a Google API Key
1. Open Google Cloud Console
Go to console.cloud.google.com and sign in with your Google account.
2. Create or Select a Project
Create a new project or select an existing one from the project dropdown at the top of the page.
3. Enable the Required APIs
Navigate to APIs & Services > Library and enable both:
- Maps JavaScript API
- Places API
4. Create an API Key
Go to APIs & Services > Credentials, click Create Credentials, and select API key. Copy the generated key.
5. Restrict the Key (Recommended)
Under the key’s settings, restrict it by:
- Application restriction: HTTP referrers — add your campaign domain(s).
- API restriction: Restrict to Maps JavaScript API and Places API only.
Use Cases
- Lead Quality: Ensure address fields contain real, deliverable addresses rather than free-text guesses.
- Faster Form Completion: Autocomplete reduces how much users have to type, lowering form abandonment rates.
- Accurate ZIP/State Data: Automatically populate city, state, and ZIP from the selected address, eliminating mismatches between fields.
- Downstream Accuracy: Cleaner address data improves matching rates with lenders, buyers, and CRM systems that rely on address verification.
Tips
- Use your own Google API key in production to avoid rate limits that could affect the autocomplete experience.
- Restrict your API key to your campaign domains to prevent unauthorized usage and unexpected billing on your Google Cloud account.
- Google Places API requests are billed by Google on a per-request basis. Monitor your Google Cloud billing dashboard to track usage.
Tip: The Google Places integration works alongside Pingtree’s Webflow2 form builder. Address fields in your form steps are automatically wired to the autocomplete service when the integration is active — no custom code is needed.