Lakeflow connect Native connectors (tik, meta ads, Google Ads) - one table per account
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2026 01:55 PM
We want to leverage these connectors to pull in marketing spend data. But the docs seem to say that the destination must be unique based on accounts. For Tik, we have a hundred accounts... each account will have a destination table for each object. So like this...
- ads_account1, campaign_account1
- ads_account2, campaign_account2
Total tables is accounts * number of objects. 100 accounts and assuming 6 tables means 600 tables!
Is there a better solution? Would be great to ingest into only one table... all ads for an accounts feed into one Ads table.
Managed ingestion connectors don't support duplicate destination table names in the same schema
also, forum says:
> The message subject contains t*i*k*t*o*k, which is not permitted in this community. Please remove this content before sending your post.
- Labels:
-
Delta Lake