Mercury Paid Campaign Agent Setup for Businesses

Mercury is our configured paid-campaign agent service for businesses that want help preparing campaign reports and proposed changes. It can organize authorized account data, build a planning brief and deliver a draft for your staff to approve. Your approved agreement controls the connected accounts and actions. Staff approval remains required for ad spend and publishing.

Team is a useful starting conversation when you want a campaign report, a proposal draft and an approval handoff. Focus may suit one defined reporting question. We match the purchase to the work and access your business approves. Ad spend, creative production, AI usage and ongoing full campaign management are separate charges and agreements.

Discuss Mercury setup

Call (317) 981-2386 with your current account arrangement and the proposed action you want help preparing. The first strategy conversation is free. We aim to respond within five minutes during business hours. If calling is inconvenient, request a callback. We agree the scope and arrange payment by phone before onboarding.

Mercury is a service your business can buy from Trojan. This page doesn't claim that today's website assistant has access to your ad accounts. Jamie can help you frame a question or callback preference. Account authorization, workflow testing and launch decisions happen through the scoped onboarding process after payment is confirmed.

You might already receive a platform report without knowing which action it supports. Mercury can be configured to connect an agreed reporting view with the business question behind it. We ask who reads the output, what they can approve and what extra context they need before choosing a campaign change.

Consider a manager who wants to understand whether a campaign is spending ahead of its approved period. That question needs dates, account currency and completed spend data. It may also need context about an intentional promotion. A request to develop a new offer has different source requirements. We keep those tasks distinct while choosing the workflows.

A useful first workflow has a trigger and a stopping point. For example, a scheduled account report can produce a dated packet for a marketing manager. The packet might identify a change worth discussing, while leaving the account untouched. A second workflow could turn an approved request into a draft campaign brief for the same manager to review.

We need your business to define a satisfactory inquiry. A campaign for a service you can no longer provide can look active in platform statistics while creating extra work for the office. Tell us which services and places are accepted. Those operating facts help Mercury explain what the report might mean for your actual business.

Name the person who can decide.

The receiving staff member should have access to the necessary business data and authority over the proposed action. An office coordinator may understand inquiry quality while lacking permission to increase media spend. We can route the report to that coordinator for context and keep the final budget decision with an approved manager.

Our paid media service covers the wider planning discussion. Google Ads management is a separate option if you want ongoing campaign work beyond the agent's agreed outputs. Mercury's service price doesn't silently include the full responsibility of a campaign-management engagement.

We can work with an existing advertiser or internal marketing team. Ask them which repeated task creates a bottleneck. They may want a cleaner reporting comparison, an offer register or a standard approval packet. Buying a configured agent is worthwhile only if the output fits the team that will use it.

Before choosing a larger plan, test one task against a question the receiving person already understands. Their check can reveal an unclear instruction or a missing fact. We want the workflow to make that choice easier to inspect before adding another account or another department's approval rules.

Mercury uses connected data only through the authorization agreed with your business. We record the business, account and intended task before arranging a connection. The person granting access must be allowed to do so. We also identify who can remove that access if the task or the working relationship changes.

Google's Ads API uses OAuth authorization and requires extra API access requirements, including a developer token. Its official documentation explains access without handling a user's login data. A supported connection still needs the right account permissions and approved setup. We check those requirements before treating a requested account workflow as ready.

For Meta account work, the official business SDK documents access tokens and permissions for the underlying APIs. The existence of that SDK doesn't make every business account or requested action available automatically. We check the specific account and supported method. If the connection needs extra approval or bespoke development, that affects the quote.

Your staff shouldn't paste account passwords into a contact form or a public chat. We agree a supported authorization process during onboarding. Keep the business's provider accounts in its own name where practical. An account list and handoff record help the team understand what it controls and what continued managed support requires.

