Google Ads Message Assets: India Agency Lead Checklist (2026)

Direct answer

Google Ads message assets let eligible Search and Performance Max ads open conversations in WhatsApp, SMS, Facebook Messenger or Zalo. India is eligible on iOS, while Android availability is global. Agencies should confirm beta access, advertiser and provider verification, message ownership, response SLAs, consent, CRM capture and qualified-lead outcomes before launch. A message click alone does not prove lead quality or revenue.

What changed in Google Ads API v26?

Google Ads API v26 added LINE and SMS to the supported BusinessMessageProvider values. The API now includes provider-specific line_info and sms_info fields. A LINE asset uses a LINE Official Account ID that begins with @; an SMS asset uses a country code and phone number.

This is an API integration change, not proof that every advertiser can activate every provider. Google's Business Message Asset guide says API access is restricted by an allowlist and directs users to their account manager. Its current Google Ads interface instructions name WhatsApp, SMS, Facebook Messenger and Zalo. Confirm the provider and creation path in the specific account before promising it to a client.

For agencies with an allowlisted integration, v26 can reduce manual asset setup and make provider configuration more auditable. It does not remove the need for Google approval, advertiser verification, messaging-platform ownership or a staffed conversation workflow.

What does a Google Ads message asset do?

A message asset adds a messaging call to action to an eligible ad. When a user selects the message button, Google opens a conversation with the advertiser on the configured provider. When the user selects the ad headline, Google sends the user to the website instead.

Google currently supports message assets in Search and Performance Max campaigns. Its documentation also says that other asset types are not triggered when the message button serves, so an agency should not assume that a call asset or lead form will appear alongside the message interaction.

This creates two distinct customer paths:

• Website path: headline click to the landing page.
• Conversation path: message-button click to the provider inbox.

Both paths need ownership, measurement and privacy controls. A landing page that is well instrumented does not automatically make the messaging path measurable.

Are message assets available in India?

Google says message ads are available globally on Android. India is included in Google's current list of countries where message ads are eligible to serve on iOS.

Availability still depends on the account. Message assets are in beta and may not be visible to every advertiser. Google's current eligibility requirements include:

• a good history of policy compliance;
• an account in an eligible vertical or sub-vertical;
• completion of the Advertiser Verification program; and
• a messaging destination that Google can verify.

Sensitive verticals or sub-verticals, including campaigns and elections, are not eligible. Google also warns that new advertisers may receive limited message-asset impressions until they accumulate positive user interactions.

Treat “India is supported” as a market-level condition, not an account approval. Record whether the asset control is actually present, which provider is available, and whether Google has approved the asset.

Which messaging provider should an agency choose?

Choose the provider the client can operate reliably, not the one that looks novel in the setup screen.

Do not choose a provider from assumed popularity alone. Check audience behavior, device mix, market, language, account eligibility, inbox ownership, business hours, response capacity, consent requirements and CRM integration.

How should account, campaign and ad-group scope work?

Google's API documentation allows business message assets to be linked at the account, campaign or ad-group level. Only one enabled asset per provider type is allowed at each level. For responsive search ads, Google applies the lowest eligible level in the hierarchy: customer, then campaign, then ad group.

That hierarchy can create quiet routing mistakes. An account-level WhatsApp number may be correct for one brand but wrong for a regional campaign or specialist product team. Before launch, export the effective scope and answer:

1. Which provider and inbox will actually serve for each campaign or ad group?
2. Does the inbox owner understand the advertised product, language and offer?
3. Will a lower-level asset override the account-level default?
4. Who disables an obsolete asset when ownership changes?
5. How will the agency test the live interaction without creating false leads?

Record the asset ID, provider, hierarchy level and effective owner. A screenshot of the setup screen is not enough if a lower-level asset can override it.

What verification and policy checks are required?

Google requires the message destination to relate to the advertised company. Its policy gives two main verification routes:

• show the messaging-platform link on the business website or social page used in the ad, with the same domain as the display URL where applicable; or
• verify domain ownership by linking Search Console and Google Ads or by using an eligible conversion or remarketing tag.

Phone-based message assets also require phone-number verification. The starter message must follow Google's editorial and advertising policies. Google advises advertisers not to mention the messaging platform in the ad headline because the headline goes to the website, not the conversation.

The verification record should include the destination, business identity, approved domain, phone or provider account, evidence route, review status and last checked date. Use the Limited Ad Serving checklist as a separate advertiser-identity control; message-asset approval does not settle every account-serving issue.

Original artifact: message-asset release and lead-handling register

Use one row per effective asset and campaign scope. Do not launch until the interaction and the operational handoff have named owners.

How should the starter message be written?

The starter message should begin the exact conversation the business can continue. It should not promise a response time, price, availability or outcome the inbox team cannot deliver.

A practical starter message does four things:

1. identifies the topic or offer;
2. asks for the minimum useful information;
3. avoids collecting sensitive data before the approved process begins; and
4. gives the human team enough context to route the inquiry.

