Twitter Ads Reader
Note
This adapter is in preview and is available on Striim Developer only. See Striim Developer for more information.
Twitter Ads is paid promotional messages that businesses use to reach a wider audience on Twitter. They can help businesses: Increase brand visibility, Drive website traffic, Generate leads, and Attract new followers. The Twitter Ads Reader fetches or collects update details from a Twitter Ads account.
Feature summary
Feature | Supported? | Notes | |
---|---|---|---|
Objects | Standard objects | ✓ | |
Custom objects | ✓ | ||
Authentication | Basic authentication | Username and password | |
OAuth authentication | ✓ | Manual configuration based | |
Custom authentication methods | Not all methods may be supported | ||
Operations | Automated mode | ✓ | |
Initial load | ✓ | ||
Pull-based incremental load | ✓ | ||
Push-based incremental load | |||
Automated pipeline | |||
Governance | Connection profile | ||
Sherlock AI | |||
Sentinel AI | |||
Schema handling | Initial schema creation | ✓ | Works with supported targets |
Schema evolution | |||
Setup | Wizard template | ||
Flow Designer | ✓ | ||
Striim TQL | ✓ | ||
Runtime | Resilience/recovery | ✓ | |
Parallel execution | |||
Metrics | ✓ | Standard metrics |
Supported authentication method
The Twitter Ads Reader supports OAuth authentication. Creating a connection requires creating a project and application in Twitter, generating an access token and secret, and setting the Striim connection properties.
Go to Twitter Ads and sign in.
Create a new project in the Developer Portal.
At the project you just created, choose Add App.
Navigate to the application you just created.
Go to Keys and tokens.
At the Access Token and Secret option, click Generate.
See Access Tokens and Twitter Ads OAuth Info in the Twitter documentation.
Supported objects
The following are the supported objects for reading from Twitter Ads:
AdAccounts
AdActiveEntities
AdCampaignAudienceReach
AdCampaigns
AdCards
AdFundingInstruments
AdFundingInstrumentsAudienceReach
AdLineItems
AdPromotedTweets
AdStats
AdTweets
Twitter Ads Reader properties
Property | Type | Default value | Notes |
---|---|---|---|
Access token | Password | The access token for connecting using OAuth. The access token is retrieved from the OAuth server as part of the authentication process. It has a server-dependent timeout and can be reused between requests. | |
Client ID | String | The client ID assigned when you register your application with an OAuth authorization server. | |
Client secret | Password | The client secret assigned when you register your application with an OAuth authorization server. | |
Connection pool size | Integer | 20 | Specifies the maximum number of active connections. |
Exclude tables | String | A list of tables excluded from read operations. Typically used to create a list of exceptions when the Tables property includes wildcards. Misconfiguration of the Tables and Exclude Tables properties can cause "Invalid table names" errors. | |
Incremental load marker | String | The incremental load marker is a unique incremental column in each object used for incremental load. When no marker is specified, tables are resynced at each polling interval. Specify the name of the column that contains the start position value. This column must meet the following criteria:
| |
Migrate schema | Boolean | False | Only available in Initial Load or Automated mode. Set to |
Mode | Select list:
| Automated | Automated mode applies incremental updates to objects that support incremental load and performs full resyncs for objects that do not support incremental load. |
Polling interval | Integer | 5m | Specifies an interval as an integer followed by a unit. Supported units are days ( |
Start Position | String | %=-1 | Value of the incremental load marker that defines the initial reading position. |
Tables | String | A semicolon-delimited (;) list of objects to read from the source. Supports the | |
Thread pool count | Integer | 10 | The number of parallel running threads. The default value of zero specifies single-threaded operation. When the value of the thread pool counter is higher than the connection pool size, large data ingestion operations can cause the app to halt. Since best performance is achieved when using one thread for each table being synced, increasing the size of the connection pool to match the number of threads in use is a performance best practice. |