Twitter Ads

The Twitter Ads connector is a Palantir-provided driver for Twitter Ads.

To create a new Twitter Ads source, follow the standard setup flow for Palantir-provided drivers, then use the sections below for Twitter Ads-specific configuration and networking. For the complete property reference, see the official Twitter Ads driver documentation ↗.

Configuration

The properties below are mandatory or recommended.

PropertyRequired?DescriptionDefault
OAuthClientIdMandatorySpecifies 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.
OAuthClientSecretMandatorySpecifies 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.
AccountIdRecommendedIdentifier of the advertising account. This Id is used to get analytic stats for the account that is identified by this Id. The AddAccounts view can be used to list available accounts with their specific Ids.
InitiateOAuthRecommendedSpecifies the process for obtaining or refreshing the OAuth access token, which maintains user access while an authenticated, authorized user is working.GETANDREFRESH
UseAppOnlyAuthenticationRecommendedA boolean that indicates whether or not you would like to use app-only authentication.TRUE

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.

DomainRequired
api.twitter.comAlways
ads-api.twitter.comAlways