One connected business account or app means one authorized account for one service. Focus permits up to two connections, Team four and Operations six. Multiple ad accounts can therefore change the plan even when they belong to one company. The AI service and hosting create extra provider costs outside that business-account allowance.

If an account connection fails, the report should show that it couldn't obtain the current input. It shouldn't silently reuse an earlier report and describe it as fresh. We can retain a dated last-successful observation for context, clearly marked. A reviewer can then decide whether to wait, use an approved export or ask for support.

Authorization for a report also needs a sensible data boundary. You may want campaign totals without passing customer-level data to an AI provider. We can discuss a summarized input for that purpose. Where a task genuinely needs private records, the source owner and provider handling must be approved before the workflow starts reading them.

A campaign report should say which account, dates and measurement definitions it uses. Mercury can assemble that context with the selected metrics. We want the receiving person to understand whether a number describes platform activity, a recorded inquiry or a later business outcome. Those stages need different evidence.

Google's query documentation supports resources, metrics and segments in an authorized Ads API query. Selecting a segment changes how the metrics are grouped. A report split by date answers a different comparison from one grouped by campaign or device. We configure the report around the agreed question and make its grouping visible.

Before discussing cost per inquiry, define the inquiry count. Your business may count a completed form, a phone conversation meeting an agreed condition or a qualified request reviewed by staff. Those choices aren't interchangeable. The report needs the definition and source, so a changed counting rule doesn't look like a sudden campaign improvement.

Bring qualification into the report where the data supports it.

A platform conversion can be useful without proving that your team sold a job. If you want Mercury to prepare a lead-quality comparison, supply the approved qualification data and a way to align it with the campaign view. Remove private details unnecessary for that analysis. Your staff should inspect uncertain matches before treating them as campaign evidence.

The lead cost calculator can help you model an acquisition allowance using your own qualification and close assumptions. Its result doesn't establish what Mercury will achieve. We can use a saved scenario as planning context, then keep actual campaign findings separate from those assumed values in the report.

Use a complete reporting day where the comparison needs daily spend. A partial morning export can make an account appear behind a full-day plan. Agree the account timezone and the point through which the data is complete. For a promotion with its own start and end, use that window consistently across the spend and inquiry data.

Attribution and reporting delays can affect a recent comparison. We don't assign a universal delay or treat every current field as final. Mercury can record when its report was prepared and which period remains subject to change. Your reviewer can ask for a later check when the requested action depends on more complete data.

Currency belongs beside the amounts. A multi-account report shouldn't quietly add different currencies into one spend total. We agree how to present accounts individually or handle a separately approved comparison. The same care applies to whether the budget includes only media or also includes production and agency fees.

If measurement is missing or unreliable, the next useful action may be a measurement audit. Our PPC audit service gives that concern a separate scope. We can configure Mercury to flag an unresolved tracking issue, but connecting the reporting workflow doesn't itself repair the website, phone measurement or conversion definition.

Mercury can prepare a campaign planning brief using your approved services, destination pages and operating limits. We ask for the offer's conditions before drafting a proposal. A campaign should point to data your team can support and a receiving route it can handle.

Start with the work you want inquiries for and the work you must exclude. A team accepting planned appointments may have different availability from a team handling urgent requests. Your actual service area also matters. A place listed in an advertising idea doesn't prove your crews or staff can serve it.

The brief can identify the intended customer, the problem they describe and the page that explains the offer. Your reviewer should be able to follow that path without filling in missing facts. We can include an unanswered business question as a required answer before any proposed ad copy is approved.

Campaign structure follows that approved offer. A useful draft might separate services that have different destinations or receiving teams. It could also propose an experiment where the business has a specific question to test. We state the hypothesis and what the report would need to observe, rather than assuming a new structure will improve results.

Include the landing page in the plan.

If an ad promises a price condition, the page needs to explain that condition accurately. If the page sends visitors to a contact form, the receiving staff must know what the customer was offered. Mercury can organize those questions in the brief. Any page edits belong to an approved page work task.

