Destination Improvement: Add account-level ID 'key' column across paid search and social connector tables
Not planned
Currently, only paid search and paid social ad_group_ad_history tables include key ID columns across all levels of granularity (customer_id, ad_group_id, campaign_id). This makes finding data at the account (id, or customer) level across all 150+ Fivetran tables time consuming and inefficient, and introduces complexity in high-priority instances where client-owned data policies require data to be deleted or managed as a whole.
Adding a customer_id column across every destination table associated with Google, Linkedin, Meta, Microsoft, Pinterest, and TikTok would greatly simplify the ability to isolate data by client across all table and add a consistent 'key' across all tables for ease of use.
-
Official comment
Hi Sam,
Luke from the Product team here. Thanks for submitting this request!
Your suggestion to add a customer_id column across all destination tables for various platforms is insightful and makes sense for streamlining data management when you need to delete data for your clients.However, at this time, this feature isn't on our roadmap. This would introduce a lot of redundant data to the downstream schemas of all Fivetran customers. Our schema design principles seek to avoid redundancy.
However, if there is significant demand for this feature from Fivetran customers, we will reconsider this stance.Cheers,
Luke
Please sign in to leave a comment.
Comments
1 comment