KampányMűvek / 19 September 2026
Marketing data reached the Workshop, while Google API logic stayed in the Engine
The native KampányMűvek Workshop gained GA4 and Google Ads views without moving authentication, data fetching or report normalization out of the CLI layer.
Situation
Website development and production delivery already worked through a shared platform, but evaluating marketing performance still required switching to separate Google interfaces. The obvious shortcut would have been to make the SwiftUI client call Google APIs directly. That would have broken the Workshop's most important contract: the desktop application must remain a presentation and command-launching layer.
Approach
We built the integration into the KampányMűvek Engine, covering site-specific configuration, authorization and error states, and normalized GA4 and Ads reports. SwiftUI now invokes CLI commands and renders their structured responses. The interface exposes time windows, traffic metrics, campaign spending, clicks, average CPC and conversions. We validated the reporting path with real account data rather than relying entirely on mock responses.
Outcome
The Workshop can present website traffic and advertising performance in one place without embedding OAuth credentials or business rules in the native application. The first real reports also exposed an important business question: advertising spend and clicks can be measurable even when recorded conversions remain at zero.