Standard Google Ads management
This is what most agencies sell, and it is written here fairly because a lot of it is fine.
A standard engagement builds campaigns by match type and theme. It writes responsive search ads, adds sitelinks and callouts, sets a daily budget and a target CPA or ROAS. It installs the Google Ads tag, or GTM, and counts form submissions and phone calls as conversions. It adds negative keywords from the search terms report. It sends a monthly report from the interface or a Looker Studio template. Someone looks at the account a couple of times a week.
Run well, that produces a working account. Plenty of businesses have grown on it.
Where it stops
The target is sometimes a number someone chose from a feeling or a trailing account average rather than from unit economics. Google treats target CPA as an average, not a per-conversion ceiling. An expensive auction can change volume, spend and efficiency, but cheaper clicks are not automatically worse and a price movement alone does not explain lead quality. Where budget genuinely is the limiter, the case for testing a target-free strategy is worth reading before the target is changed.
When Maximise conversions or target CPA uses several actions in one goal, it optimises conversion count rather than their configured monetary values. A completed job and a duration-only wrong number can therefore be presented as equivalent selected conversions unless the goal or imported outcome distinguishes them.
Tracking often stops at the website. Calls made directly from responsive search ad call assets can have no site visit and no CRM quality layer unless a supported call-tracking and feedback route is built.
In a standard setup, CRM outcomes may not go back. Unless those outcomes are supplied through an eligible conversion import, Google cannot use them as the bidding goal.
The weekly check is a person scrolling the interface. Anomalies are found when the client rings. It is also usually a Smart Bidding account by default, so manual CPC only earns its place in a narrow, knowable case, not as a routine substitute for the checking above.
The boundary
Fire Pixel is not a standard account-maintenance service, and it is not a bidding-agent product layered on top of Google's either; see where AI agents actually earn their keep in a Google Ads account for that distinction.
If a conventional setup is all the account needs, I will say so. The diagnostic can document the gaps and leave the implementation with your existing team.
The diagnostic is the decomposition step: your goal broken into the conversions, values and pipes the account needs, written down, with a build order.
Ongoing management is split by the evidence the business actually has. Lead generation management uses calls, forms, CRM outcomes and later sales stages. Ecommerce management uses Merchant Center, transactions, order lines, customer status and product margin.
Standard account work still happens inside either engagement. It is not the whole product.
Standard vs Fire Pixel
| Standard | Fire Pixel | |
|---|---|---|
| Target source | A feeling or a trailing account average | Close rate, completion rate and contribution, derived in the Qualified Lead Loop's Value step |
| Conversion definition | Several actions counted equally in one goal, so a completed job and a duration-only call can look the same | Primary bidding goals separated from reporting-only actions, with values maintained |
| Calls | No site visit and no CRM quality layer for calls made directly from ads | Calls from ads mapped and captured in the Capture step, with a documented route or gap |
| CRM feedback | Outcomes may not go back, so Google cannot use them as the bidding goal | Eligible outcomes sent back to Google in the Return step, without counting the same outcome twice |
| Review cadence | A person scrolling the interface; anomalies surface when the client rings | The weekly loop: a warehouse and an automation flag what moved, then a person reviews it and decides |
| What you receive | A monthly report from the interface or a Looker Studio template | A short note every week, a dashboard on the warehouse, and a log of every change and why |
If you are not sure which side of this table your account is on, the account and measurement diagnostic will document the gap honestly, without assuming you need ongoing management to close it.
FAQ
What does standard Google Ads management usually include?
Campaigns built by match type and theme, responsive search ads with sitelinks and callouts, a daily budget and a target CPA or ROAS, the Google Ads tag or GTM counting form submissions and phone calls as conversions, negative keywords added from the search terms report, and a monthly report from the interface or a Looker Studio template. Someone looks at the account a couple of times a week. Run well, that produces a working account, and plenty of businesses have grown on it.
When does standard management stop working?
It stops working once the target no longer reflects unit economics, once several conversion actions are counted as equal when their value is not, once calls made directly from ads have no site visit and no CRM quality layer, once CRM outcomes are not supplied back to Google as an eligible conversion import, and once the weekly check is a person scrolling the interface rather than a system that flags what moved.
What changes with Fire Pixel?
Targets are derived from close rate, completion rate and contribution rather than a feeling or a trailing average. Conversion actions are separated into primary bidding goals and reporting-only actions, with values maintained. Calls from ads are mapped and captured with a documented route. Eligible CRM outcomes are sent back to Google without double counting. A warehouse and an automation flag what moved every week, and a person reviews it and decides.