Hi Maria,

Thanks for submitting this feature request. 

The API we use to fetch the creative report data doesn't return the creative name. We generally avoid combining data from multiple endpoints to populate a single table because it can lead to degraded performance and more rate limiting. We also prioritize normalization where possible. In this case, the creative name is already synced to the creative_history table (name column). You can join creative_history using the foreign key, creative_id, in the report table. 

For more information, you can refer to our ERD: https://fivetran.com/connector-erd/linkedin_ads.

Hope this helps,
Luke