Keep the first interaction short. A message that asks for a full application, payment information or extensive personal details creates unnecessary risk and abandonment. If the client needs regulated or sensitive information, move the user to the approved secure workflow rather than collecting it informally in chat.

Review every language version. A translated message can change the promise, required information or consent meaning even when the English master is approved.

How should an agency staff the conversation path?

The media campaign and the inbox schedule must agree. If ads run overnight but the client answers only during business hours, set the expectation honestly and route the conversation to a queue with a defined next action.

Before activation:

• test the button on supported devices;
• verify the destination account and welcome text;
• assign the primary and backup inbox owners;
• define business hours and language coverage;
• set response and escalation targets;
• train the team on the offer and disallowed claims;
• connect the conversation to a governed CRM record; and
• create a pause rule for unstaffed periods, policy incidents or sustained SLA failure.

Do not optimize delivery toward message conversions while the operations team cannot answer or qualify the resulting conversations. More message clicks can worsen customer experience when the handoff is broken.

How should message-asset performance be measured?

Google's current reporting documentation lists impressions, clicks, cost, CTR, CPC, conversions, view-through conversions and supported offline retail measures. After an asset is added and approved, the “Leads from Messages” conversion goal becomes available for campaign setup.

Those platform metrics are the start of the measurement chain, not its end. An agency should reconcile:

1. message-button interactions;
2. conversations that successfully reached the inbox;
3. unique people after deduplication;
4. conversations meeting the approved qualification standard;
5. opportunities, orders or other governed business outcomes; and
6. response time, abandonment and disqualification reasons.

Do not treat a message click, conversation start and qualified lead as interchangeable. Preserve the conversion definition and any offline import logic. Use the Data Strength measurement checklist to separate platform-reported uplift from qualified business outcomes, and the measurement stack guide when deciding whether attribution, an experiment or a broader model answers the client question.

What can public ad data not prove?

Public Meta or Google ad data may show an advertiser, message, visible call to action, landing page or served date. It cannot prove the competitor's effective asset hierarchy, provider account ownership, verification route, beta access, inbox staffing, response time, conversation volume, consent process, CRM match, qualification standard, bid strategy, budget, cost, conversions, revenue, margin or incrementality.

An observed message button also cannot prove that the conversation path worked or that the advertiser replied. Public ad libraries may omit interactive assets or show them differently from live placements. Use the Advertisng research methodology to record only what is observable and the public ad-intelligence workspace to organize public creative evidence. Keep private message content and customer data in authorized client systems.

Frequently asked questions

Are Google Ads message assets available to every account?

No. Message assets are in beta, and Google says the feature may not be available in every account. Eligibility also depends on policy history, advertiser verification and vertical.

Can message assets run in India?

Google says message ads are available globally on Android and lists India among the eligible iOS countries. Account and provider eligibility still need to be confirmed.

Which campaigns support message assets?

Google's current Help documentation supports message assets in Search and Performance Max campaigns.

Does API v26 make LINE and SMS available everywhere?

No. API v26 adds LINE and SMS provider fields, but Business Message Asset API access is allowlisted. Confirm support with the account manager and in the target customer account.

Does a message click count as a qualified lead?

No. It records an interaction under the configured measurement. Qualification requires a separate definition and evidence from the inbox, CRM or other authorized business system.

Can one message asset be used for the whole account?

It can be linked at account level, but campaign or ad-group assets can take precedence. Use one account-level destination only when its team, language, product knowledge and operating hours fit every affected campaign.

Can the starter message ask for sensitive personal information?

Agencies should minimize data collection and follow the client's approved legal, privacy and security process. Move regulated or sensitive information to a secure authorized workflow instead of assuming a messaging inbox is appropriate.

Can competitor message assets reveal response quality?

No. Public evidence cannot show whether the inbox was staffed, how quickly the advertiser replied, whether the conversation qualified or whether it produced revenue.

A restrained next step

Choose one eligible Search or Performance Max campaign and complete the release register before activating the message asset. Test the website and conversation paths separately, staff the inbox, define the qualified-lead outcome and confirm the pause rule. Use Advertisng only for observable public-ad research; do not place private conversations, phone numbers or customer records in the competitor-research workspace.

Primary sources

1. Google Ads API: Release notes, API v26 addition of LINE and SMS Business Message Asset provider support; reviewed October 23, 2026.
2. Google Ads API: Business message assets, supported providers, allowlist access, required provider data, hierarchy and linking rules; reviewed October 23, 2026.
3. Google Ads Help: About message assets, beta status, campaign types, eligibility, advertiser verification and setup requirements; reviewed October 23, 2026.
4. Google Ads Help: How message assets work, website and conversation click paths and other-asset behavior; reviewed October 23, 2026.
5. Google Ads Help: How to use message assets, campaign setup, provider inputs and Leads from Messages goal; reviewed October 23, 2026.
6. Google Ads Help: How to report on message assets, reporting metrics and Android/iOS availability including India; reviewed October 23, 2026.
7. Google Advertising Policies Help: Message asset requirements, business relationship, domain and phone verification, review and editorial requirements; reviewed October 23, 2026.