The screenshot provides a concrete destination-page inspection exercise. We can ask a staff member to locate the offer and the inquiry buttons, then check the route intended for a campaign. Its captured storm message and callback wording need current business approval before reuse. The image documents a published design, without establishing advertising results.

The campaign URL builder can help your team keep tracking labels consistent. Agree the naming rules before collecting a comparison. Two different labels for the same offer can make a report harder to interpret. Mercury's configured instructions can retain the approved naming convention for draft links.

Creative production deserves its own agreement. We can organize a request for a designer or video editor, including the offer and required facts. The Mercury plan doesn't automatically supply photography, final artwork or a produced video. Explore video editing and creative services when the campaign needs that work.

Keep the proposed action proportional to the evidence. A short data window may justify a question or a small approved test rather than a broad account change. Your staff chooses the action after examining the brief. We can make uncertainty easy to see and keep the approval record alongside the proposal.

The following figures are hypothetical teaching inputs. They aren't a client result or a spending proposal. Imagine a business has approved a 4,000-dollar media budget for a 30-day promotion. At the end of the eighth complete day, its entered spend is 1,200 dollars in the same account currency.

Mercury could package that comparison with the campaign's approved purpose and a question for the manager. Was an early promotion surge intentional? Has an offer changed? Are the reported inquiries useful to the business? The arithmetic can show a pacing difference while leaving the spending decision with the staff member who knows those conditions.

The campaign budget pacer provides an existing way to run this kind of calendar comparison with your own inputs. It doesn't connect to an ad account or change its budget. A Mercury workflow can use an agreed calculation and reporting definition within its agreed task, with the same separation between a number and an approved account action.

Suppose the manager asks for a proposed adjustment. The next draft should identify the specific campaign and the budget field involved. It should show the current value, proposed value and expected approval window. A staff member must confirm what that field means in the specific platform and campaign arrangement before applying the change.

The new proposal should also explain what happens if the campaign changes before approval. A stale comparison shouldn't remain an open invitation to act later. We can configure the workflow to ask for refreshed input and another staff approval when the relevant conditions have changed. The exact rule is part of your setup.

This example helps us test whether the receiving person can use the packet. We can check the arithmetic and the source dates. We can also check whether the draft leaves uncertainty visible. None of those checks establishes that a different daily setting will produce a lower lead cost or more booked work.

An approval workflow needs more detail than a button labelled yes. Mercury's proposed change should identify the account, campaign and affected setting. We agree who may approve it and what that approval covers. If the draft is revised materially, the person needs to review the revised proposal before it is applied.

The packet can show the existing value beside the proposed one and a reason tied to the source report. For copy, include the destination and approved offer conditions. For spend, include the account currency and the relevant period. Your staff should be able to recognize the request without opening unrelated reports to reconstruct it.

Read-only reporting is a useful place to start. If you want scoped account actions, we check the supported connection and the staff approval step separately. We don't give Mercury a blanket instruction to increase ad spend because a metric moved. A plan's workflow allowance doesn't itself authorize any specific account action.

Google documents that some API requests can use partial failure, where successful operations may commit while others return errors. That means a request needs its results inspected. A system should avoid treating a mixed outcome as either complete success or a harmless failure that can be repeated in full. Our proposed action workflow includes an appropriate result check.

For supported scoped actions, we discuss how to recognize retries and avoid repeating an already completed change. That is a setup requirement to test, rather than a claim that today's public chat provides it. If the outcome is uncertain, route the condition to the agreed staff member and confirm the actual account state before another attempt.

Approval also needs an understandable end. A manager should be able to reject a draft, ask for a change or let it expire. Your staff remains responsible for policy, offer accuracy and budget authority. We configure the output and routing around that responsibility, with a clear record of the proposal the person actually reviewed.

