To find your Google API key, open the Google Cloud Console, select or create a project, enable the API you need, then generate a key under Credentials and restrict it before anyone on your team uses it. For most B2B revenue teams, the key is only one piece of the setup, so this guide also covers when a key is the wrong credential.

What a Google API Key Does for a B2B Team
A Google API key is a unique identifier that ties requests to a Google Cloud project so usage can be tracked and billed. It does not prove who a user is. It simply tells Google which project is making a call.
For a small B2B sales or marketing team, that matters when you run scripts or internal tools that call public Google services, such as cleaning company addresses in your CRM before territory assignment or checking whether a prospect's business location exists before a rep is routed to it.
Related: Data Science Myths for Small B2B Marketing Teams
When an API Key Is Enough, and When It Is Not
Google uses two different kinds of credentials, and mixing them up is the most common setup error for revenue operations teams.
- API keys work well for public data services such as Maps Platform geocoding or place lookups, where requests do not read private account data.
- OAuth or service account credentials are usually required for private account data, including Google Analytics reporting and Google Ads account management. Check the documentation for each API before you assume a key will work.
If the data you need belongs to your own accounts, plan for OAuth from the start. Trying to force an API key into that workflow usually leads to errors and to keys being shared in places they should not be.
Step-by-Step: Create Your Google API Key
- Sign in to Google Cloud Console: Use the Google account that your team owns, not a personal one, so access survives staff changes.
- Create or select a project: Open the project dropdown, choose 'New Project' and give it a name your team will recognize, such as the tool or workflow it supports.
- Enable the API: Go to 'APIs and Services' then 'Library', search for the service you need and select 'Enable'. Enable only what the workflow uses.
- Generate the key: Go to 'Credentials', select 'Create Credentials' and choose 'API key'. Copy it into your password manager or secrets store at once.
- Restrict the key: Select 'Edit' on the key and apply restrictions before using it anywhere. This is covered in the next section.
Related: Sales Types for Small B2B Teams: A Data-Driven Guide
Restrict the Key Before Your Team Uses It
An unrestricted key can be used against any API enabled on the project, from any location. Set both kinds of restriction:
- API restrictions: Limit the key to the specific APIs the workflow needs, and nothing else.
- Application restrictions: Limit use to the HTTP referrers, IP addresses, or app identifiers that will actually make the calls.
- Review and rotate: Schedule a periodic check of who has access to the project and replace keys when someone leaves the team.
Keep Keys Out of CRM Fields and Shared Documents
Revenue teams often paste keys into HubSpot or Salesforce custom fields, workflow notes, or shared spreadsheets so that a colleague can run an automation. That spreads the key to people and tools that do not need it. Store keys in a secrets manager or in environment variables on the server that runs the script, and give the CRM only the outputs it needs, such as cleaned addresses or a validated status field.
Where Google Data Helps a Small Sales Team
The most practical use is data hygiene before reps act. Accurate company addresses and locations make territory rules work, and clean records make routing more reliable. A Google API key can support that clean-up step for public location data.
A key does not replace visitor identification. Happierleads is a B2B website visitor identification platform that reveals the exact person behind each anonymous visit, and it supports AI lead scoring, intent data, email outreach automation, and CRM integrations. Your Google API key handles location and reporting tasks in your own project. The two work side by side: the key keeps your reference data clean, and the visitor platform tells reps who is on the site now.
If you are deciding how visitor data should reach your CRM, the guide to HubSpot and Salesforce visitor identification setup walks through the connection step by step. For routing, see how to route identified website visitors to the right rep.
Common Mistakes to Avoid
- Publishing a key in a public code repository, client-side web page, or shared CRM note.
- Leaving a key unrestricted, which lets it call any enabled API.
- Forgetting to set budgets and usage alerts, so a looping script creates unexpected charges.
- Using an API key for private account data that needs OAuth or a service account.
- Tying keys to a single employee's personal Google account, which breaks when that person leaves.
Frequently Asked Questions
Short answers to the questions revenue teams ask most often about Google API keys.
If your team wants to see which companies visit your site and who is behind each visit, you can book a free demo of Happierleads and walk through the setup with someone on the team.
Frequently asked questions
Can I use a Google API key to read my Google Analytics or Google Ads data?
Usually no. Private account data typically requires OAuth or a service account. An API key is generally suited to public data services, so check the documentation for the specific API first.
What should I do if a Google API key is exposed?
Delete or regenerate the key in Google Cloud Console right away, review recent usage for unfamiliar activity, and update every tool that used the old key. Then add restrictions to the new key.
Can one API key serve several internal tools?
You can create multiple keys. Give each tool or workflow its own key with its own restrictions, so you can rotate or revoke one without breaking the others.
Do Google APIs cost money?
Many services include free usage tiers, and usage beyond those tiers can be billed. Set budgets and alerts in your Google Cloud billing settings to avoid surprise charges.




