Twitter Ads is currently in closed beta. Contact support to inquire if testers for this integration are needed.
This integration is powered by Singer's twitter-ads tap and certified by Stitch. Check out and contribute to the repo on GitHub.
For support, contact Stitch support.
Twitter Ads integration summary
Stitch’s Twitter Ads integration:
- Replicates core object data using the Twitter Ads API v.7. Refer to the Schema section for a list of objects available for replication.
- Supports configuring custom reports using Twitter’s Analytics API
Twitter Ads feature snapshot
A high-level look at Stitch's Twitter Ads (v1) integration, including release status, useful links, and the features supported in Stitch.
| STITCH | |||
| Release status | Supported by | ||
| Stitch plan |
Standard |
API availability |
Available |
| Singer GitHub repository | |||
| REPLICATION SETTINGS | |||
| Anchor Scheduling |
Supported |
Advanced Scheduling |
Supported |
| Table-level reset |
Unsupported |
Configurable Replication Methods |
Unsupported |
| DATA SELECTION | |||
| Table selection |
Supported |
Column selection |
Supported |
| Select all |
Supported |
||
| TRANSPARENCY | |||
| Extraction Logs |
Supported |
Loading Reports |
Supported |
Connecting Twitter Ads
Twitter Ads setup requirements
To set up Twitter Ads in Stitch, you need:
-
To have access to the Twitter Ads accounts you want to replicate data from.
Step 1: Retrieve account ID
- Login to your Twitter Ads account.
- Select the ads account that you’d like to use.
- Click your account icon upper right corner of the screen.
- Click Settings in the dropdown menu.
- Copy your account ID and keep it readily available for the next step.
Note: If you would like to add multiple ads accounts for this integration, repeat the above steps for each account.
Step 2: Add Twitter Ads as a Stitch data source
- Sign into your Stitch account.
-
On the Stitch Dashboard page, click the Add Integration button.
-
Click the Twitter Ads icon.
-
Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.
For example, the name “Stitch Twitter Ads” would create a schema called
stitch_twitter_adsin the destination. Note: Schema names cannot be changed after you save the integration. - In the Account IDs field, paste the account ID you copied from Step 1. If you’re adding multiple accounts IDs, format them as a comma-delimited list. For example:
accountId1, accountId2 - Optional: In the Attribution Window field, enter the number of days you want to use as a lookback period for conversion reporting to stabilize. Custom report tables use this value during Extraction.
- Optional: Check the with deleted box if you want to include deleted records in the extraction Stitch performs.
-
In the Country Codes field, enter a comma-separated list of the ISO alpha-2 country codes for each country you want to include in segmentation and targeting.
For example: A list of
US, DE, IEcorresponds toUnited States, Germany, Ireland.Note: This field is required to use some segment types in custom reports.
Step 3: Configure reports
Stitch’s Twitter Ads integration supports the configuration of custom reports. For each report configured in the Your Reports section, a table will display in the Tables to Replicate tab as available for selection.
Refer to the Table reference for an example of a custom report table.
Create a new report
To add a report, click the + Configure new report link. For each report you configure, you’ll define the following parameters:
- Report Name: A name for the report, which is used to create the name of its corresponding destination table
- Entity: The Twitter Ads entity (object) to report on. The entity you select determines the metrics (columns) available for selection and the segments you can apply to those metrics. Refer to the Custom report options compatibility reference for more info.
- Segment: A segment to apply to the entity’s available metrics. Note: Some entity and segment combinations may be incompatible. Refer to the Segment compatibility reference for more info.
- Granularity: The granularity of the report data. Possible options are
DAY,HOUR, andTOTAL.
Remove a report
To remove a report, click the - Remove this report link.
Note: Removing a report will not remove the corresponding table or its data from your destination.
Step 4: Define the historical replication start date
The Sync Historical Data setting defines the starting date for your Twitter Ads integration. This means that:
- For tables using Key-based Incremental Replication, data equal to or newer than this date will be replicated to your destination.
- For tables using Full Table Replication, all data - including records that are older, equal to, or newer than this date - will be replicated to your destination.
Change this setting if you want to replicate data beyond Twitter Ads’s default setting of 1 year. For a detailed look at historical replication jobs, check out the Syncing Historical SaaS Data guide.
Step 5: Create a replication schedule
In the Replication Frequency section, you’ll create the integration’s replication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.
Twitter Ads integrations support the following replication scheduling methods:
-
Advanced Scheduling using Cron (Advanced or Premium plans only)
To keep your row usage low, consider setting the integration to replicate less frequently. See the Understanding and Reducing Your Row Usage guide for tips on reducing your usage.
Step 6: Set objects to replicate
The last step is to select the tables and columns you want to replicate. Learn about the available tables for this integration.
Note: If a replication job is currently in progress, new selections won’t be used until the next job starts.
For Twitter Ads integrations, you can select:
-
Individual tables and columns
-
All tables and columns
Click the tabs to view instructions for each selection method.
- In the integration’s Tables to Replicate tab, locate a table you want to replicate.
-
To track a table, click the checkbox next to the table’s name. A blue checkmark means the table is set to replicate.
-
To track a column, click the checkbox next to the column’s name. A blue checkmark means the column is set to replicate.
- Repeat this process for all the tables and columns you want to replicate.
- When finished, click the Finalize Your Selections button at the bottom of the screen to save your selections.
- Click into the integration from the Stitch Dashboard page.
-
Click the Tables to Replicate tab.
- In the list of tables, click the box next to the Table Names column.
-
In the menu that displays, click Track all Tables and Fields:
- Click the Finalize Your Selections button at the bottom of the page to save your data selections.
Initial and historical replication jobs
After you finish setting up Twitter Ads, its Sync Status may show as Pending on either the Stitch Dashboard or in the Integration Details page.
For a new integration, a Pending status indicates that Stitch is in the process of scheduling the initial replication job for the integration. This may take some time to complete.
Initial replication jobs with Anchor Scheduling
If using Anchor Scheduling, an initial replication job may not kick off immediately. This depends on the selected Replication Frequency and Anchor Time. Refer to the Anchor Scheduling documentation for more information.
Free historical data loads
The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.
Twitter Ads replication
In this section:
Extraction
This section provides a high-level look at extraction, but you can check out the sync review on Google Docs for a more technical look at this process.
For every table set to replicate, Stitch will perform the following during Extraction:
Discovery
During Discovery, Stitch will:
Determining table availability
At the start of each replication job, Stitch performs a structure sync. During this phase, Stitch detects the objects available for replication.
There are two types of tables for Twitter Ads:
-
Core object tables: These are tables that aren’t created using the Custom reports feature in the integration’s settings page. Table availability depends on the Twitter Ads Singer tap, which powers Stitch’s integration. The tap contains a JSON schema for each available table.
The Table reference section of this guide lists the tables currently available for replication, as well as info about how they replicate.
-
Custom report tables: These are tables that are created using the Custom reports feature in the integration’s settings page. Table availability depends on configuration of the report in the integration’s settings page. Note: Custom report tables must also be set to replicate in the Tables to Replicate tab - Stitch won’t automatically replicate them.
Refer to the Table reference for an example of a custom report table.
Determining column availability
Column availability is dependent upon the type of table:
- Core Object tables: Column availability is determined by the JSON schema backing the table in the Singer tap.
-
Custom report tables: Column availability is determined by the Entity selected during report configuration. Each entity in Twitter Ads is compatible with one or more metric groups. Each metric in a metric group corresponds to a column available for replication.
For example: If the entity is compatible with the BILLING metric group, you’d see
billed_engagementsandbilled_charge_local_microcolumns available for replication.Refer to the Entity and metric group compatibility reference for more info.
Data replication
After discovery is completed, Stitch will move onto extracting data for the tables and columns you set to replicate.
How Stitch extracts data depends on the type of table being replicated:
-
Core object tables: For these tables, extraction depends on the type of Replication Method the table uses. Refer to the Table reference for the Replication Method each table uses.
-
Custom report tables: Custom report tables replicate using Key-based Incremental Replication and the Attribution Window you define during setup. Attribution Windows are used in conjunction with Replication Keys to determine where Stitch should begin extraction for a table during each extraction job.
Loading
How data replicated from an Twitter Ads integration is loaded into your destination depends on two factors:
- The type of table being loaded:
- Core object tables are loaded using Upsert loading behavior.
- Custom report tables are loaded using Append-Only loading behavior.
- If your destination supports upserts, or updating existing rows. For destinations that support upserts, Stitch uses Primary Keys to de-dupe data during loading. Primary Keys are used to identify unique rows within a table and ensure that only the most recently updated version of that record appears in your destination.
Note: For Append-Only destinations, data will be loaded in an Append-Only manner, regardless of the table type.
Twitter Ads table reference
Schemas and versioning
Schemas and naming conventions can change from version to version, so we recommend verifying your integration’s version before continuing.
The schema and info displayed below is for version 1 of this integration.
This is the latest version of the Twitter Ads integration.
Table and column names in your destination
Depending on your destination, table and column names may not appear as they are outlined below.
For example: Object names are lowercased in Redshift (CusTomERs > customers), while case is maintained in PostgreSQL destinations (CusTomERs > CusTomERs). Refer to the Loading Guide for your destination for more info.
accounts
| Replication Method : |
Key-based Incremental |
Replication Key  :
|
updated_at |
Primary Key  :
|
id |
API endpoint : |
The accounts table contains info about the advertising-enabled accounts the user authenticating the integration has access to.
|
id
Reference:
|
|
updated_at
|
|
approval_status
|
|
business_id
|
|
business_name
|
|
created_at
|
|
deleted
|
|
industry_type
|
|
name
|
|
salt
|
|
timezone
|
|
timezone_switch_at
|
account_media
| Replication Method : |
Key-based Incremental |
Replication Key :
|
updated_at |
|
Primary Key :
|
id |
API endpoint : |
The account_media table contains info about the account media associated with an account.
advertiser_business_categories
| Replication Method : |
Full Table |
Primary Key :
|
id |
| API endpoint : | |||
The advertiser_business_categories table contains info about the advertiser business categories associated with an advertiser’s ad groups.
|
id
|
|
iab_categories
|
|
name
|
bidding_rules
| Replication Method : |
Full Table |
Primary Key :
|
currency |
| API endpoint : | |||
The bidding_rules table contains info about the bidding rules for currencies.
|
currency
|
|
maximum_cpe_bid_local_micro
|
|
minimum_cpe_bid_local_micro
|
|
minimum_denomination
|
campaigns
| Replication Method : |
Key-based Incremental |
Replication Key :
|
updated_at |
|
Primary Key :
|
id |
API endpoint : |
The campaigns table contains info about the campaigns associated with an account.
|
id
Reference: |
|
|
updated_at
|
|
|
account_id
Reference:
|
|
|
created_at
|
|
|
currency
|
|
|
daily_budget_amount_local_micro
|
|
|
deleted
|
|
|
duration_in_days
|
|
|
end_time
|
|
|
entity_status
|
|
|
frequency_cap
|
|
|
funding_instrument_id
Reference: |
|
|
name
|
|
|
reasons_not_servable
|
|
|
servable
|
|
|
standard_delivery
|
|
|
start_time
|
|
|
total_budget_amount_local_micro
|
cards_image_app_download
| Replication Method : |
Key-based Incremental |
Replication Key :
|
updated_at |
|
Primary Key :
|
id |
API endpoint : |
The cards_image_app_download table contains info about image app download cards associated with an account.
|
id
|
|
updated_at
|
|
account_id
Reference:
|
|
app_cta
|
|
card_type
|
|
card_uri
|
|
country_code
|
|
created_at
|
|
deleted
|
|
google_play_app_id
|
|
image_display_height
|
|
image_display_width
|
|
media_key
|
|
media_url
|
|
name
|
cards_image_conversation
| Replication Method : |
Key-based Incremental |
Replication Key :
|
updated_at |
|
Primary Key :
|
id |
API endpoint : |
The cards_image_conversation table contains info about image conversation cards associated with an account.
|
id
|
|
updated_at
|
|
account_id
Reference:
|
|
card_type
|
|
card_uri
|
|
created_at
|
|
deleted
|
|
first_cta
|
|
first_cta_tweet
|
|
image_display_height
|
|
image_display_width
|
|
media_key
|
|
media_url
|
|
name
|
|
thank_you_text
|
|
title
|
cards_image_direct_message
| Replication Method : |
Key-based Incremental |
Replication Key :
|
updated_at |
|
Primary Key :
|
id |
API endpoint : |
The cards_image_direct_message table contains info about the image direct message cards associated with an account.
|
id
|
|
updated_at
|
|
account_id
Reference:
|
|
app_cta
|
|
card_type
|
|
card_uri
|
|
created_at
|
|
deleted
|
|
first_cta
|
|
first_cta_welcome_message_id
|
|
image_display_height
|
|
image_display_width
|
|
media_key
|
|
media_url
|
|
name
|
|
recipient_user_id
Reference: |
cards_poll
| Replication Method : |
Key-based Incremental |
Replication Key :
|
updated_at |
|
Primary Key :
|
id |
API endpoint : |
The cards_poll table contains info about poll cards associated with an account.
|
id
|
|
updated_at
|
|
account_id
Reference:
|
|
card_type
|
|
card_uri
|
|
content_duration_seconds
|
|
created_at
|
|
deleted
|
|
duration_in_minutes
|
|
end_time
|
|
first_choice
|
|
name
|
|
second_choice
|
|
start_time
|
|
video_height
|
|
video_hls_url
|
|
video_poster_height
|
|
video_poster_url
|
|
video_poster_width
|
|
video_url
|
|
video_width
|
cards_video_app_download
| Replication Method : |
Key-based Incremental |
Replication Key :
|
updated_at |
|
Primary Key :
|
id |
API endpoint : |
The cards_video_app_download table contains info about the video app download cards associated with an account.
|
id
|
|
updated_at
|
|
account_id
Reference:
|
|
app_cta
|
|
card_type
|
|
card_uri
|
|
country_code
|
|
created_at
|
|
deleted
|
|
google_play_app_id
|
|
media_key
|
|
media_url
|
|
name
|
|
poster_media_url
|
|
video_owner_id
Reference: |
cards_video_conversation
| Replication Method : |
Key-based Incremental |
Replication Key :
|
updated_at |
|
Primary Key :
|
id |
API endpoint : |
The cards_video_conversation table contains info about the video conversation cards associated with an account.
|
id
|
|
updated_at
|
|
account_id
Reference:
|
|
card_type
|
|
card_uri
|
|
created_at
|
|
deleted
|
|
first_cta
|
|
first_cta_tweet
|
|
media_key
|
|
media_url
|
|
name
|
|
poster_media_url
|
|
thank_you_text
|
|
title
|
|
video_height
|
|
video_owner_id
Reference: |
|
video_width
|
cards_video_direct_message
| Replication Method : |
Key-based Incremental |
Replication Key :
|
updated_at |
|
Primary Key :
|
id |
API endpoint : |
The cards_video_direct_message table contains info about the video direct message cards associated with an account.
|
id
|
|
updated_at
|
|
account_id
Reference:
|
|
card_type
|
|
card_uri
|
|
created_at
|
|
deleted
|
|
first_cta
|
|
first_cta_welcome_message_id
|
|
media_key
|
|
media_url
|
|
name
|
|
poster_media_url
|
|
recipient_user_id
Reference: |
|
video_owner_id
Reference: |
cards_video_website
| Replication Method : |
Key-based Incremental |
Replication Key :
|
updated_at |
|
Primary Key :
|
id |
API endpoint : |
The cards_video_website table contains info about the video website cards associated with an account.
|
id
|
|
updated_at
|
|
account_id
Reference:
|
|
card_type
|
|
card_uri
|
|
content_duration_seconds
|
|
created_at
|
|
deleted
|
|
media_key
|
|
media_url
|
|
name
|
|
poster_media_url
|
|
title
|
|
video_height
|
|
video_owner_id
Reference: |
|
video_poster_height
|
|
video_poster_width
|
|
video_width
|
|
website_dest_url
|
|
website_display_url
|
|
website_shortened_url
|
|
website_url
|
cards_website
| Replication Method : |
Key-based Incremental |
Replication Key :
|
updated_at |
|
Primary Key :
|
id |
API endpoint : |
The cards_website table contains info about the website cards associated with an account.
|
id
|
|
updated_at
|
|
account_id
Reference:
|
|
card_type
|
|
card_uri
|
|
created_at
|
|
deleted
|
|
image_display_height
|
|
image_display_width
|
|
media_key
|
|
media_url
|
|
name
|
|
website_dest_url
|
|
website_display_url
|
|
website_shortened_url
|
|
website_title
|
|
website_url
|
content_categories
| Replication Method : |
Full Table |
Primary Key :
|
id |
| API endpoint : | |||
The content_categories table contains info about the content categories used as targeting criteria for ad groups.
|
id
|
|
iab_categories
|
|
name
|
EXAMPLE_CUSTOM_REPORT
| Replication Method : |
Key-based Incremental |
Replication Key :
|
end_time |
|
Primary Key :
|
_sdc_dimensions_hash_key |
Official docs : | |
| Loading Behavior: | |||
This is an example of a table created from a custom report configured in the integration’s settings page.
Metric columns in report tables depend on the entity selected for the report.
When data is extracted for reports, Stitch uses the Attribution Window defined in the integration’s settings.
|
_sdc_dimensions_hash_key
Applicable only to Twitter Ads integrations, this column is a a Stitch-generated MD5 hash that should be used as a Primary Key in tables created using the Custom reports feature. The hash consists of a UTF-8 encoded JSON list containing of the report’s dimensions. |
|
end_time
|
|
METRICS_YOU_SELECT
The available metrics depend on the entity you select for the report. Refer to the Entity and metric group compatibility reference for more info. |
|
account_id
Reference:
|
|
country
|
|
entity
The entity selected for the report. Refer to the Entity and metric group compatibility reference for more info. Possible values are:
|
|
entity_id
The name of the entity selected for the report. |
|
granularity
The granularity selected for the report. Possible values are:
|
|
placement
|
|
platform
|
|
report_name
|
|
segment_name
|
|
segment_value
|
|
segmentation_type
|
funding_instruments
| Replication Method : |
Key-based Incremental |
Replication Key :
|
updated_at |
|
Primary Key :
|
id |
API endpoint : |
The funding_instruments table contains info about the funding instruments associated with an account.
|
id
Reference: |
|
|
updated_at
|
|
|
able_to_fund
|
|
|
account_id
Reference:
|
|
|
created_at
|
|
|
credit_limit_local_micro
|
|
|
credit_remaining_local_micro
|
|
|
currency
|
|
|
deleted
|
|
|
description
|
|
|
end_time
|
|
|
entity_status
|
|
|
funded_amount_local_micro
|
|
|
io_header
|
|
|
reasons_not_able_to_fund
|
|
|
start_time
|
|
|
type
|
iab_categories
| Replication Method : |
Full Table |
Primary Key :
|
id |
| API endpoint : | |||
The iab_categories table contains info about the app categories associated with ad groups.
|
id
Reference: |
|
name
|
|
parent_id
|
line_items
| Replication Method : |
Key-based Incremental |
Replication Key :
|
updated_at |
|
Primary Key :
|
id |
API endpoint : |
The line_items table contains info about the line items (ad groups) associated with an account.
|
id
Reference: |
|
updated_at
|
|
account_id
Reference:
|
|
advertiser_domain
|
|
advertiser_user_id
|
|
automatically_select_bid
|
|
bid_amount_local_micro
|
|
bid_type
|
|
bid_unit
|
|
campaign_id
Reference: |
|
categories
|
|
charge_by
|
|
created_at
|
|
creative_source
|
|
currency
|
|
deleted
|
|
end_time
|
|
entity_status
|
|
name
|
|
objective
|
|
optimization
|
|
placements
|
|
primary_web_event_tag
|
|
product_type
|
|
start_time
|
|
target_cpa_local_micro
|
|
total_budget_amount_local_micro
|
|
tracking_tags
line_items (table), tracking_tags (attribute)
|
line_item_apps
| Replication Method : |
Key-based Incremental |
Replication Key :
|
updated_at |
|
Primary Key :
|
id |
API endpoint : |
The line_item_apps table contains info about the apps associated with line items associated with an account.
|
id
|
|
updated_at
|
|
account_id
Reference:
|
|
app_store_identifier
|
|
created_at
|
|
deleted
|
|
line_item_id
Reference: |
|
os_type
|
media_creatives
| Replication Method : |
Key-based Incremental |
Replication Key :
|
updated_at |
|
Primary Key :
|
id |
API endpoint : |
The media_creatives table contains info about the media creatives associated with an account.
|
id
|
|
updated_at
|
|
account_id
Reference:
|
|
account_media_id
Reference: |
|
approval_status
|
|
created_at
|
|
deleted
|
|
landing_url
|
|
line_item_id
Reference: |
|
serving_status
|
preroll_call_to_actions
| Replication Method : |
Key-based Incremental |
Replication Key :
|
updated_at |
|
Primary Key :
|
id |
API endpoint : |
The preroll_call_to_actions table contains info about the preroll call-to-actions associated with line items (ad groups) associated with an account.
|
id
|
|
updated_at
|
|
account_id
Reference:
|
|
call_to_action
|
|
call_to_action_url
|
|
created_at
|
|
deleted
|
|
line_item_id
Reference: |
promotable_users
| Replication Method : |
Key-based Incremental |
Replication Key :
|
updated_at |
|
Primary Key :
|
id |
API endpoint : |
The promotable_users table contains info about the promotable users associated with an account.
|
id
|
|
updated_at
|
|
created_at
|
|
deleted
|
|
promotable_user_type
|
|
user_id
Reference: |
promoted_accounts
| Replication Method : |
Key-based Incremental |
Replication Key :
|
updated_at |
|
Primary Key :
|
id |
API endpoint : |
The promoted_accounts table contains info about the promoted accounts associated with line items (ad groups) associated with an account.
|
id
|
|
updated_at
|
|
account_id
Reference:
|
|
approval_status
|
|
created_at
|
|
deleted
|
|
entity_status
|
|
line_item_id
Reference: |
|
user_id
Reference: |
promoted_tweets
| Replication Method : |
Key-based Incremental |
Replication Key :
|
updated_at |
|
Primary Key :
|
id |
API endpoint : |
The promoted_tweets table contains info about references to Tweets associated with line items (ad groups) associated with an account.
|
id
|
|
updated_at
|
|
account_id
Reference:
|
|
approval_status
|
|
created_at
|
|
deleted
|
|
entity_status
|
|
line_item_id
Reference: |
|
tweet_id
Reference: |
scheduled_promoted_tweets
| Replication Method : |
Key-based Incremental |
Replication Key :
|
updated_at |
|
Primary Key :
|
id |
API endpoint : |
The scheduled_promoted_tweets table contains info about the scheduled promoted Tweets associated with an account.
|
id
|
|
updated_at
|
|
account_id
Reference:
|
|
created_at
|
|
deleted
|
|
line_item_id
Reference: |
|
scheduled_tweet_id
|
|
tweet_id
Reference: |
tailored_audiences
| Replication Method : |
Key-based Incremental |
Replication Key :
|
updated_at |
|
Primary Key :
|
id |
API endpoint : |
The tailored_audiences table contains info about the Tailored Audiences associated with an account.
|
id
|
|
|
updated_at
|
|
|
account_id
Reference:
|
|
|
audience_size
|
|
|
audience_type
|
|
|
created_at
|
|
|
deleted
|
|
|
is_owner
|
|
|
name
|
|
|
partner_source
|
|
|
permission_level
|
|
|
reasons_not_targetable
|
|
|
targetable
|
|
|
targetable_types
|
targeting_app_store_categories
| Replication Method : |
Full Table |
Primary Key :
|
targeting_value |
| API endpoint : | |||
The targeting_app_store_categories table contains info about the app store targeting categories associated with promoted products.
|
targeting_value
|
|
name
|
|
os_type
|
|
targeting_type
|
targeting_conversations
| Replication Method : |
Full Table |
Primary Key :
|
targeting_value |
| API endpoint : | |||
The targeting_conversations table contains info about the conversation-based targeting criteria for Promoted Products.
|
targeting_value
|
|
conversation_type
|
|
name
|
|
targeting_type
|
targeting_criteria
| Replication Method : |
Full Table |
Primary Key :
|
id : line_item_id |
| API endpoint : | |||
The targeting_criteria table contains info about the targeting criteria associated with an account.
|
id
|
|
line_item_id
Reference: |
|
account_id
Reference:
|
|
created_at
|
|
deleted
|
|
name
|
|
operator_type
|
|
tailored_audience_expansion
|
|
tailored_audience_type
|
|
targeting_type
|
|
targeting_value
|
|
updated_at
|
targeting_devices
| Replication Method : |
Full Table |
Primary Key :
|
targeting_value |
| API endpoint : | |||
The targeting_devices table contains info about the device-based targeting criteria for Promoted Products.
|
targeting_value
|
|
manufacturer
|
|
name
|
|
os_type
|
|
targeting_type
|
targeting_interests
| Replication Method : |
Full Table |
Primary Key :
|
targeting_value |
| API endpoint : | |||
The targeting_interests table contains info about the interest-based targeting criteria for Promoted Products.
|
targeting_value
|
|
name
|
|
targeting_type
|
targeting_languages
| Replication Method : |
Full Table |
Primary Key :
|
targeting_value |
| API endpoint : | |||
The targeting_languages table contains info about the language-based targeting criteria for Promoted Products.
|
targeting_value
|
|
name
|
|
targeting_type
|
targeting_locations
| Replication Method : |
Full Table |
Primary Key :
|
targeting_value |
| API endpoint : | |||
The targeting_locations table contains info about location-based targeting criteria for Promoted Products. According to Twitter Ads’s documentation, geo-targeting is available for Promoted Accounts and Tweets at the country, state/region, city, and postal code levels.
|
targeting_value
|
|
country_code
|
|
location_type
|
|
name
|
|
targeting_type
|
targeting_network_operators
| Replication Method : |
Full Table |
Primary Key :
|
targeting_value |
| API endpoint : | |||
The targeting_network_operators table contains info about network operator-based targeting criteria for Promoted Products.
|
targeting_value
|
|
country_code
|
|
name
|
|
targeting_type
|
targeting_platforms
| Replication Method : |
Full Table |
Primary Key :
|
targeting_value |
| API endpoint : | |||
The targeting_platforms table contains info about platform-based targeting criteria for Promoted Products.
|
targeting_value
|
|
name
|
|
targeting_type
|
targeting_platform_versions
| Replication Method : |
Full Table |
Primary Key :
|
targeting_value |
| API endpoint : | |||
The targeting_platform_versions table contains info about mobile OS-version based targeting criteria for Promoted Products.
|
targeting_value
|
|
name
|
|
number
|
|
os_type
|
|
targeting_type
|
targeting_tv_markets
| Replication Method : |
Full Table |
Primary Key :
|
locale |
| API endpoint : | |||
The targeting_tv_markets table contains info about TV markets where TV shows can be targeted. Use the targeting_tv_shows table for info about individual TV shows.
|
locale
|
|
country_code
|
|
name
|
targeting_tv_shows
| Replication Method : |
Full Table |
Primary Key :
|
targeting_value |
| API endpoint : | |||
The targeting_tv_shows table contains info about TV-show based targeting criteria for Promoted Products.
|
targeting_value
|
|
genre
|
|
locales
The TV market locales the TV show is associated with. Use these values to join records from this table to the In the format |