Our DIY business agent guide is useful if you're deciding which permissions a first workflow should have. Think about what an error could affect before selecting a tool. Draft generation and account execution deserve different access decisions even when they begin with the same campaign question.

A Mercury readout can describe the reporting scope before presenting findings. We configure it to carry a preparation time and the date through which data was included. The report should label missing inputs and show which conclusions depend on them. Your manager can then challenge the reasoning instead of guessing what the agent meant.

A practical opening might identify the campaign being assessed, the approved offer and one question for the meeting. The supporting section can show the selected metrics and their comparison. End with the proposed action, any unresolved business facts and the staff member who needs to answer them.

When a campaign appears to attract unsuitable inquiries, the report should examine the data your team supplied. A salesperson's short note about a mismatch may be useful, but it isn't a complete survey of every customer. We can preserve the source and its limits rather than presenting a few notes as a measured account-wide rate.

Some differences will remain unexplained. A competitor's activity, seasonality or a changed platform auction may be relevant, but Nova or Mercury shouldn't assert a cause it hasn't established. We can ask the report to separate findings from possible explanations. The receiving team can decide whether another source or a controlled test would help.

An approved change deserves a later observation with the same care. Record what was applied and when, then choose an appropriate period for assessment. If the business also changed staffing or the landing page, include that context. The agent's report should avoid assigning all later inquiries to one campaign setting.

We can include an escalation for conflicting numbers. If the account export and a team spreadsheet cover different days, the report can show that mismatch and stop the comparison. If an inquiry source hasn't been approved, it can ask for the receiving owner's answer. Clear limits make the packet easier to use than a polished conclusion built on incompatible inputs.

Our existing budget pacer and tracking-link builder can support a manual reporting process too. Those tools remain useful whether you buy Mercury or keep the preparation with staff. The purchasing question is who will own the recurring setup, checks and correction work.

A home-service team may want an advertising discussion after a relevant weather notice. The notice can be an input to a planning workflow, subject to the business's approved sources and territory. It doesn't establish demand, property damage or authorization to spend. The receiving team first checks what work it can actually accept.

Hailey is the separate weather-related setup offering in our agent service lineup. If your business wants Hailey to notify staff and Mercury to prepare a campaign proposal, we scope that handoff explicitly. Each workflow needs a defined trigger and output. Naming two agents doesn't mean either may start an advertising campaign independently.

A useful event-to-campaign brief includes the source and check time, the relevant approved area and the service under discussion. Staff should confirm coverage and current capacity before approving an offer. If the business can't take extra requests, the right choice may be to hold the proposal and focus on existing customers.

For the advertisement itself, use verified service claims and suitable approved assets. A weather event doesn't justify implying a diagnosis for a person's property. Avoid suggesting that every address in an area has damage. We can encode those restrictions in the brief and require a reviewer who understands the contractor's actual service.

Local ad targeting requires its own account and method check. A territory list in the business facts isn't proof that a platform will show an ad only to every desired household. Your advertiser checks the available settings and their limits. Mercury can prepare a proposal for that review while leaving the final targeting and publishing decision with authorized staff.

The weather-response agent DIY guide explains how to think about approved notices and human handoffs. It can help you prepare a planning call. For search data around the same services, Nova supports a separate analysis and content-brief process with its own sources.

We want the combined plan to reflect actual tasks. Team allows up to two configured agent roles and three workflows. A notice, a response draft and a campaign brief may use that allowance, depending on the agreed definitions. Additional accounts, more workflows or a broader operating arrangement need a revised quote.

Mercury can prepare draft campaign text from approved offer data. We give it the actual service, conditions and destination. A reviewer should see which input supports each important claim. If the source doesn't confirm a price, credential or availability, the draft should leave that detail for the business to answer.

Campaign copy needs the same factual discipline as the landing page. A headline can be short while still implying a promise your team hasn't approved. We ask your campaign approver to compare the headline with its landing page and every offer condition. That is especially useful where a promotion has an end date or only applies to certain customers.

