Written answers to the questions buyers actually type. Each one opens with a summary that stands on its own, and is dated so you know how current it is.
Automate the numbers. Never automate the paragraph that explains them.
Client reporting consumes senior time at the least profitable moment of the month, and the output is usually a dashboard screenshot with a paragraph of commentary. The data, layout and delivery can be fully automated. The interpretation should not be — a report with no human commentary is a data dump, and clients stop opening it. The right split frees the time that makes the commentary good.
A tag that fires in your test does not mean a tag that fires for your customers.
Most GA4 tracking failures are conditional rather than total: the mobile variant of a form, the returning visitor, the booking flow that only redirects for one service type. They survive launch QA because QA tests the happy path once, on desktop, as a new visitor. Catching them requires walking each conversion path end to end in a real session, then repeating the check after a week of live traffic.
Most of the difference between full recovery and partial recovery is decided before you finish reading this.
In the first four hours of a Google Ads account compromise: revoke unrecognised access, freeze the payment method, pause campaigns you did not create, and enforce two-factor on every Google account with admin rights. Then stop. Do not delete campaigns, users or history — deletion destroys the evidence a spend recovery claim depends on, and it is the most common self-inflicted wound in these incidents.
Creative decides how well you perform inside the limits. Structure decides where the limits are.
Google Ads account structure is how campaigns, ad groups, budgets and conversion actions map onto the business — locations, service lines, margin tiers. Structure decides what budget can respond to, which puts a hard ceiling on return on ad spend. Optimising creative under a bad structure produces small, repeating gains; correcting the structure produces a step change and then stops, which is the shape you want.
It is an evidence exercise with renewal dates, not a one-time form.
LegitScript is the third-party certification Google requires before advertisers in certain healthcare, pharmacy, addiction treatment and telemedicine categories can run ads. Without it, ads in those categories are disapproved. Certification is an evidence exercise rather than a form, it carries renewal dates that get missed, and certified advertisers still get flagged occasionally by policy matching errors.
The honest answer is that most mid-market marketers do not need one yet. Here is how to tell whether you do.
A dashboard is sufficient when reporting reads from one platform and history beyond that platform's retention does not matter. A marketing data warehouse earns its cost under four conditions: cross-platform questions, retention beyond platform limits, per-location rollups, and numbers that must be reproducible and auditable. For most mid-market marketing datasets, running costs are tens of dollars a month; connector licensing is usually the larger line.
The conversions are real. The ability to credit them to a location is what is missing.
In multi-location businesses, conversion events frequently fire without a location parameter. The conversions are real and correctly counted in aggregate, but per-location performance becomes unmeasurable — which means budget decisions across sites get made on aggregate data and instinct. This is an attribution gap, it is fixable at the event layer, and it should be closed before any optimisation work begins.
They answer different questions. Most estimation arguments are really about which question is being asked.
Story points measure relative size and become a schedule only when multiplied by measured velocity. Hour bands communicate cost and commitment to a client. Agencies need both: points for internal sequencing, bands with written assumptions for the commercial conversation. Most estimation disputes are two people answering different questions with the same number.
The conversion work is the easy part. Nobody believes that until the deadline arrives.
A mid-size Tableau Server to Tableau Cloud migration — on the order of 150 data sources and 100-plus workbooks — takes three to six months end to end. The variable is rarely conversion effort; it is inventory, stakeholder validation and access provisioning. Programs that skip the inventory phase estimate against a number nobody has verified, and the variance is routinely a factor of two.
It is an administrative layer, not an advertising account. Confusing the two is where the operational failures start.
A Google Ads manager account — Google's term is My Client Center, or MCC — is a container that administers multiple Google Ads accounts under one login, with consolidated billing, cross-account reporting and shared assets. No campaigns run in it directly. It becomes worth the setup at roughly five accounts, and becomes essential wherever separate locations carry separate budgets or separate accountability.
Some of the gap is by design. The rest is a defect, and the two need separating before anyone makes a budget decision.
Google Ads and GA4 report different conversion counts because they use different attribution models, different attribution dates, and different session definitions. A stable gap of roughly five to fifteen percent is normal. A large, unstable, or directionally odd gap usually indicates duplicate event firing, broken cross-domain measurement, or an unverified conversion action.
The margin on a fixed-fee project is decided before anyone writes code.
A fixed-fee statement of work protects margin through four mechanisms: an estimate built from decomposed work rather than a buffered guess, a written assumptions list, an explicit exclusions list, and acceptance criteria that make "done" testable. Projects that lose money almost always failed at one of those four in the document, not during delivery.
The role is widely advertised and inconsistently defined. Here is the version that describes a job rather than a title.
A fractional technical project manager owns delivery for an organization part-time — typically two to four days a week — covering estimation, sequencing, scope and change control, QA, and client-facing communication for technical work. The role differs from a full-time PM in availability and cost structure, and from a consultant in that a fractional PM has operational responsibility for shipping, not just recommendations.