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

Community

Connector Improvement: Columns are missing in Linkedin Connector

Answered
Shivakumara Avadhani User

Following columns are not present ad_analytics_by_campaign

1. DATERANGE
2. DOCUMENTCOMPLETIONS
3. DOCUMENTMIDPOINTCOMPLETIONS
4. DOCUMENTTHIRDQUARTILECOMPLETIONS
5. DOWNLOADCLICKS
6. PIVOTVALUES"

Following columns are not present in either of these tables
campaign_history
campaign_serving_status_history

1. SERVINGSTATUS
2. TARGETINGCRITERIA
3. TOTALBUDGET

Please sign in to leave a comment.

Comments

3 comments

Date Votes
  • Official comment
    Lucas Alexander Fivetranner

    Hi Shivakumara,

    Thanks for submitting this feature request. 2-5 in your first list for ad_analytics_by_campaign makes sense. I've added these to our backlog. 

    I'm curious why you need 'DATERANGE', given that we're already syncing a day column for every row. 'PIVOTVALUES' is what we use to sync the other tables in the schema (e.g. AD_ANALYTICS_BY_CREATIVE_WITH_CONVERSION_BREAKDOWN uses the CONVERSION pivot and PIVOTVALUES).

    I'm also curious why you need 'SERVINGSTATUS' in campaign_history and campaign_serving_status_history. The CAMPAIGN_SERVING_STATUS_HISTORY in the schema contains the serving statuses for all campaigns. We don't store this directly in the CAMPAIGN_HISTORY table because it is an array.

    I've also added 'TARGETINGCRITERIA' and 'TOTALBUDGET' to our backlog. The former will require a breakout table, as each campaign can have multiple targeting criteria.

    Please review my response regarding DATARANGE, PIVOTVALUES, and SERVINGSTATUS and let me know what you think. 

    Cheers,
    Luke

  • Shivakumara Avadhani User

    Hi Lucas,

    Thank you for the detailed explanation.

    • If DateRange is the same as Day, then this field is fine. If we are using PIVOTVALUES to sync other tables in the schema, we can ignore this field. For the last field, if the serving status matches the status in campaign_serving_status_history, then these fields are good. Could you please help us add the remaining fields to ad_analytics_by_campaign:

      • DOCUMENTCOMPLETIONS
      • DOCUMENTMIDPOINTCOMPLETIONS
      • DOCUMENTTHIRDQUARTILECOMPLETIONS
      • DOWNLOADCLICKS

    • Additionally, please add the following fields to the appropriate table (campaign_history or campaign_serving_status_history):

      • TARGETINGCRITERIA
      • TOTALBUDGET

    Thanks and Regards,
    Shivakumara K A

  • Lucas Alexander Fivetranner

    Hi Shivakumara,

    Thanks for the follow-up. A couple of updates on the fields you requested.

    For TARGETINGCRITERIA, this data is actually already available in the schema via two dedicated tables: TARGETING_CRITERIA_INCLUDE_HISTORY and TARGETING_CRITERIA_EXCLUDE_HISTORY. We model it this way because a single campaign can have multiple targeting criteria, so a direct column on CAMPAIGN_HISTORY wouldn't capture the full structure. Both tables join to CAMPAIGN_HISTORY on campaign_id and campaign_last_modified_time, and each row contains a facet_name and facet_value pair representing a single targeting criterion. TARGETING_CRITERIA_INCLUDE_HISTORY also has an index column indicating the position of the criterion.

    For TOTALBUDGET, we have this on our backlog and plan to add it to CAMPAIGN_HISTORY.

    For the four analytics fields you requested on AD_ANALYTICS_BY_CAMPAIGN, all four are on our backlog as well:

    • DOCUMENTCOMPLETIONS
    • DOCUMENTMIDPOINTCOMPLETIONS
    • DOCUMENTTHIRDQUARTILECOMPLETIONS
    • DOWNLOADCLICKS

    I'll update this thread once these changes ship. Thanks again for the detailed report.

    Cheers,
    Luke