Twitter Ads

ON THIS PAGE

Hevo can replicate your Twitter Ads’ data to your data warehouse using Twitter API.

Note: For Pipelines created with this Source, Hevo provides you a fully-managed BigQuery data warehouse Destination if you do not already have one set up. You are only charged the cost that Hevo incurs for your project in Google BigQuery. The invoice is generated at the end of each month and payment is recovered as per the payment instrument you have set up. You can now create your Pipeline and directly start analyzing your Source data. Read Hevo Managed Google BigQuery .

Setup

Steps at Twitter

  • Step 1 : Apply for a developer account

    1. To connect Twitter Ads to Hevo, you need a Twitter app with access to the Twitter Ads API. If you already have a developer account, skip ahead to Step 2.
    2. Go to Twitter’s Apply for access page.
    3. Select Apply for a developer account.
    4. Select Build customized solutions in-house.
    5. Input your organization details and explain how you intend to use the Twitter data in subsequent application screens. For the use case description field, we recommend using the following paragraph:
      We will use Twitter API to pull our advertising data and load it into our data warehouse for internal analytics purposes. My organization is keen to understand our ads' performance on Twitter and also perform comparative analysis with other ads platforms. We will be only pulling data out of Twitter and don't plan to trigger any action on the platform.

    Note: It may take few days for Twitter to approve your developer account.

  • Step 2 : Create a Twitter Application
    1. If you already have an application that you can use to connect to HEVO, skip to Step 3.
    2. After your developer account is approved, go to Twitter’s Create Application page to create a Twitter app.
    3. In the Website URL field, fill https://hevodata.com/
    4. In the Tell us how this app will be used field, you can fill the following: This application will be used to pull analytics on the advertising that I run on the Twitter platform in order to analyse performance.
  • Step 3 : Submit the Advertising API License Agreement form
    1. Navigate to the Advertising Api License Agreement.
    2. Fill and submit the form.
  • Step 4 : Generate keys and tokens for your account
    1. Go to your Twitter App Dashboard.
    2. Select the application that you created in Step 2.
    3. Click on the Keys and tokens tab
    4. Create your keys and tokens.
    5. Make a note of these keys and tokens. You will need them to configure Twitter Ads source at HEVO.

Steps at HEVO

  1. Select Pipelines in the left pane and click Create Pipeline to create a pipeline.
  2. Select Twitter Ads as a source type to continue.
  3. Pipeline Name: A unique name for your Twitter Ads pipeline
  4. Enter the following keys and tokens that you created: 
    Consumer Key
Consumer Secret
Access Token
Access Token Secret
  5. Select Accounts: Select accounts for which objects and reports need to be replicated
  6. Load Reports from specific countries: Toggle, if you want to load country level reports also
  7. Select Countries: Select countries for which country level reports need to be replicated(Campaigns’ targeted countries). There is a max limit of 10 countries.
  8. Select the destination where you want to replicate your Twitter Ads data or click on New Destination to create a new Destination.

Supported Objects and Reports

Hevo ingests the following data from your Twitter Ads account :

Objects

  • ACCOUNT
  • FUNDING_INSTRUMENT
  • CAMPAIGN
  • LINE_ITEM
  • PROMOTED_TWEET
  • MEDIA_CREATIVE