Jeff Clerisier's Google Ads Search, Google Ads Measurement and AI-Powered Performance Ads certifications are personal credentials. You can inspect the linked certificates through our Google Ads management page. They don't confer a vendor partnership on a new agent setup or replace a platform's assessment of a proposed advertisement.

The campaign's visuals also need approval. Use photographs your business has permission to publish and describe them accurately. A project image should retain the correct business and context. We don't fabricate campaign screenshots or imply a result through a stock dashboard. Mercury's setup can route an asset request to the responsible creative team.

The existing editorial photograph used for this service shows a magnifying glass on papers at a dark desk. It illustrates campaign analysis, without pretending to show Mercury running an account. The visual is already used in Trojan's approved search-related content. A client-specific advertisement would require its own approved assets and production agreement.

If your team has an existing designer, ask what data they need in a creative brief. We can include the intended audience, offer, destination and required conditions in the agreed output. Final design and production remain separate services. A brief helps the team work from the same approved facts while preserving their judgment.

Policy compliance remains an explicit responsibility. Your staff and advertiser need to confirm whether the offer and text comply with the relevant platform rules and applicable requirements. We can flag a concern and preserve source context. We don't promise that a drafted ad will be accepted or that approval guarantees campaign performance.

The monthly Mercury service fee buys a bounded amount of Trojan care. It covers an operating check and small corrections or changes to existing workflows within the allowance. It doesn't purchase advertising inventory. Your platform media spend and any separately approved campaign-management work remain outside the listed agent service price.

We prefer client-owned provider accounts with direct billing where suitable. If we pay an approved provider for your business, its documented charges pass through at cost. AI or API usage, automation subscriptions and hosting can all create extra costs. We identify the selected provider and allowance during the planning call.

At setup, we configure supported usage controls and an alert at 80 percent of the approved provider budget. Optional outbound work can pause or go to the assigned staff contact at the ceiling. Provider billing may arrive late, so a safety buffer is needed. We won't describe every integration as having an exact universal hard spending stop.

That provider control is separate from your ad account budget. Staff approves campaign spend and publishing according to the written workflow. If a reporting provider allowance is exhausted, Mercury's next report may pause. It doesn't mean an existing ad account has stopped serving, so the receiving team needs a clear escalation for that condition.

Plan runs measure processed events or requested tasks, including retries. An unsuccessful operation can still incur a provider charge. Polling without a matching event doesn't count as a run, while staying within the approved API budget. We explain those definitions so an allowance of 3,000 runs isn't mistaken for prepaid media, AI tokens or unrestricted account changes.

Focus includes one monthly support hour, Team two and Operations three. Additional support is approved at 150 dollars per hour or quoted separately. Unused time ends with the month. A new workflow, an account migration or bespoke API work requires another pricing agreement before we accept it as included care.

Initial sources are limited to 25 pages or text-ready files for Focus, 75 for Team and 150 for Operations. A file can be up to 5 MB. We inspect messy exports and large collections before quoting the work they require. Setup includes sample tests, instructions and one training session for up to three, five or ten team members, according to the plan.

The agreement should define monthly renewal and cancellation alongside the launch conditions. Recommended terms begin monthly care when approved workflows go live. At handoff, document the business's accounts and setup, plus any hosting dependency. Continued managed scheduling and maintenance end when that support service ends.

Will Mercury raise my ad budget by itself?

The service described here requires staff approval for ad spend and publishing. A report can recommend a discussion or prepare a draft change. Any supported account action must have an agreed permission and approval step. A favorable metric doesn't grant the agent blanket budget authority.

Are ads or media spend included in the monthly price?

Your advertising platform charges remain separate. Mercury's monthly fee pays for the listed Trojan support allowance and operating check. Creative production and full campaign management are also separately scoped. Bring your media budget to the call so we can distinguish it from the service and provider costs.

Can we buy Mercury for reporting only?

