TTD: Ingest Scheduled Reports
PlannedWhich connector?:the trade desk
Additional details: right now we choose a custom report, then it gets scheduled by Fivetran and it's ingested.
But some reports are more complex and require customization while creating the schedule itself, for example, adding conversion pixel names.
I think that the easies way is to allow us to choose existing scheduled reports similarly to how we can do it for custom reports.
-
Official comment
Hi Jose,
Thanks for flagging this.
I looked into how existing schedules get picked up and found the issue. The connector already fetches every schedule on your account on each sync, including ones you configure directly in The Trade Desk, not just ones Fivetran creates. But because your connection uses
Block Allschema change handling, a schedule you set up yourself in The Trade Desk never gets registered as an available table for you to enable. Currently, the list of tables available to sync is built after our platform filters out tables viaBlock All. We added a quick workaround to at least sync the schedules Fivetran created. We haven't addressed this issue yet for the schedules created within The Trade Desk.This is a known gap, and there's a fix planned for an upcoming sprint that addresses exactly this. Once implemented, the connector will sync the full schedule list into the connector's configuration on every run, so any schedule, including ones you configure yourself, shows up on the schema tab regardless of your schema change handling setting. I don't have a firm date yet, but it's on the near-term roadmap.
Thanks again for submitting this; it helped pin down exactly where this breaks.
Cheers,
Luke
Please sign in to leave a comment.
Comments
1 comment