The ‘Google Login’ option is provided on ‘Seller Sign in’ form which will only be displayed if the admin has enabled ‘Google Login’ plugin settings from ‘Advertisement Feed Plugins’.

Fig. 1.1: Seller Sign In Form 

Admin will need a Google Account (like Gmail Login Credentials) to sign up for Merchant Center. If the admin doesn’t have a Google account, they must first go to accounts.google.com and click Create account.

Once the Google Account has been created, admin must go to https://console.developers.google.com/ which will redirect them to ‘Google Sign In to continue to Google Cloud Platform’ page as shown in figure 1.2. Admin must click on the ‘Create Account’ button and choose any one of the two options: ‘For Myself’ or ‘To Manage My Business’ as per their necessity. 

Fig. 1.2: Google Sign In to continue to Google Cloud Platform

‘Create Your Google Account’ page will appear as shown in figure 1.3, in which the admin must enter the required field and click on the ‘Next’ button. A verification code will be shared with the admin on their registered email address. Once the verification step is complete, the general steps required to setup the Google business account such as entering Business Name, Business Category, Add Location, Customer Locations, Seller’s Business Location, Seller’s Contact Details, Verifying Mailing Address, adding Services, Business Description, and Add photos of Business are to be followed. 

Fig. 1.3: Create Your Google Account page

Once the Google Account has been created, admin must: 

1. Login on https://console.developers.google.com/ through their credentials. As shown in figure 1.4, the dashboard will open on the screen. Fig. 1.4: Dashboard
2. On the dashboard, the admin must click on ‘Select a Project’ drop-down provided on the top-navigation panel. If no project has been created as shown in figure 1.5, click on the ‘New Project’ button provided on the top-right corner.Fig. 1.5: Select a Project
3. A ‘New Project’ form will appear as shown in figure 1.6.Fig. 1.6: Create New Project Form
   Admin must:
   • Project Name*: A unique project name. 
   • Organization*: Select the organization to which the new project is to be attached. This select cannot be changed later. 
   • Location*: Enter the link of the parent organization or folder.
     Once the input fields have been entered, the admin must click on ‘Create’ to add the new project.
4. Click on ‘Credentials’ from the side-navigation panel which will open the credentials page as shown in figure 1.7. Fig. 1.7: Credentials Page
5. Click on ‘Create Credentials’ blue plus icon to create new credentials. A drop-down list will appear as shown in figure 1.8.Fig. 1.8: Create Credentials
6. Admin must select the ‘API Key’ option which will create an API key also known as ‘Developer Key’. It will be displayed on the ‘Credentials’ page as shown in figure 1.9.Fig. 1.9: Created API/ Developer Key
   The ‘Developer Key’ is generated successfully and can be copied whenever required.
7. Admin must then click on the ‘Create Credentials’ blue plus icon and select the ‘OAuth Client ID’ option from the list which will redirect admin to ‘Create OAuth Client ID’ page as shown in figure 1.10.Fig. 1.10: Create OAuth Client ID page
8. Admin must click on ‘Configure Consent Screen’ if the page appears as in figure 1.10. ‘OAuth Consent Screen’ will appear as shown in figure 1.11 (a) and (b) belowFig. 1.11 (a): OAuth Consent ScreenFig. 1.11 (b): OAuth Consent Screen
   Admin must fill in all the necessary details and then click on the ‘Save’ button.
9. This will redirect admin to the next step which asks to select ‘User Type’ as shown in figure 1.12. Admin must select the type (recommended ‘External’) and click on the ‘Create’ button.Fig. 1.12: User Type for OAuth Consent Screen
10. Admin must then again click on the ‘Create Credentials’ blue plus icon and select ‘OAuth Client ID’ option from the list which will redirect admin to ‘Create OAuth Client ID’ page as shown in figure 1.13.Fig. 1.13: Create OAuth Client ID
    Admin must select the ‘Application Type*’ from the drop-down list. Select ‘Web Application’ from the list which will open an extended list as shown in figure 1.14 that is to be filled by admin. Admin can enter a new name for their client Id. Fig. 1.14: ‘Web Application’ for ‘Create OAuth Client ID’
    Admin must add:
    • Authorizer JavaScript origins: Add domain name with format – http://domainname.com or https://domainname.com (for SSL certificate enabled on server). 
    • Authorized Redirect URIs: Add callback URI on which it will redirect you back and provide merchant account details. The format to be used- http://domainname.com/public/index.php?url=google-login/index or https://domainname.com/public/index.php?url=google-login/index (if SSL certificate enabled on server).
      Admin must click on ‘Create’ which will create the Client ID and Secret Key for them . 
11. The keys generated will appear on the ‘Credentials’ page as shown in figure 1.15.Fig. 1.15: Credentials Page
    The process to create keys is completed from Admin-end.
12. These keys are to be configured by admin in the input fields provided on ‘Google Login Plugin Settings’ form as shown in figure 1.16, provided in Plugins> Social Login. Clicking on the action button provided to the right of ‘Google Login’ plugin will open this form.Fig. 1.16: Google Shopping Feed Plugin Settings
    The ‘Client Id’ and ‘Client Secret’ keys can be accessed by clicking on icon provided to the right of ‘Client ID’ mentioned under ‘OAuth 2.0 Client IDs’ list. A ‘Client ID for Web Application’ page will open which will display ‘Client ID and ‘Client Secret’ as shown in figure 1.17 below.Fig. 1.17: Client ID and Client Secret Keys
    The ‘Developer Key’ can directly be copied from the ‘Credentials’ list by clicking on   icon provided to its right.