Google Ads call-asset audits for agencies: review number ownership, campaign scope and conversion evidence

Define the client's call objective

A call-asset review should start with the team the client wants the visitor to reach. An agency may manage a central booking line, several branches or a specialist service with its own staff. These arrangements require different account decisions. A presence check can show an applied call type, but it cannot tell whether the number reaches the right people or whether that team is ready to handle the enquiry.

Write the objective in business language. For example, make sure the evening-course campaign points enquiries toward the enrolment team rather than the general reception line. This gives the specialist a useful target and prevents the review from becoming an exercise in adding a number solely because the audit says one is missing.

Confirm whether the client wants direct calls from the ad, website enquiries, or both. A call conversion category in the account is relevant context, but it does not dictate every campaign's contact strategy. The client may deliberately use a central number for several services or keep a particular campaign focused on a registration page.

The agency's conclusion should name the intended destination, observed configuration and selected next action. It can be a supported attachment, new asset, detachment, business clarification or measurement review. A verified provider setting is useful, but it should not be presented as proof that staff answered calls or that every caller became a customer.

Agree on the immediate decision separately from the long-term reporting project. The client may need the correct campaign contact today while the team later reviews call conversion definitions. Keeping those tasks separate allows a focused supported change without pretending that the entire measurement system has been audited or repaired as part of one number attachment.

Separate number content and relationship scope

A call asset stores the number and related provider fields. Its association applies that asset to an account, campaign or other supported level. These are separate objects of review. An account can contain a number that is not attached to the requested campaign, and one asset can have relationships beyond the single campaign discussed in Slack.

Google's call-asset guidance explains the phone-number feature and states that more-specific call-asset levels take precedence. It also notes that configured assets do not appear with every impression. Use those provider distinctions when assessing the actual account branch rather than copying sitelink hierarchy assumptions into call routing.

Separate the stored business number from a displayed forwarding number or an operational phone system. A compact asset read does not inspect every downstream routing rule. The agency can establish the configured content while asking the business owner to confirm where calls actually land and how they are handled.

Do not describe a call asset as a completed tracking setup merely because its phone field is present. Conversion action definitions, recording choices and reporting availability are separate matters. The client's review should keep contact configuration, operational handling and measurement clear.

Read the account call check

ppctor's account call-extension card is shown when the inspected conversion setup includes an action categorised as a phone-call lead. It then checks whether the returned extension data contains a call type at account level or in the selected campaign coverage collection.

This trigger is based on the category in the setup collection. It is not itself a request for recent primary call counts, a proof that a particular campaign bids toward calls, or confirmation that the number belongs to the correct branch. These questions need their own relevant evidence.

A present result means that the declared type was found within this check's scope. The card does not require a suitable call asset in every campaign. One selected campaign relationship can satisfy the presence condition even while another campaign still needs a deliberate number review.

A missing result should prompt investigation rather than an invented number. The account may use website calls, another supported contact arrangement or a deliberately different campaign objective. The agency should confirm the business brief before proposing the supported asset operation.

Document a deliberate exception in the agency brief. A business might track calls for one service while another campaign intentionally sends visitors to online registration. The broad category-triggered account check can still be useful, but its observation should not erase that distinction or become an instruction to add direct calling to every offer.

Preserve the selected coverage boundary

The extension reader obtains enabled account and campaign relationships. Its core campaign coverage population consists of enabled campaigns with impressions in the selected period, excluding its declared Local Services and Smart channels. The account call card uses that selected coverage data alongside the account type list.

A future campaign without activity in that window can be outside this account card's campaign coverage population. Its absence should not be interpreted as complete proof that no campaign-level call asset exists. A focused current configuration question needs the appropriate relevant relationship evidence.

Account relationships are read even for a dormant account. That is useful because applied account assets can exist independently of currently enabled campaigns. Do not assume the audit skipped number configuration simply because the account has no currently serving campaign.

The compact account check does not inspect every lower-level call association, location number or phone-system route. A full routing question must state the intended scope and obtain its relevant sources. The presence card is a bounded observation, not a certificate for every possible contact path.

Read the campaign routing observation

The separate campaign detail reader collects enabled campaign associations, enabled account associations and the relevant asset content. It builds per-campaign call association counts and a set of distinct returned account phone strings. The campaign card uses those observations to distinguish own call assets from inherited numbers.

When there is no own call association and more than one distinct account number is returned, the current campaign card marks the inherited choice for review. This is a routing concern to investigate. It does not establish that the provider actually sent a recorded call to the wrong office.

A campaign with its own call association gets a positive own-asset result in that card. The predicate does not require exactly one own number or prove operational suitability. The agency should not turn the compact label into a claim that every number in the campaign has been tested.

