Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: Clarification on data separation between Twitter Ads and Twitter Organic connectors

Answered
ABEMA ABEMA User

We understand that Fivetran provides separate connectors for Twitter Ads and Twitter Organic. However, we would like to confirm the following:

  • Are the data schemas  separated between these two connectors, with no overlap?
  • Does the Twitter Organic connector include any paid/ads data, or vice versa?

If there is any overlap, we would like to request that the data be separated so that organic and paid metrics can be analyzed independently without additional filtering.

Thank you.

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Official comment
    Lucas Alexander Fivetranner

    Hi Abema,

    I'll answer your two questions first:

    1. Yes, there is table overlap between Twitter Organic and Twitter Ads for several tables. ACCOUNT_HISTORY uses the same endpoint (accounts) in both connectors. CARD_HISTORY is also essentially the same. TWEET is also shared as a table name, and uses the same endpoint, but we pass different parameters. Organic calls accounts/{account_id}/tweets?timeline_type=ORGANIC, while Ads calls accounts/{account_id}/tweets?timeline_type=ALL (so Ads includes both paid-context and organic tweets in that base tweet pull).
    2. No paid/ads metric groups are included in the Organic connector’s reporting schema.

    Based on that information, do you still need further separation? Can you elaborate a bit on what you would like changed and what your use case is that requires that?

    Thanks,
    Luke