Console

1. Go to the Data transfers page in the Google Cloud console.

   Go to Data transfers

2. ClickaddCreate transfer.

3. On theCreate Transfer page:

   • In theSource type section, forSource, chooseGoogle Merchant Center.

   • In theTransfer config name section, forDisplay name, enter aname for the data transfer such asMy Transfer. The transfer name canbe any value that lets you identify the transfer if you need to modifyit later.

     

   • In theSchedule options section:

     • Select aRepeat frequency. If you selectHours,Days,Weeks, orMonths, you must also specify a frequency. You canalso selectCustom to specify a custom repeat frequency. If youselectOn-demand, then this data transfer runs when youmanually trigger the transfer.
     • If applicable, select eitherStart now orStart at set time,and provide a start date and run time.
     • ForStart date and run time, enter the date and time to start thetransfer. This value should be at least 24 hours later than thecurrent UTC time. If you choseStart now, this option is disabled.

     If you leave the schedule options set toStart now, the first datatransfer run starts immediately, and it fails with the following errormessage:No data to transfer found for the Merchant account. If youhave just created this transfer, you may need to wait for up to a daybefore the data of your Merchant account are prepared and availablefor the transfer. The next scheduled run should run successfully. Ifthe data of your Merchant account are prepared on the same date in UTCtime, you canset up a backfillfor today's run.

     

   • In theDestination settings section, forDestination dataset,choose the dataset that you created to store your data.

     

   • In theData source details section, forMerchant ID, enter yourMerchant ID or MCA ID. Select the report(s) that you would like totransfer. SeeSupported Reportsfor more details.

     

   • In theService Account menu, select aservice accountfrom the service accounts associated with yourGoogle Cloud project.You can associate a service account with your data transfer instead ofusing your user credentials. For more information about using serviceaccounts with data transfers, seeUse service accounts.

     • If you signed in with afederated identity,then a service account is required to create a data transfer. If yousigned in with aGoogle Account,then a service account for the transfer is optional.
     • The service account must have therequired permissions.

   • (Optional) In theNotification options section:

     • Click the toggle to enable email notifications. When you enable thisoption, the transfer administrator receives an email notificationwhen a transfer run fails.
     • ForSelect a Pub/Sub topic, choose yourtopic name or clickCreate a topic.This option configures Pub/Sub runnotifications for yourtransfer.

4. ClickSave.

bq

Enter thebq mk command and supply the transfer creation flag —--transfer_config. The following flags are also required:

• --data_source
• --target_dataset
• --display_name
• --params

You can also supply the--project_id flag to specify a particularproject. If--project_id isn't specified, the default project is used.

bqmk\--transfer_config\--project_id=project_id\--target_dataset=dataset\--display_name=name\--params='parameters'\--data_source=data_source--service_account_name=service_account_name

Where:

• project_id is your project ID.
• dataset is the target dataset for the transfer configuration.
• name is the display name for the transfer configuration. Thetransfer name can be any value that lets you identify thetransfer if you need to modify it later.
• parameters contains the parameters for the created transferconfiguration in JSON format. For example:--params='{"param":"param_value"}'.
  • For Merchant Center data transfers, you must supply themerchant_id parameter.
  • Theexport_products parameter specifies whether to transfer productand product issues data. This parameter is included by default, even ifyou don't specify theexport_products parameter. Google recommendsthat you include this parameter explicitly and set it to "true".
  • Theexport_regional_inventories parameter specifies whether totransfer regional inventories data.
  • Theexport_local_inventories parameter specifies whether totransfer local inventories data.
  • Theexport_price_competitiveness parameter specifies whether totransfer price competitiveness data.
  • Theexport_price_insights parameter specifies whether to transferprice insights data.
  • Theexport_best_sellers_v2 parameter specifies whether to transferbest sellers data.
  • Theexport_performance parameter specifies whether to transferproduct performance data.
• data_source is the data source —merchant_center.
• service_account_name is the service account name used toauthenticate your data transfer. The service accountshould be owned by the sameproject_id used to create the transfer andit should have all of therequired permissions.

bqmk\--transfer_config\--target_dataset=mydataset\--display_name='My Transfer'\--params='{"merchant_id":"1234","export_products":"true","export_regional_inventories":"true","export_local_inventories":"true","export_price_benchmarks":"true","export_best_sellers":"true"}'\--data_source=merchant_center

If you have just created this data transfer, you may need to wait for up to a daybefore the data of your Merchant account are prepared and available for thetransfer.` The next scheduled run should run successfully. If the data ofyour Merchant account are prepared on the same date in UTC time, you canset up a backfill for today's run.

API

Use theprojects.locations.transferConfigs.createmethod and supply an instance of theTransferConfigresource.