The card is hidden when neither own call associations nor returned account numbers are present. A hidden card is therefore not a verified pass about all call configuration. Use the actual presence and coverage observations when explaining what the review established.

Distinguish numbers, assets and associations

One phone number can appear in several assets or relationships. A count of assets is not necessarily a count of unique phone numbers, and a count of campaign applications is another unit. State which one the client requested before interpreting the returned totals.

The campaign detail's account-number set deduplicates the returned phone strings. Different formatting can remain different strings even when a business considers them the same dialable number. The agency should resolve the actual content rather than assume that the compact distinct-string count performed a complete telephone identity normalisation.

The per-campaign call count reflects the selected enabled relationships. It can be useful for configuration review without telling how many calls occurred. Do not label an association count as enquiries or conversions merely because the asset type is call.

For a short conversational list, distinguish examples from a complete total. Showing two numbers in a reply does not establish that every requested account branch was inspected. A broader count should preserve source coverage, collection completeness and the actual counting unit.

When the client asks which campaigns share a number, define the join around actual asset relationships and inspected phone content. Do not match a campaign name to a number by position in two unrelated lists. Exact internal identity protects the comparison, while the visible answer can remain a simple list of campaign names and readable numbers.

Handle unread number evidence accurately

The account call check depends on extension and conversion-action evidence. The audit maps failures in those required sections to an unavailable result rather than treating a fallback empty set as established absence. Preserve that distinction when explaining the account's configuration.

The campaign detail reader needs relationship and asset content evidence to identify numbers. An unread phone field is not a verified empty business number. If the requested decision depends on actual number content, resolve that missing observation before approving a change.

A successful relationship read can establish a call association without proving that its content was inspected. Conversely, a stored number can be read without establishing its selected enabled association. The agency's next query should target the missing side rather than repeat unrelated account collections.

Keep unknown operational facts separate from provider settings. Even complete asset reads do not prove that the team answers the line or that its internal forwarding works. Ask the responsible business owner for that evidence when it affects the client's decision.

Use the correct call-asset hierarchy

Call assets and sitelinks should not share one casual inheritance explanation. The provider's call-specific guidance describes more-specific-level precedence. A campaign attachment can therefore change the relevant eligible call pool differently from adding a campaign sitelink alongside inherited navigation links.

That distinction does not make a campaign association a complete exclusive-routing certificate. Relevant group-level configuration can be more specific, and other contact surfaces can need their own review. The current compact campaign detail does not enumerate every such relationship.

If the client asks which number can appear for one group, inspect the requested branch and supported relationship sources. An account-level set alone cannot answer that exact question. The assistant should retain the intended campaign and group context while collecting only the evidence needed.

Removing a direct campaign association can expose a different inherited configuration. A detachment proposal should explain the selected removal, then establish the remaining relevant branch where that is part of the request. Do not promise the absence of every call option after one relationship is removed.

An agency reviewing several campaign types should avoid one generic inheritance sentence for all assets. The local framework can retain resource relationships, but the specialist still needs the correct provider rule for the selected type. The call-specific branch question should be answered with call evidence, rather than inferred from a successful sitelink review in the same account.

Confirm number ownership and destination

The business should confirm the number it wants advertised and the team it reaches. Account billing country, campaign targeting and a number's country code are different subjects. Do not choose a phone number or its country merely by copying an unrelated account setting.

If the agency has several client branches, identify which one the campaign promotes. A familiar central number may be intentional, or a branch-specific number may be needed. The assistant should not infer this operational choice from the campaign name alone when the business brief is ambiguous.

Use the client-approved number from relevant supplied context or a verified selected asset. Do not generate an illustrative telephone number in a live proposal. Invented examples in an article are useful for explanation, while production content requires an actual business destination.

Record who can authorise changes to that contact route. The connected owner approves the displayed provider operation, while the business owner may need to confirm the number's operational facts. Preparation should establish those facts before presenting a complete live request.

If the client supplies a replacement number, ask whether it is temporary or a lasting routing decision when that affects the handoff. A short-term enrolment line can need a later business review. The account specialist should not schedule an unsupported automatic restoration or infer a future expiry simply because the campaign promotes a seasonal offer.

Review the team's operational readiness

A number can be configured correctly while the intended staff are unavailable. The agency should ask about the team's handling arrangements when these affect the campaign brief. This is operational review, not a claim that the app called the line or inspected the business phone system.

Separate campaign scheduling, call-asset scheduling and staffing. The dedicated convenience creation path supplies the number and country code, not a full hours-management workflow. A request for additional settings needs confirmation of the actual supported action and its constraints.

