Add TikTok Ads reporting source
Implemented a Connector-V2 batch source for TikTok Ads BASIC and AUCTION_AD reporting, including ad-level spend, impressions, clicks, optional daily dimensions, and exact numeric mapping.
apache/seatunnel · #12283
Advertising-data connector feature
SeaTunnel can now ingest bounded TikTok Ads reports with exact metrics, pagination safeguards, retries, and cross-engine coverage.
Problem
SeaTunnel had no supported TikTok Ads source. A production-oriented reporting path needed bounded responses, correct pagination and truncation handling, precise metric conversion, credential masking, cancellation, and predictable failure behavior.
Approach
Adds the source factory, configuration, report client, single-reader execution, retries and deadlines, connector packaging, bilingual documentation, and mock-backed engine E2E coverage. The initial scope supports one advertiser and synchronous reports without arbitrary filters.
Impact and scope
- Enables repeatable ingestion of TikTok Ads performance data into SeaTunnel pipelines.
- Protects reporting accuracy through exact numeric mapping and explicit pagination and truncation checks.
- Integrates through SeaTunnel's standard distribution and engine paths rather than as a connector-local proof of concept.
Validation
- Eighty-five unit tests and one packaged SPI/HTTP integration test passed on both Java 8 and Java 11.
- Mock-backed E2E tests passed on Zeta, Flink 1.18, and Spark 3.3, alongside formatting and whitespace checks.
- A SeaTunnel maintainer approved the feature, and the GitHub-verified merge commit credits Goutam Adwant. No live advertiser validation is claimed; GH-10753 remains open as the connector umbrella.