Skip to main content

Community

Connector Improvement: Microsoft Ads Improvements

Answered

Please sign in to leave a comment.

Comments

3 comments

  • Official comment

    Hi Denton, Drew from the Product Team here!

    Thanks for sharing this feedback, I have a few followup questions:

    The Account Name and Campaign Name are not available columns:

    • we have separated the campaign_name into the campaign_history table to preserve normalization of the data.
    • thanks for sharing information about the missing data in campaign_history. We will look into this.

    The report has conversions, revenue, all conversions, and all revenue as available columns, but the goal name is not available:

    • would exploring the addition conversions and revenue solve this problem?
    • we could also solve this with a dbt package, is that something you would find useful?

    Hi Drew,

    The Account Name and Campaign Name are not available columns:

    • "we have separated the campaign_name into the campaign_history table to preserve normalization of the data."  Can you help me better understand how that helps preserve normalization of the data?
    • "thanks for sharing information about the missing data in campaign_history. We will look into this." - Thank you! 

    The report has conversions, revenue, all conversions, and all revenue as available columns, but the goal name is not available:

    • "would exploring the addition conversions and revenue solve this problem?"  Do you mean adding this to the "goals_and_funnels_daily_report" report?  If so, I think this would be a good addition.  However, this does not help solve the issue described.  The real gap is that the campaign_performance_daily_report schema simply does not contain the full data set available in the API.  Here is a link to the CampaignPerformanceReportColumn Value Set from Microsoft: https://docs.microsoft.com/en-us/advertising/reporting-service/campaignperformancereportcolumn?view=bingads-13 - To build a robust campaign report using Fivetran Data, you must rely on multiple schemas which makes it unnecessarily complicated to get a useable dataset + it dramatically increases the number of rows in each sync.
    • I have not used a dbt package before, so I am not sure if this would be helpful or not.

    Thanks,

    Denton