A defined reporting question can be an appropriate first workflow. We discuss the account data, comparison and recipient before choosing the plan. You can keep the first setup focused on readable outputs and leave live account changes with your current staff. The source and access requirements still need approval.

Does the service require a Google Ads account?

The setup depends on the campaign platforms your business actually uses. A Google Ads task needs authorized access to that account and the supported connection requirements. Other platforms need their own assessment. We confirm whether the proposed method works before promising that a specific account is included.

What does Team include for a campaign workflow?

Team permits up to two configured agents, three agreed workflows and four connected business accounts. It includes up to 3,000 monthly runs and two hours of monthly support. We define the reporting, proposal and approval tasks with you. Those allowances don't automatically include every campaign idea or platform action.

Can Mercury prepare negative keyword or copy suggestions?

We can discuss those draft outputs using authorized account data and your approved services. Your advertiser reviews the context before applying a suggestion. The workflow should preserve the affected campaign and the reason. Implementation permissions and approval are agreed separately from the ability to generate a draft.

What if account data stops arriving?

The configured report should identify the failed or incomplete input and its check time. It can route that condition to your approved receiving person. A prior report can remain available as dated context. We don't want old numbers presented as a fresh basis for changing an account.

Can I use Mercury with Hailey?

We can scope an approved handoff between weather-related notices and a campaign planning brief. Your team checks territory and service capacity, then approves any spending or publishing. Discuss the exact workflow count and account connections. A weather notice alone doesn't authorize outreach or advertising.

Will the setup produce cheaper leads?

We haven't supplied a guaranteed acquisition cost or customer result. Mercury helps prepare the agreed analysis and approval process. Actual campaign outcomes depend on the offer, account conditions, measurement and business handling. We can examine findings without turning them into a promised saving for another business.

How do we stop using it later?

Agree the account ownership, hosting and handoff before purchase. Your staff should know how to revoke access and stop scheduled work. The final support terms define renewal and cancellation. Continued managed scheduling or maintenance ends with the support service, while the documented account arrangement guides what your team retains.

Do we need to share our customer database?

A reporting or planning task may work with account summaries and approved service facts. We use only the inputs required by the scoped workflow. If customer-level data is needed for another task, the owner approves the handling and provider destination first. Private details belong outside the initial public chat request.

Can I build a campaign helper myself?

Use the DIY business agent guide to consider sources and permissions. Start with a draft or read-only task you can judge. You still need to maintain access and inspect mistakes. Buying Mercury gives Trojan a defined setup and care role around the responsibilities you approve.

Does an API error mean no changes happened?

It can require a closer result check. Google documents partial-failure behavior for supported requests, where some operations can succeed while others return errors. A scoped action workflow needs to inspect outcomes before retrying. If account state is uncertain, route it to staff and verify what happened.

How do I pay and begin onboarding?

Choose the plan you want to discuss and call (317) 981-2386. We check the workflow, connections and operating allowance with you. After the scope is approved, payment is arranged through Trojan's existing phone process. Onboarding begins after payment confirmation; this page doesn't create a new checkout or accept a contract.

Start with one current campaign question. Tell us who receives the report and who can authorize a change. We can discuss a suitable plan and the data it needs. You don't have to connect an account during the first conversation or arrive with a finished automation specification.

Mercury is most useful when a team wants a clearer recurring preparation and approval process. If your immediate need is a full campaign-management engagement, use our Google Ads service or the broader paid media offer. We can discuss the distinction before you pay for the wrong scope.

For the other setup roles, visit the agent service hub. Nova handles search analysis and content priorities, while the contractor weather-response guide explains a different operating trigger. Choose the business task first, then decide which approved workflow supports it.

Call about Mercury

A callback request through our contact form can include your preferred plan and a short description of the campaign question. Keep credentials out of that message. We confirm scope, permission and provider budgets with you, then arrange payment before onboarding starts.