Ask which enquiries the team is prepared to handle. A course information line can differ from technical support or existing-customer service. The chosen route should match the campaign's promise rather than merely satisfy a type-presence audit.

A handoff can record a deliberate holding state until operational readiness is confirmed. If an owner requests a supported campaign or asset status change, show that exact scope. Do not silently disable unrelated campaigns because a single team's number needs review.

The team can also define the evidence it expects from an operational check: confirmation that the intended department receives the line and knows the advertised offer. This is a business task outside the provider configuration read. The agency should record the responsible owner and actual confirmation rather than report an assumed successful test.

Separate local format checks and provider rules

The current campaign call-asset helper validates an uppercase two-letter country code and a phone string matching its declared local pattern. That pattern permits certain formatting characters. Passing this preparation check does not prove that the provider will accept the number or approve it for the business.

Google's current call-asset guidance includes provider number-format and verification requirements. Use the actual approved business number in a suitable normalised form, and inspect provider feedback if the request is refused. Do not treat the helper's looser local pattern as a promise that every punctuation style is eligible.

The tool rejects fields that do not apply to the chosen convenience type. A request to create a call asset should therefore not include unrelated sitelink descriptions or URLs simply because the same extension action supports several types. The parameters belong to the selected operation.

Keep human business declarations and provider approval separate from syntactic checks. A well-formed number can still need verification, and a verified content write does not establish that every required commercial or provider condition is satisfied. The agency should explain the actual accepted and unresolved milestones.

Define the call conversion question

A configured number, a click on a call option, a connected call and a reported conversion are different observations. Choose the metric that matches the user's question. Do not report asset presence as a number of enquiries, or assume that every interaction is a primary conversion.

The account setup category can help locate call-related actions, but a category name is not a complete definition of lead quality. The agency should inspect the relevant action names and settings when the client asks what is counted. All lead categories remain leads for the broad reporting concept; special labels do not prove a customer's commercial stage.

A request for a specific call action should use its actual identity and the requested period. Several actions can represent different touchpoints in one journey. Adding them may be appropriate for a declared conversion total, but it should not be relabelled as deduplicated unique callers.

Do not invent a universal GA4 counterpart for calls. An individual comparison needs a selected corresponding event with compatible scope. The assistant can inspect available event names and suggest a probable candidate, but the event choice must be established rather than assumed from a generic category.

A website event with a phone-related name might record a button interaction rather than a connected conversation. The agency should ask the owner what that event represents before treating it as the same outcome as an Ads call action. The name can help locate a candidate; it cannot certify the underlying event implementation.

Preserve primary calls and their value

The app's primary-conversion reporting should retain legitimate primary call actions in the selected aggregate. Secondary actions remain outside a primary-only definition. The call-asset audit does not change those roles merely because it finds a routing concern.

Primary calls can carry assigned conversion value. A broad primary conversion-value metric can include that value alongside other primary actions. It should not be labelled purchase-only revenue when its actual scope includes calls or other non-purchase categories.

Offline actions can also be relevant to the client's journey and visible through supported reporting. A later imported sale and an earlier call can both be legitimate primary records. The tool should honour the chosen reporting definition without claiming that their sum counts unique people or performs business deduplication.

If the client wants purchase-only results, use that narrower selection deliberately. If the request concerns all primary conversions, preserve the broader definition. The agency should state the chosen metric plainly and avoid silently changing it to make a call campaign appear more or less successful.

Assigned call value should remain labelled according to the selected measurement. It can support the client's optimisation definition without representing cash received from that exact conversation. A financial question may need another source or a narrower business outcome. The tool should retain legitimate primary values while the explanation preserves what those values mean.

Choose reuse or supported new creation

A suitable existing call asset can be attached to the requested campaign through the convenience association action. The helper validates account ownership and asset type and obtains readable content or a name for review. The client should see which known number is being associated with the campaign.

The current enabled direct relationship is checked before attachment. If it is already present, the helper avoids creating the same association again. This is relationship deduplication, not a claim that every asset containing the same phone number was found or merged.

New call-asset creation takes the supplied country code and number and attaches the new asset to the campaign. It retains existing campaign extensions. The proposal should expose both creation and application rather than describing the result as a silent replacement of all previous contact configuration.

The dedicated convenience path does not provide a universal number-content editor or every optional call setting. More specific requests need their actual supported actions and current validation. Do not advertise arbitrary account, group, reporting or scheduling changes as automatic side effects of adding a campaign call asset.

Review detachment without promising deletion

Campaign detachment removes the selected enabled direct relationship while retaining the underlying asset. Other associations remain separate. A client asking to remove the number from one campaign should see this exact relationship action, not a promise that the number is deleted everywhere.

