0dd3111a47
* test: create test state initialization * feat: add lookback_window configuration and logic * fix: pendulum subtract method used instead of minus * style: rename _get_start_date * docs: explain parameter meaning * fix: add lookback_window param in invalid_config json * chore: bump connector version in Dockerfile * fix start_date subtract * Automated Change * Remove comparision * auto-bump connector version --------- Co-authored-by: Moguero <thibault.latrace@gmail.com> Co-authored-by: Octavia Squidington III <octavia-squidington-iii@users.noreply.github.com>
2.9 KiB
Core streams
Bing Ads is a SOAP based API. Connector is implemented with SDK library
Connector has such core streams, and all of them support full refresh only:
Report streams
Connector also has report streams, which support incremental sync.
- AccountPerformanceReport
- AdPerformanceReport
- AdGroupPerformanceReport
- CampaignPerformanceReport
- BudgetSummaryReport
- KeywordPerformanceReport
To be able to pull report data you need to generate 2 separate requests.
-
First - to request appropriate report
-
Second - to poll acatual data. Report download timeout is 5 min
Initially all fields in report streams have string values, connector uses reports.REPORT_FIELD_TYPES collection to transform values to numerical fields if possible
Connector uses reports_start_date config for initial reports sync and current date as an end data.
Connector has hourly_reports, daily_reports, weekly_reports, monthly_reports report streams. For example account_performance_report_daily, ad_group_performance_report_weekly. All these reports streams will be generated on execute.
If lookback_window is set to a non-null value, initial reports sync will start at reports_start_date - lookback_window. Following reports sync will start at cursor_value - lookback_window.
Request caching
Based on library
Connector uses caching for these streams:
- Account
- Campaign
- AdGroup
See this link for the nuances about the connector.