Google Ads

Supports:

  • ✅ Model sync destination
  • ✅ Bulk sync source

Connection

Configuration

NAMETYPEDESCRIPTIONREQUIREDREADONLY
oauth_refresh_tokenstringfalsefalse
connected_userstringfalsetrue
accountsarrayfalsefalse
client_idstringfalsefalse
client_secretstringfalsefalse
blanket_user_consentbooleanCauses this connection to send signals to Google Ads indicating that every transmitted user has accepted ad personalization and data sharing policies. This will cause the user to be included in more advertising functionsfalsefalse
custom_reportsstringOne report per line. Format is a report name followed by a Google Ads SQL query. e.g. myReport:ad_groups:campaign.idfalsefalse

Example

1{
2 "name": "Google Ads connection",
3 "type": "googleads",
4 "configuration": {
5 "accounts": [
6 {
7 "label": "",
8 "value": ""
9 }
10 ],
11 "blanket_user_consent": false,
12 "client_id": "a45gadsfdsaf47byor2ugfbhsgllpf12gf56gfds",
13 "client_secret": "ay8d5hdepz62px8lqeoakuea2ccl4rxm13i6tbyorxhu1i20kc8ruvksmzxq",
14 "custom_reports": "",
15 "oauth_refresh_token": "dasfdasz62px8lqeoakuea2ccl4rxm13i6tbyorxhu1i20kc8ruvksmzxq"
16 }
17}

Model Sync

Target

Google Ads connections may be used as the destination in a model sync.

Target creation

Google Ads connections may be used to create a new target for a model sync. The following parameters are required to create a new target:

NAMEDESCRIPTIONENUM
accountAccount IDtrue
nameUser list namefalse

Bulk Sync

Source

Configuration

NAMETYPEDESCRIPTIONREQUIREDREADONLY
reporting_lookbackintegerLookback period for reportsfalsefalse

Example

1{
2 ...
3 "source_configuration": {
4 "reporting_lookback": 0
5 }
6}