If the direct relationship is absent, there is nothing at that selected level to detach. The number may still be relevant through another branch configuration. A no-op at campaign level does not establish the absence of every call route.

The helper verifies the expected remaining enabled campaign asset set. This protects the scope of the requested direct change. It does not inspect the downstream phone system or automatically revise another campaign using the same asset.

A broader removal request needs its actual relationship inventory and supported operations. Keep each intended effect in the proposal, including any inherited state the owner asked to change. Do not broaden a local request without stating and obtaining approval for the wider scope.

Follow an invented agency number review

This example is invented. Rowan Coast Media manages Alder Vale Classes. The Local Evening Courses campaign has no own call relationship, while the returned account set contains two different phone strings. The campaign card flags the inherited choice for review; it does not prove that an actual caller reached the wrong team.

The agency asks the client which route the campaign should use. Alder Vale confirms a specific enrolment line and its responsible team. The specialist also checks whether the request concerns the campaign branch or a particular group. No live number is invented from the fictional business name.

The owner supplies the actual approved number in the production conversation. The agency prepares a supported new campaign call asset using that number and the appropriate country code. The confirmation shows the complete content and the attachment effect, while noting that existing extensions are retained.

After the connected owner confirms, the helper creates the asset, associates it with the campaign and checks the declared leaves and relationship. The technical receipt establishes the stored configuration. It does not claim that staff answered the line, that every impression showed a call option or that new primary conversions occurred.

The agency records the remaining scope question for any more-specific group associations and assigns operational number confirmation to the business. A later performance request uses the chosen call action and completed period. This keeps hierarchy, operations and measurement separate while preserving one coherent client objective.

If the client later changes its routing arrangement, the team uses a new current proposal. The original approval does not authorise every future number change. The handoff contains the established destination, actual relationship and verified outcome so another operator can continue without guessing.

Present exact owner-approved effects

Show the campaign, selected number content and exact association action in clear rows. For creation, show the number and country code, followed by the campaign attachment. For an existing asset, use its readable content while the tool retains validated identity internally.

One confirmation can cover a supported routing sequence, with each action visible. If the complete request needs narrower proposals for safe review, explain that requirement before writing. Do not silently attach only some requested numbers or omit a requested detachment while reporting the entire routing update as complete.

The pending proposal states that no changes have been made yet and expires in fifteen minutes. Live execution follows the connected owner's confirmation. Asking which number is currently configured or requesting an explanation of call measurement should remain read or conversational work.

Keep notes relevant to resulting behaviour. Retained assets, retained other relationships and the precise campaign scope matter. Raw provider payloads and asset IDs do not help an ordinary client judge routing. Readable presentation should simplify the approval without concealing an effect.

Verify the number and campaign relationship

The creation helper reads back the declared call-asset fields using the returned created identity. It separately checks the enabled campaign association. This establishes both stored content and the specific application rather than assuming one accepted response proves every intended field.

Existing attachment and detachment check the expected remaining enabled relationship set. The exact internal resource selection remains important even when client-facing messages omit IDs. Human-readable names and validated identity can coexist without exposing technical references.

A verified setting change does not establish provider approval or operational call handling. The agency should report the technical result prominently while preserving the remaining business and provider observations. The owner needs to know what was actually checked.

Current validation occurs before the write, while result verification occurs afterward. A proposal can become stale if another operator changes the account. The flow should communicate the actual current outcome rather than treating every confirmation as permission to override unreviewed intervening changes.

Reconcile uncertain execution

A missing Slack receipt is different from an uncertain provider write. The durable execution record and current asset and relationship evidence help establish what happened. Do not replay creation merely because the owner did not see a final message immediately.

The asset may exist while the complete association check remains unresolved, or the association may be known while a content field was unread. The next observation should address the actual missing milestone. An incomplete result should not be summarised as nothing changed.

For multi-action work, preserve each confirmed outcome. A successful detachment does not prove a later creation, and an uncertain creation does not show that earlier accepted work rolled back. A recovery plan should use the actual current state rather than an invented all-or-nothing assumption.

Assign one operator to reconcile the attempt. Another number proposal should wait for the relevant evidence and fresh approval. This coordination reduces the chance that an ambiguous notification creates several overlapping contact changes.

Keep the original requested number and relationship scope available during reconciliation. A provider read can show a current object, but the specialist must still compare it with the actual approved result. A similarly named asset or a different phone string is not enough to close an unresolved attempt as verified.

Continue the routing conversation in Slack