Reports

  • ACCOUNT_AGE_REPORT
  • ACCOUNT_APP_STORE_CATEGORY_REPORT
  • ACCOUNT_DEVICES_REPORT
  • ACCOUNT_EVENTS_REPORT
  • ACCOUNT_GENDER_REPORT
  • ACCOUNT_INTERESTS_REPORT
  • ACCOUNT_LOCATIONS_REPORT
  • ACCOUNT_PLATFORMS_REPORT
  • ACCOUNT_PLATFORM_VERSIONS_REPORT
  • ACCOUNT_POSTAL_CODES_REPORT
  • ACCOUNT_REGIONS_REPORT
  • CAMPAIGN_AGE_REPORT
  • CAMPAIGN_APP_STORE_CATEGORY_REPORT
  • CAMPAIGN_CONVERSION_TAGS_REPORT
  • CAMPAIGN_DEVICES_REPORT
  • CAMPAIGN_EVENTS_REPORT
  • CAMPAIGN_GENDER_REPORT
  • CAMPAIGN_INTERESTS_REPORT
  • CAMPAIGN_KEYWORDS_REPORT
  • CAMPAIGN_LANGUAGES_REPORT
  • CAMPAIGN_LOCATIONS_REPORT
  • CAMPAIGN_PLATFORMS_REPORT
  • CAMPAIGN_PLATFORM_VERSIONS_REPORT
  • CAMPAIGN_POSTAL_CODES_REPORT
  • CAMPAIGN_REGIONS_REPORT
  • CAMPAIGN_SIMILAR_TO_FOLLOWERS_OF_USER_REPORT
  • CAMPAIGN_TV_SHOWS_REPORT
  • FUNDING_INSTRUMENT_AGE_REPORT
  • FUNDING_INSTRUMENT_APP_STORE_CATEGORY_REPORT
  • FUNDING_INSTRUMENT_CONVERSION_TAGS_REPORT
  • FUNDING_INSTRUMENT_DEVICES_REPORT
  • FUNDING_INSTRUMENT_EVENTS_REPORT
  • FUNDING_INSTRUMENT_GENDER_REPORT
  • FUNDING_INSTRUMENT_INTERESTS_REPORT
  • FUNDING_INSTRUMENT_LOCATIONS_REPORT
  • FUNDING_INSTRUMENT_PLATFORMS_REPORT
  • FUNDING_INSTRUMENT_PLATFORM_VERSIONS_REPORT
  • FUNDING_INSTRUMENT_REGIONS_REPORT
  • LINE_ITEM_AGE_REPORT
  • LINE_ITEM_APP_STORE_CATEGORY_REPORT
  • LINE_ITEM_CONVERSION_TAGS_REPORT
  • LINE_ITEM_DEVICES_REPORT
  • LINE_ITEM_EVENTS_REPORT
  • LINE_ITEM_GENDER_REPORT
  • LINE_ITEM_INTERESTS_REPORT
  • LINE_ITEM_KEYWORDS_REPORT
  • LINE_ITEM_LANGUAGES_REPORT
  • LINE_ITEM_LOCATIONS_REPORT
  • LINE_ITEM_PLATFORMS_REPORT
  • LINE_ITEM_PLATFORM_VERSIONS_REPORT
  • LINE_ITEM_POSTAL_CODES_REPORT
  • LINE_ITEM_REGIONS_REPORT
  • LINE_ITEM_SIMILAR_TO_FOLLOWERS_OF_USER_REPORT
  • LINE_ITEM_TV_SHOWS_REPORT
  • PROMOTED_TWEET_AGE_REPORT
  • PROMOTED_TWEET_APP_STORE_CATEGORY_REPORT
  • PROMOTED_TWEET_CONVERSION_TAGS_REPORT
  • PROMOTED_TWEET_DEVICES_REPORT
  • PROMOTED_TWEET_EVENTS_REPORT
  • PROMOTED_TWEET_GENDER_REPORT
  • PROMOTED_TWEET_INTERESTS_REPORT
  • PROMOTED_TWEET_KEYWORDS_REPORT
  • PROMOTED_TWEET_LANGUAGES_REPORT
  • PROMOTED_TWEET_LOCATIONS_REPORT
  • PROMOTED_TWEET_PLATFORMS_REPORT
  • PROMOTED_TWEET_PLATFORM_VERSIONS_REPORT
  • PROMOTED_TWEET_POSTAL_CODES_REPORT
  • PROMOTED_TWEET_REGIONS_REPORT
  • PROMOTED_TWEET_SIMILAR_TO_FOLLOWERS_OF_USER_REPORT
  • PROMOTED_TWEET_TV_SHOWS_REPORT
  • MEDIA_CREATIVE_REPORT

Replication Window and Schedule

Objects

On the initial setup, Hevo replicates objects’ data once. Subsequently, objects are synced up once on a daily basis.

Reports

On the initial setup, Hevo replicates reports’ data for the last 90 days. Subsequently, reports are synced up on an hourly basis by default.

Reports sync frequency can be adjusted by changing the pipeline’s scheduled frequency.

Appendix

Objects Primary Key

Object Primary Key
ACCOUNT AccountId, Id
FUNDING_INSTRUMENT AccountId, Id
CAMPAIGN AccountId, Id
LINE_ITEM AccountId, Id
PROMOTED_TWEET AccountId, Id
MEDIA_CREATIVE AccountId, Id

Reports Primary Key

