Twelve million dollars of managed advertising spend is not twelve times harder than one million. It is a different category of problem.
At one million, a competent team optimises campaigns. At twelve million, spread across eleven industries and several currencies, the constraint stops being campaign quality and becomes governance: who is allowed to change what, how money reaches the platform, how spend maps to entities, and how anyone establishes what worked. Teams that scale without solving those four questions do not fail loudly. They plateau, and nobody can explain why.
This is an account of how we run the portfolio, written for people managing budgets at the same order of magnitude.
What the portfolio contains
The managed book spans tourism, insurance, financial services, real-estate investment advisory, fintech applications, ride-hailing, large-format retail, music and artist marketing, music copyright administration, official television broadcast channels, and beauty and cosmetics. Alongside the paid media sits a content ecosystem exceeding one million active subscribers.
Client identities are confidential. The sector spread is not, and it is the more useful information anyway — because the operational lessons come from the differences between those categories, not from any single account.
Consider what those differences actually mean in practice. A ride-hailing client optimises to installs and first completed trips, with demand that swings by weather and by hour. A real-estate investment advisory client optimises to qualified consultations on a sales cycle measured in months. An insurance client operates inside advertising restrictions that vary by market and by product. A cosmetics client lives and dies by creative refresh rate. A broadcast channel measures in watch time and subscriber growth rather than in conversions at all.
No single playbook covers that range. What transfers between them is not tactics. It is structure.
Account architecture is the first decision and the hardest to reverse
Most portfolio-level problems we inherit are architecture problems that surfaced eighteen months late.
The recurring failure is a single account carrying multiple markets, multiple brands, or multiple business models because that is how it started and nobody wanted to rebuild it. The consequences arrive gradually: conversion actions that mean different things sharing one column, automated bidding trained on incompatible signals, budget caps that cannot be enforced per business line, and reporting that requires a spreadsheet reconciliation nobody trusts.
Our operating principles:
One account per market-and-model combination. Not per country, and not per brand — per combination of the two. A single brand running lead generation in Türkiye and e-commerce in the Gulf needs two accounts, because the conversion definitions and the bidding signals have nothing in common.
Conversion actions defined before the first campaign is built. Every account gets a documented conversion schema, with primary and secondary actions declared explicitly and values assigned where a value exists. Retrofitting this onto a running account means discarding the learning history.
Naming conventions enforced at creation. Trivial at ten campaigns, load-bearing at four hundred. A naming convention that encodes market, funnel stage, and business line is what makes portfolio-level reporting possible without a data engineering project.
Change control at the account level. Who can alter budgets, bidding strategies, or conversion settings is a permissions decision, not a trust decision. At this volume, an unlogged bid strategy change is a five-figure event.
Funding: the part nobody writes about
Advertising platforms are not built for a Türkiye-based operator funding accounts across multiple jurisdictions and currencies. This is the layer that quietly caps growth for most agencies in the region, and it has nothing to do with marketing skill.
The problems are concrete. Payment methods get declined for cross-border reasons the platform will not explain. Accounts suspend for billing mismatches between the payment instrument and the registered entity. Currency of account and currency of card diverge, producing conversion costs that never appear in any campaign report. Spend attribution to the correct client entity breaks when several accounts share a funding source. Invoices must satisfy the tax requirements of the client's jurisdiction, not the operator's.
We solved this with dedicated card and wallet infrastructure rather than by improvising per client. Each managed account draws on a defined funding instrument, spend is attributable to a specific entity at source, and reconciliation happens against the platform's own billing records rather than against a bank statement someone has to interpret.
The result is that funding stops being an operational emergency and becomes a scheduled process. That sounds unglamorous. It is the single change that most reliably distinguishes portfolios that scale from portfolios that stall.
Governance: budget as a controlled variable
At portfolio scale, budget is not a number in a campaign field. It is a control system with several layers.
Committed budget — the amount contracted with the client for the period. Fixed.
Allocated budget — how that commitment distributes across markets, channels and campaign types. Reviewed monthly.
Pacing — where actual spend sits against allocation, tracked daily. Underspend is a failure with the same weight as overspend; an account that delivers 78% of committed budget has returned money the client could have deployed.
Reserve — a deliberately unallocated portion, typically five to ten per cent, held for opportunities that emerge mid-period. Portfolios without a reserve cannot respond to anything, because every reallocation requires taking money from something that is working.
The discipline is in the review cadence, not in the framework. Daily pacing, weekly performance, monthly allocation, quarterly structure. Anything reviewed less often than its rate of change is not being managed.
Attribution, honestly
Attribution at this scale is a measurement problem with no clean solution, and portfolios that claim otherwise are reporting model output as fact.
What we hold to:
Platform-reported conversions are a signal, not a result. Every platform reports favourably on itself. Where the same conversion appears in Google Ads, in Meta, and in analytics with three different numbers, the honest position is that all three are estimates.
The client's own system is the source of truth. A CRM record or a completed transaction outranks any platform report. Where a client cannot connect ad platform data to their own record of outcomes, we say so rather than reporting platform numbers as though they were revenue.
Long cycles need proxy metrics, chosen carefully. A real-estate advisory client with a four-month sales cycle cannot optimise to closed deals in-period. They optimise to a validated intermediate signal — a qualified consultation — and the qualification criteria are agreed in writing, because a proxy nobody has defined is just a vanity metric with extra steps.
Incrementality beats attribution where it is testable. Geo holdouts and structured pauses answer the only question that matters — what would have happened without the spend — more reliably than any attribution model. They are underused because they require deliberately not spending money, which is a difficult conversation and the right one.
What this is actually for
The portfolio exists to answer a question enterprises ask before they commit: can this be run properly at our scale, in our markets, under our compliance constraints?
The evidence for that is not a case study with a flattering percentage. It is the operating detail — account architecture, funding infrastructure, budget governance, attribution honesty — because those are what break first when volume increases, and they are what a prospective client should be interrogating.
Our documented case studies cover individual engagements in more depth. The business units page sets out how paid media, funding infrastructure, and advisory combine in a single engagement, and our compliance position covers the regulatory and AML framework the funding layer operates under.
For enterprises evaluating a managed portfolio arrangement, start a conversation.