Begin with a focused request such as which call number is associated with Local Evening Courses and whether it uses account-level configuration. The answer should preserve the requested scope, current observations and unread lower-level detail. The compact audit can locate the issue without pretending it answered every branch.

A follow-up can ask to use the number the client just supplied. The assistant should retain the campaign and actual number context while preparing the supported operation. Ask only for genuinely missing information or unresolved ambiguity rather than forcing the owner to repeat the entire brief.

Creative or explanatory questions can remain conversational. The assistant can suggest how to explain the enquiry route to a client using known business facts without a new provider call. Claims about current account numbers or actual call totals require relevant evidence.

Keep progress visible without a user mention, and place mentions before the final feedback text and controls in normal replies. Avoid raw IDs and technical bodies in the client's thread. The important information is the selected route, scope, exact action and established outcome.

Read observed results at the right grain

Use compatible supported dimensions and metrics for the requested call report. Campaign-level conversions repeated beside every number would not measure each asset's individual contribution. Keep relationship, asset and conversion-action grains distinct.

Apply conditions precisely. Calls above a threshold differ from calls at least at that threshold, and missing data is not zero. Compound requests need their predicates at the correct row grain. A ratio with no denominator should remain undefined rather than becoming a convenient numeric result.

When the user asks for a chart, use the relevant actual period series. The native chart flow can present up to three compatible metrics with the twenty-point series limit. Coarser declared segmentation can keep a longer period in one chart unless the user explicitly requests daily detail.

Do not claim that a new number caused every later movement in reported calls. Other creative, targeting, staffing and measurement changes can matter. The agency can describe the established configuration and observed results without inventing causal certainty or a guaranteed uplift.

If two reports disagree, compare their declared scopes before changing the number again. Different conversion actions, periods or current-status filters can explain different totals. A routing mutation is not a general repair for a measurement mismatch. The assistant should investigate the definitions that produced the observations rather than choose a new contact setting to make them agree.

Avoid unnecessary collection and calls

The campaign detail reader collects its independent relationship and content sources concurrently and joins them locally. Explaining an already returned number set does not need a separate provider request for every asset. Reuse should retain the observation's scope and actual evidence.

A new exact attachment needs the relevant current campaign relationship and typed asset validation. It does not require every Merchant product, all historical keywords or every Analytics event. Additional evidence should answer a specific missing requirement, not expand automatically into a full account investigation.

Local dependency planning can identify the existing campaign parent without unnecessary prerequisite creation. The dedicated number action validates its known shape locally, while current provider checks and readback protect the actual operation. Efficiency should remove redundant work without removing these safeguards.

Do not promise a fixed latency or call count for every routing question. Provider conditions and requested evidence affect the work. The client should receive clear progress and a scoped result while infrastructure details remain in the appropriate internal records.

Leave a clear agency handoff

Record the campaign, approved number, country context, intended team and exact relationship action. Include whether the asset was reused or created and the verified or unresolved outcome. Another specialist should know the business route without decoding a raw API resource name.

Assign operational confirmation separately from provider settings. The business owner may need to verify the line's actual handling, while the account specialist tracks the relevant configuration or policy observation. Neither task is implied by the other's completion.

Retain the selected conversion definition for later reports. Primary calls, named actions and unique callers are not interchangeable. A future agency review should know what the earlier report counted and which measurement questions remain open.

Review a withdrawn number before applying any pending proposal that still contains it. A client can change its instructions while the agency is coordinating several teams. The retained conversation helps explain the sequence, but current preparation must use the complete requested result that the owner actually intends to approve.

Close each task at its own milestone. The campaign relationship can be verified while the operational team check remains pending, and both can finish before a useful performance window exists. This division gives the client a reliable account of progress without understating completed work or overstating the remaining result.

Use the broader agency audit workflow for account context and the call-assets audit guide for general routing concepts. The related sitelink review concerns a different asset type with different hierarchy behaviour.

Answer practical call-asset questions

Does one present call type prove every campaign has the right number?

No. The account presence check has a narrower predicate.

Does the campaign card certify exactly one own number?

No. Own call association presence is its compact positive condition.

Are distinct returned phone strings unique dialable identities?

Not necessarily. Formatting and actual content need appropriate review.

Does a call attachment set up every tracking option?

No. Contact configuration and measurement are separate tasks.

Can primary calls have conversion value?

Yes. Preserve their legitimate value in the selected primary scope.

Does verified configuration prove calls were answered?

No. Operational handling requires its own evidence.

Should uncertain creation be replayed?

No. Reconcile the recorded attempt and current resources first. Establish whether the asset and campaign relationship already exist with the approved content. A failed notification or incomplete status check does not justify another creation that might duplicate the original accepted request.