Microsoft Ads¶
The Microsoft Ads connector is a Palantir-provided driver for Microsoft Ads.
To create a new Microsoft Ads source, follow the standard setup flow for Palantir-provided drivers, then use the sections below for Microsoft Ads-specific configuration and networking. For the complete property reference, see the official Microsoft Ads driver documentation ↗.
Configuration¶
The properties below are mandatory or recommended.
| Property | Required? | Description | Default |
|---|---|---|---|
CustomerId ↗ |
Mandatory | CustomerId of the currently authenticated user. | — |
DeveloperToken ↗ |
Mandatory | DeveloperToken of the currently authenticated user. | — |
AccountId ↗ |
Recommended | The id of the account that you want to get data for. | — |
InitiateOAuth ↗ |
Recommended | Specifies the process for obtaining or refreshing the OAuth access token, which maintains user access while an authenticated, authorized user is working. | REFRESH |
OAuthClientId ↗ |
Recommended | Specifies the client Id that was assigned when the custom OAuth application was created. (Also known as the consumer key.) This ID registers the custom application with the OAuth authorization server. | — |
OAuthClientSecret ↗ |
Recommended | Specifies the client secret that was assigned when the custom OAuth application was created. (Also known as the consumer secret). This secret registers the custom application with the OAuth authorization server. | — |
Networking¶
The table below lists the domains that the source needs to be able to access in order to successfully run.
For each domain, add a corresponding egress policy. If the source is hosted on-premises and not directly reachable from Foundry, use an agent proxy egress policy instead; the agent host itself must also be able to reach the listed domains. See using an agent as a proxy for details.
| Domain | Required |
|---|---|
| bingads.microsoft.com | Always |
| api.bingads.com | Always |
| clientcenter.api.bingads.microsoft.com | Always |
| login.microsoftonline.com | Always |
| campaign.api.bingads.microsoft.com | If UseSandbox=False |
| clientcenter.api.bingads.microsoft.com | If UseSandbox=False |
| adinsight.api.bingads.microsoft.com | If UseSandbox=False |
| reporting.api.bingads.microsoft.com | If UseSandbox=False |
| campaign.api.sandbox.bingads.microsoft.com | If UseSandbox=True |
| clientcenter.api.sandbox.bingads.microsoft.com | If UseSandbox=True |
| adinsight.api.sandbox.bingads.microsoft.com | If UseSandbox=True |
| reporting.api.sandbox.bingads.microsoft.com | If UseSandbox=True |
中文翻译¶
Microsoft Ads¶
Microsoft Ads 连接器是 Palantir 为 Microsoft Ads 提供的驱动程序。
要创建新的 Microsoft Ads 数据源，请遵循 Palantir 提供驱动程序的标准设置流程，然后使用以下各节进行 Microsoft Ads 特定的配置和网络设置。有关完整的属性参考，请参阅官方 Microsoft Ads 驱动程序文档 ↗。
配置¶
以下属性为必填或推荐项。
| 属性 | 是否必填 | 描述 | 默认值 |
|---|---|---|---|
CustomerId ↗ |
必填 | 当前认证用户的客户 ID。 | — |
DeveloperToken ↗ |
必填 | 当前认证用户的开发者令牌。 | — |
AccountId ↗ |
推荐 | 您要获取数据的账户 ID。 | — |
InitiateOAuth ↗ |
推荐 | 指定获取或刷新 OAuth 访问令牌的流程，该令牌用于在已认证授权用户工作时维持其访问权限。 | REFRESH |
OAuthClientId ↗ |
推荐 | 指定创建自定义 OAuth 应用程序时分配的客户端 ID（也称为消费者密钥）。该 ID 用于将自定义应用程序注册到 OAuth 授权服务器。 | — |
OAuthClientSecret ↗ |
推荐 | 指定创建自定义 OAuth 应用程序时分配的客户端密钥（也称为消费者密钥）。该密钥用于将自定义应用程序注册到 OAuth 授权服务器。 | — |
网络设置¶
下表列出了数据源成功运行所需访问的域名。
对于每个域名，请添加相应的出站策略。如果数据源部署在本地且无法直接从 Foundry 访问，请改用代理出站策略；代理主机本身也必须能够访问所列域名。详情请参阅使用代理作为代理服务器。
| 域名 | 必需条件 |
|---|---|
| bingads.microsoft.com | 始终需要 |
| api.bingads.com | 始终需要 |
| clientcenter.api.bingads.microsoft.com | 始终需要 |
| login.microsoftonline.com | 始终需要 |
| campaign.api.bingads.microsoft.com | 当 UseSandbox=False 时需要 |
| clientcenter.api.bingads.microsoft.com | 当 UseSandbox=False 时需要 |
| adinsight.api.bingads.microsoft.com | 当 UseSandbox=False 时需要 |
| reporting.api.bingads.microsoft.com | 当 UseSandbox=False 时需要 |
| campaign.api.sandbox.bingads.microsoft.com | 当 UseSandbox=True 时需要 |
| clientcenter.api.sandbox.bingads.microsoft.com | 当 UseSandbox=True 时需要 |
| adinsight.api.sandbox.bingads.microsoft.com | 当 UseSandbox=True 时需要 |
| reporting.api.sandbox.bingads.microsoft.com | 当 UseSandbox=True 时需要 |