Twitter Ads helps you reach potential customers, gain more followers, and measure results in real time. With promoted Tweets, you can reach the right audience by targeting based on interests, geography, gender, device, or users similar to your followers, and quickly grow your community. This article will give you an overview of the Grow/Twitter Ads integration.
Connecting to Twitter Ads
- Select the Data tab next to the Dashboard.
This takes you to the Data Overview page. - Click on the Connections button.
- Click on the blue Connect button at the end of the Your Top Data Sources options.
- From the list of Connections, search and select the Twitter Ads button.
A window pops up with the Twitter Ads login page. Sign in to your account and approve the connection to give Grow access to your account.
Data Warehousing
Twitter Ads is on the Grow Data Warehouse, which we highly recommend you use. For more information about warehousing your data, visit the Data Warehouse Help Article.
Tables
The list of tables available will depend on your unique Twitter Ads project. You can expect to see one table per dataset associated with the project Id in your connection. Below is an example:
Custom Tables
As the warehouse doesn't include any default table for Twitter Ads, you have to build your own custom tables.
Grow offers you the flexibility to configure custom tables based on the dimensions, metrics, and date groupings that you see fit. This helps you to bring only relevant data into Grow, increasing the performance of the metrics.
Note that Twitter Ads might limit the number of dimensions and metrics that can be selected within a single report.
- Campaigns
- Promoted Tweets
- Ad Groups
- Funding Instruments
Warehousing Your Data
-
In the Connections Overview page, click on your Twitter Ads connection.
This opens the Connection Details page. - Select the Manage Connection button inside the Connection Details section to open the warehouse table selection flow.
-
Select the data you want stored in the Data Warehouse and click the Sync & Store button at the bottom of the Manage Connection page.
This begins the initial population of your warehouse with the tables you defined. Populating your data warehouse for the first time may take a while, sometimes up to several hours.
You may continue working within the app while your data is In Queue or Processing.
If your data source is not already connected, refer to the Connecting to a Data Source for more details.
Sync Interval
Full Sync
Full sync intervals is 12 hours for Custom Tables.
Incremental Sync
Incremental sync is not supported for Custom Tables.
To learn more about sync intervals and how to adjust the default settings, please visit the Sync section of the Data Warehouse help article.
Endpoints
Instead of having set endpoints, Twitter Ads offers a combination of entities, placements, and metric groups.
There are four entities available: Campaign, Promoted tweet, Ad Groups, and Funding Instrument.
For placements, you can choose either All On Twitter or Publisher Network. Note that if you would like to see things such as total spend (among others), you'll need to pull both of these reports in and join them.
For metric groups, you can choose from the following options: Engagement, Web Conversion, Mobile Conversion, Media, Video, Lifetime Value Mobile Conversion, and Billing. Please note, however, that when you choose Funding Instrument as an entity, the only metric groups available are Engagement and Billing.
After choosing these three fields, an additional field will appear titled Individual Entities. You can choose these by clicking the Select Individual Entities button.
This will bring up a list of individual entities for the combination of entity, placement, and metric group you have chosen. Each combination pulls up a different set of individual entities. The data that pulls in will be based on the entities that you select for the combination of the other report settings.
Once everything is set-up, select the Date Range you want to pull.
FAQs + Tips and Tricks
Check out Twitter Ads Help Center documentation on common analytics discrepancies you may find.