Just wanted to follow up with this one.

Hi Kristen Allcorn, Drew from the product team here.

Thanks for this feature request and thank you for providing the links to the relevant documentation! These seem like fairly straightforward fields to add to the campaign_history, ad_group_history, and ad_history tables.

Could you provide a bit more detail on why you would like these fields in ad_performance_daily_report? Is this just due to the fields not being provided properly in the ad_history table? Typically we avoid providing this type of data in a report type table because it leads to denormalization.

Hi all,

We reviewed Microsoft's docs and confirmed that final_url_suffix can be added: https://learn.microsoft.com/en-us/advertising/bulk-service/campaign?view=bingads-13#finalurlsuffix. It's currently in our backlog. 

There is ambiguity for url_custom_parameters. There isn't a corresponding field in Microsoft's documentation: https://learn.microsoft.com/en-us/advertising/bulk-service/campaign?view=bingads-13. However, we see the following code snippet on that page:

// 'Custom Parameter' column header in the Bulk file
        UrlCustomParameters = new CustomParameters
        {
            // Each custom parameter is delimited by a semicolon (;) in the Bulk file
            Parameters = new[] 
            {
                new CustomParameter(){
                    Key = "promoCode",
                    Value = "PROMO1"
                },
                new CustomParameter(){
                    Key = "season",
                    Value = "summer"
                },
            },
        },

So, if url_custom_parameters is the same as custom_parameters - https://learn.microsoft.com/en-us/advertising/bulk-service/campaign?view=bingads-13#customparameter, we already sync it for the campaign_history table. But since this parameter contains many key-value pairs, we store them in the separate table campaign_custom_parameter_history.