Report Primary Key
ACCOUNT_AGE_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
ACCOUNT_APP_STORE_CATEGORY_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
ACCOUNT_DEVICES_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT, PLATFORM_TARGET_VALUE
ACCOUNT_EVENTS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
ACCOUNT_GENDER_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
ACCOUNT_INTERESTS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
ACCOUNT_LOCATIONS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
ACCOUNT_PLATFORMS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
ACCOUNT_PLATFORM_VERSIONS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT, PLATFORM_TARGET_VALUE
ACCOUNT_POSTAL_CODES_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT, COUNTRY_TARGET_VALUE
ACCOUNT_REGIONS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT, COUNTRY_TARGET_VALUE
CAMPAIGN_AGE_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
CAMPAIGN_APP_STORE_CATEGORY_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
CAMPAIGN_CONVERSION_TAGS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
CAMPAIGN_DEVICES_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT, PLATFORM_TARGET_VALUE
CAMPAIGN_EVENTS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
CAMPAIGN_GENDER_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
CAMPAIGN_INTERESTS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
CAMPAIGN_KEYWORDS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
CAMPAIGN_LANGUAGES_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
CAMPAIGN_LOCATIONS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
CAMPAIGN_PLATFORMS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
CAMPAIGN_PLATFORM_VERSIONS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT, PLATFORM_TARGET_VALUE
CAMPAIGN_POSTAL_CODES_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT, COUNTRY_TARGET_VALUE
CAMPAIGN_REGIONS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT, COUNTRY_TARGET_VALUE
CAMPAIGN_SIMILAR_TO_FOLLOWERS_OF_USER_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
CAMPAIGN_TV_SHOWS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
FUNDING_INSTRUMENT_AGE_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
FUNDING_INSTRUMENT_APP_STORE_CATEGORY_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
FUNDING_INSTRUMENT_CONVERSION_TAGS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
FUNDING_INSTRUMENT_DEVICES_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT, PLATFORM_TARGET_VALUE
FUNDING_INSTRUMENT_EVENTS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
FUNDING_INSTRUMENT_GENDER_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
FUNDING_INSTRUMENT_INTERESTS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
FUNDING_INSTRUMENT_LOCATIONS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
FUNDING_INSTRUMENT_PLATFORMS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
FUNDING_INSTRUMENT_PLATFORM_VERSIONS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT, PLATFORM_TARGET_VALUE
FUNDING_INSTRUMENT_REGIONS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT, COUNTRY_TARGET_VALUE
LINE_ITEM_AGE_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
LINE_ITEM_APP_STORE_CATEGORY_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
LINE_ITEM_CONVERSION_TAGS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
LINE_ITEM_DEVICES_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT, PLATFORM_TARGET_VALUE
LINE_ITEM_EVENTS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
LINE_ITEM_GENDER_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
LINE_ITEM_INTERESTS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
LINE_ITEM_KEYWORDS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
LINE_ITEM_LANGUAGES_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
LINE_ITEM_LOCATIONS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
LINE_ITEM_PLATFORMS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
LINE_ITEM_PLATFORM_VERSIONS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT, PLATFORM_TARGET_VALUE
LINE_ITEM_POSTAL_CODES_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT, COUNTRY_TARGET_VALUE
LINE_ITEM_REGIONS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT, COUNTRY_TARGET_VALUE
LINE_ITEM_SIMILAR_TO_FOLLOWERS_OF_USER_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
LINE_ITEM_TV_SHOWS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
PROMOTED_TWEET_AGE_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
PROMOTED_TWEET_APP_STORE_CATEGORY_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
PROMOTED_TWEET_CONVERSION_TAGS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
PROMOTED_TWEET_DEVICES_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT, PLATFORM_TARGET_VALUE
PROMOTED_TWEET_EVENTS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
PROMOTED_TWEET_GENDER_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
PROMOTED_TWEET_INTERESTS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
PROMOTED_TWEET_KEYWORDS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
PROMOTED_TWEET_LANGUAGES_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
PROMOTED_TWEET_LOCATIONS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
PROMOTED_TWEET_PLATFORMS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
PROMOTED_TWEET_PLATFORM_VERSIONS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT, PLATFORM_TARGET_VALUE
PROMOTED_TWEET_POSTAL_CODES_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT, COUNTRY_TARGET_VALUE
PROMOTED_TWEET_REGIONS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT, COUNTRY_TARGET_VALUE
PROMOTED_TWEET_SIMILAR_TO_FOLLOWERS_USER_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
PROMOTED_TWEET_TV_SHOWS_REPORT ACCOUNT_ID, ENTITY_ID, DATE, SEGMENT_NAME, PLACEMENT
MEDIA_CREATIVE_REPORT ACCOUNT_ID, ENTITY_ID, DATE, PLACEMENT
Last updated on 20 Oct 2020
Was this page helpful?

Thank you for helping improve Hevo's documentation. If you need help or have any questions, please consider contacting support.