Summary
The user reports a bug where the Facebook Marketing source schema incorrectly sets ‘ad_id’ as the primary key for custom streams, regardless of the selected breakdown level, and the ‘ad_id’ field in BigQuery is always null.
Question
Hi all!
When adding custom insights to Facebook Marketing source, the schema seems to always set the custom streams’ schema with an ‘ad_id’ as primary key, even when selecting ‘campaign_id’ or other as the breakdown level. Furthermore, the ‘ad_id’ field in the final BigQuery table is always null, even when selecting ‘ad_id’ as the breakdown dimension level. Am I the only one experiencing this?
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.
Join the conversation on Slack
['facebook-marketing', 'custom-insights', 'schema-issue', 'bigquery', 'ad-id']
I couldn’t find any open issues reporting this problem. My suggestion, <@U066U84SC0P>, is to open a GitHub issue and share all the relevant information you have, such as the Facebook App version you’re using and the custom insight report JSON. Once you have it opened, please share it here. I’ll ask the connector team to take a look.
<@U01MMSDJGC9> thank you for the reply! When looking around in the source’s code, I found a native stream with breakdowns that covered my needs (its name was not so intuitive so I didn’t see it at first). Only had to tweak the page size parameter so to not get a “too many rows” errors.
If I ever need to mess with custom insights again, I’ll open the issue (if not fixed by then 
). Thanks again