New Woo brand announcement v2 | Feb 4, 2025

Added by Mahrie - https://woomarketingstudio.wordpress.com/2024/12/20/studio-request-logo-rollout-customer-comms/

Review Translator – Google Cloud Configuration

In order to configure and start using the plugin a few things need to be setup. Part of this is off-site in the Google Cloud dashboard, part on the plugin settings page. Don’t worry, we’ll walk you through everything.

Getting the Google Cloud API Key

↑ Back to top

In order to use the Review Translator plugin we need to connect to the Google Cloud Translation API. To connect to the Translation API you need a Google Cloud account and create an API key. We’ll walk you through creating everything in the steps below.

Enabling the Google Cloud Translation API

↑ Back to top

Head over to this link and click on the “Enable” button to enable the Cloud Translation API; https://console.cloud.google.com/apis/library/translate.googleapis.com

Enable the Google Cloud Translation API

Create the Google Cloud API Key

↑ Back to top

To create a new API key for this plugin head over to https://console.cloud.google.com/apis/credentials. Make sure you’re logged in with the correct Google account you wish to use for your store. 

If prompted you may have to add a billing account. Follow the steps Google provides for this.

Create a new project if you don’t have one yet following the provided the steps on the screen.

Create a new project in Google Cloud


Next, click on the “+ Create credentials”, located at the top center of the page. Choose “Create API Key” from the dropdown that appears. 

Click to create a new API key

The API key will be created automatically. Copy the key to the field on the plugin settings page. 

Setup restrictions for the API Key

It is recommended to setup restrictions for the API key so it can only be used from your own domain and nothing else. This prevents the API key from being abused. To setup the restrictions you can click on the API key that was just created to set an application.

Below the option to restrict it to your site/app, you can also setup for the API key to only be used with certain APIs. Here it is recommended to select the “Cloud Translation API” as a restriction.

Set the API restrictions only to the Cloud Translation API

Setting up budgets and alerts

↑ Back to top

This part is optional, but highly recommended. Each translation that goes through the translation API is charged by Google. You might be able to get some free credit each month, good for 500,000 character translation for free. For exact pricing make sure to check the Cloud Translation pricing price (at the time of writing it is $20 per 1 million characters).

To setup budgets you can open the hamburger navigation menu on the top left on any Google Cloud page and click on the “Billing” link. Once the page is loaded the left side menu opens and has a “Budget & Alerts” page. From that page you can add Budgets using the “+ Create budget” link at the top/center of the page. If you need further instructions, there’s also a “Learn” button at the top right for more information from Google on this.

Setting Quotas & System limits

↑ Back to top

Alongside setting up budgets you can also setup quotas & system limits to prevent overuse. From the left hand hamburger menu, head over to the “IAM & Admin” > “Quotas & System limits” page. On that page you can add a filter for Service “Cloud Translation API” to filter only the relevant rows. 

From there on you can change the values according to your requirements/wishes, as well as see the current usage if you’re interested in that. 

Set quotas and limits for your project

(Don’t take inspiration from my values, these were just test values)

You can read more on Quotes and Limits here; https://cloud.google.com/translate/quotas

Google Attribution and Disclaimer

Google requires attribution for texts that are translated through their service. This is handled out of the box through the plugin with the grey attribution image and link. If you wish to have a different attribution image and want to handle this yourself you can replace the existing one with the following snippet;

// Removes existing attribution
remove_action( 'Review_Translator_for_Woo\review\after_translated_from', 'Review_Translator_for_Woo\display_google_translation_attribution' );

// Add custom attribution (this is the default attribution that you can modify to fit your site
function custom_display_google_translation_attribution( $translated_review ) {
	if ( ! $translated_review || ! $translated_review->exists() ) {
		return;
	}

	if ( $translated_review->get_translation_service() !== 'google-cloud-translate' ) {
		return;
	}

    if ( 'google-grey' == get_option( 'rtw_google_attribution', 'google-grey' ) ) {
		?><span class="rtw-attribution" style="float: right;"><a href="https://translate.google.com" rel="noopener nofollow" target="_blank" style="vertical-align: middle;"><?php require wp_kses_post( plugin_dir_path( Review_Translator_for_Woo_FILE ) . 'assets/img/google-powered-grey.svg' ); ?></a></span><?php
	}
}
add_action( 'Review_Translator_for_Woo\review\after_translated_from', 'custom_display_google_translation_attribution' );

Google also requires a disclaimer to be added to your site. This is not done automatically through the plugin as there is not one unified way to do so. The disclaimer and instructions can be found here: https://cloud.google.com/translate/attribution#disclaimer

Next steps

That’s it for configuring things on Google’s end. The next step is to configure the plugin settings.