In general, the google-analytics-admin library uses
Service Account
credentials to connect to Google Cloud services. When running within
Google Cloud Platform environments the
credentials will be discovered automatically. When running on other
environments, the Service Account credentials can be specified by providing the
path to the
JSON keyfile
for the account (or the JSON itself) in
environment variables. Additionally, Cloud SDK
credentials can also be discovered automatically, but this is only recommended
during development.
The google-analytics-admin library aims to make authentication
as simple as possible, and provides several mechanisms to configure your system
without requiring Service Account Credentials directly in code.
Credentials are discovered in the following order:
Specify credentials in method arguments
Specify credentials in configuration
Discover credentials path in environment variables
Discover credentials JSON in environment variables
Discover credentials file in the Cloud SDK's path
Discover GCP credentials
Google Cloud Platform environments
When running on Google Cloud Platform (GCP), including Google Compute Engine
(GCE), Google Kubernetes Engine (GKE), Google App Engine (GAE), Google Cloud
Functions (GCF) and Cloud Run, Credentials are discovered automatically.
Code should be written as if already authenticated.
Environment Variables
The Credentials JSON can be placed in environment variables instead of
declaring them directly in code. Each service has its own environment variable,
allowing for different service accounts to be used for different services. (See
the READMEs for the individual service gems for details.) The path to the
Credentials JSON file can be stored in the environment variable, or the
Credentials JSON itself can be stored for environments such as Docker
containers where writing files is difficult or not encouraged.
The environment variables that google-analytics-admin
checks for credentials are configured on the service Credentials class (such as
::Google::Analytics::Admin::V1alpha::AnalyticsAdminService::Credentials):
ANALYTICS_ADMIN_CREDENTIALS - Path to JSON file, or JSON contents
ANALYTICS_ADMIN_KEYFILE - Path to JSON file, or JSON contents
GOOGLE_CLOUD_CREDENTIALS - Path to JSON file, or JSON contents
GOOGLE_CLOUD_KEYFILE - Path to JSON file, or JSON contents
GOOGLE_APPLICATION_CREDENTIALS - Path to JSON file
The path to the Credentials JSON file can be configured instead of storing
it in an environment variable. Either on an individual client initialization:
This option allows for an easy way to authenticate during development. If
credentials are not provided in code or in environment variables, then Cloud SDK
credentials are discovered.
NOTE: This is not recommended for running in production. The Cloud SDK
should only be used during development.
Creating a Service Account
Google Cloud requires Service Account Credentials to
connect to the APIs. You will use the JSON key file to
connect to most services with google-analytics-admin.
Create a new project or click on an existing project.
Activate the menu in the upper left and select APIs & Services. From
here, you will enable the APIs that your application requires.
Note: You may need to enable billing in order to use these services.
Select Credentials from the side navigation.
Find the "Create credentials" drop down near the top of the page, and select
"Service account" to be guided through downloading a new JSON key file.
If you want to re-use an existing service account, you can easily generate a
new key file. Just select the account you wish to re-use, click the pencil
tool on the right side to edit the service account, select the Keys tab,
and then select Add Key.
The key file you download will be used by this library to authenticate API
requests and should be stored in a secure location.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[],[],null,["Version latestkeyboard_arrow_down\n\n- [0.1.4 (latest)](/ruby/docs/reference/google-analytics-admin/latest/AUTHENTICATION)\n- [0.1.3](/ruby/docs/reference/google-analytics-admin/0.1.3/AUTHENTICATION) \n\nAuthentication\n==============\n\nIn general, the google-analytics-admin library uses\n[Service Account](https://cloud.google.com/iam/docs/creating-managing-service-accounts)\ncredentials to connect to Google Cloud services. When running within\n[Google Cloud Platform environments](#google-cloud-platform-environments) the\ncredentials will be discovered automatically. When running on other\nenvironments, the Service Account credentials can be specified by providing the\npath to the\n[JSON keyfile](https://cloud.google.com/iam/docs/managing-service-account-keys)\nfor the account (or the JSON itself) in\n[environment variables](#environment-variables). Additionally, Cloud SDK\ncredentials can also be discovered automatically, but this is only recommended\nduring development.\n\nQuickstart\n----------\n\n1. [Create a service account and credentials](#creating-a-service-account).\n2. Set the [environment variable](#environment-variables).\n\n export ANALYTICS_ADMIN_CREDENTIALS=path/to/keyfile.json\n\n1. Initialize the client.\n\n```ruby\nrequire \"google/analytics/admin\"\n\nclient = Google::Analytics::Admin.analytics_admin_service\n```\n\nCredential Lookup\n-----------------\n\nThe google-analytics-admin library aims to make authentication\nas simple as possible, and provides several mechanisms to configure your system\nwithout requiring **Service Account Credentials** directly in code.\n\n**Credentials** are discovered in the following order:\n\n1. Specify credentials in method arguments\n2. Specify credentials in configuration\n3. Discover credentials path in environment variables\n4. Discover credentials JSON in environment variables\n5. Discover credentials file in the Cloud SDK's path\n6. Discover GCP credentials\n\n### Google Cloud Platform environments\n\nWhen running on Google Cloud Platform (GCP), including Google Compute Engine\n(GCE), Google Kubernetes Engine (GKE), Google App Engine (GAE), Google Cloud\nFunctions (GCF) and Cloud Run, **Credentials** are discovered automatically.\nCode should be written as if already authenticated.\n\n### Environment Variables\n\nThe **Credentials JSON** can be placed in environment variables instead of\ndeclaring them directly in code. Each service has its own environment variable,\nallowing for different service accounts to be used for different services. (See\nthe READMEs for the individual service gems for details.) The path to the\n**Credentials JSON** file can be stored in the environment variable, or the\n**Credentials JSON** itself can be stored for environments such as Docker\ncontainers where writing files is difficult or not encouraged.\n\nThe environment variables that google-analytics-admin\nchecks for credentials are configured on the service Credentials class (such as\n`::Google::Analytics::Admin::V1alpha::AnalyticsAdminService::Credentials`):\n\n- `ANALYTICS_ADMIN_CREDENTIALS` - Path to JSON file, or JSON contents\n- `ANALYTICS_ADMIN_KEYFILE` - Path to JSON file, or JSON contents\n- `GOOGLE_CLOUD_CREDENTIALS` - Path to JSON file, or JSON contents\n- `GOOGLE_CLOUD_KEYFILE` - Path to JSON file, or JSON contents\n- `GOOGLE_APPLICATION_CREDENTIALS` - Path to JSON file\n\n```ruby\nrequire \"google/analytics/admin\"\n\nENV[\"ANALYTICS_ADMIN_CREDENTIALS\"] = \"path/to/keyfile.json\"\n\nclient = Google::Analytics::Admin.analytics_admin_service\n```\n\n### Configuration\n\nThe path to the **Credentials JSON** file can be configured instead of storing\nit in an environment variable. Either on an individual client initialization: \n\n```ruby\nrequire \"google/analytics/admin\"\n\nclient = Google::Analytics::Admin.analytics_admin_service do |config|\n config.credentials = \"path/to/keyfile.json\"\nend\n```\n\nOr globally for all clients: \n\n```ruby\nrequire \"google/analytics/admin\"\n\nGoogle::Analytics::Admin.configure do |config|\n config.credentials = \"path/to/keyfile.json\"\nend\n\nclient = Google::Analytics::Admin.analytics_admin_service\n```\n\n### Cloud SDK\n\nThis option allows for an easy way to authenticate during development. If\ncredentials are not provided in code or in environment variables, then Cloud SDK\ncredentials are discovered.\n\nTo configure your system for this, simply:\n\n1. [Download and install the Cloud SDK](https://cloud.google.com/sdk)\n2. Authenticate using OAuth 2.0 `$ gcloud auth login`\n3. Write code as if already authenticated.\n\n**NOTE:** This is *not* recommended for running in production. The Cloud SDK\n*should* only be used during development.\n\nCreating a Service Account\n--------------------------\n\nGoogle Cloud requires **Service Account Credentials** to\nconnect to the APIs. You will use the **JSON key file** to\nconnect to most services with google-analytics-admin.\n\nIf you are not running this client within\n[Google Cloud Platform environments](#google-cloud-platform-environments), you\nneed a Google Developers service account.\n\n1. Visit the [Google Cloud Console](https://console.cloud.google.com/project).\n2. Create a new project or click on an existing project.\n3. Activate the menu in the upper left and select **APIs \\& Services**. From\n here, you will enable the APIs that your application requires.\n\n *Note: You may need to enable billing in order to use these services.*\n4. Select **Credentials** from the side navigation.\n\n Find the \"Create credentials\" drop down near the top of the page, and select\n \"Service account\" to be guided through downloading a new JSON key file.\n\n If you want to re-use an existing service account, you can easily generate a\n new key file. Just select the account you wish to re-use, click the pencil\n tool on the right side to edit the service account, select the **Keys** tab,\n and then select **Add Key**.\n\n The key file you download will be used by this library to authenticate API\n requests and should be stored in a secure location."]]