Managing Microsoft Ads (Bing) by chat: campaigns without learning a second dashboard

Bing is the default on Windows and still holds a meaningful share of desktop search; its audience skews older, more corporate-device and more B2B in intent. In many industries the cost per click is noticeably lower than on Google simply because fewer advertisers compete.

The problem is that for someone who learned Google Ads, Microsoft Ads is a second interface, a second vocabulary and a second conversion tracking system. Most advertisers never open the channel for that reason. Managing by chat removes the barrier: you give Microsoft the same kind of instruction you already give Google, in the same conversation.

In Tecrube your Microsoft Ads account connects to Claude or ChatGPT through the same connector as Google Ads. Say “list the campaigns in my Microsoft account” and live data comes back; say “add these keywords to that ad group” and you see a preview first, then it is written on approval.

You do not need to know which menu hides which setting. The only thing you need to know is what you want; translating that into the platform's language is the tool's job.

Once the connector URL from your member panel (/app) is added to your assistant, the first Microsoft tool call opens an authorisation screen with your Microsoft account. You choose which ad account to manage; no password is shared and you can revoke access at any time.

If you already have a campaign structure in Google, you can say “rebuild my Google search campaign structure for Microsoft”. The tool reads the Google side and prepares a preview for the Microsoft side; you check geography, budget and language settings and approve.

The new-campaign preview shows campaign name, daily budget, target region, ad groups, keywords and match types in one table. The campaign is created paused; after reviewing landing pages and copy you enable it.

The budget rule that applies to Google applies here as well: a single-step increase above fifty percent is rejected. Typing one zero too many cannot reach your account because of that rule.

Microsoft Ads uses responsive search ads too: several headlines and descriptions that the platform combines at serving time. Have at least two RSAs written per ad group and make sure the headlines answer the search intent; in chat you can ask for “a headline set with three different angles for this group”.

For bidding, enhanced CPC or a conversion-focused automated strategy is a reasonable start, but moving to target CPA before conversion data exists starves the algorithm. Narrow location and audience settings by looking at your Google campaign's data: start with the cities that already convert.

Microsoft's conversion tracking is the UET tag, installed independently of Google's tag. If the tag is missing or no goal is defined, the campaign receives clicks and measures nothing. Before enabling, ask in chat whether the UET tag and conversion goals are in place; if not, the tool tells you which goal is missing.

If you use Google Tag Manager, adding the UET tag there is the cleanest route. With Tecrube's Tag Manager connection you can add the tag from chat and publish it after a preview, so both platforms' conversion definitions attach to the same events.

Microsoft Ads has its own import tool that copies Google campaigns; it is fast, but it carries Google's mistakes along and transfers bids and budgets one to one. The advantage of building by chat is selectivity: you can say “set up only the three converting ad groups, with the negative list, at forty percent lower budget”.

A practical rule: import if the Google account is clean, build selectively if it is messy. Either way, UET and conversion goals must be checked before enabling; Google's conversion data does not apply on Microsoft.

Daily for the first week, then weekly, ask for “the Microsoft campaign's last seven days: spend, clicks, conversions and the most expensive search terms”. Carrying your Google negative list over to Microsoft is usually the most profitable job of week one, and it takes a single approval.

Put Microsoft next to Google, not in place of it. Same intent, lower cost and a different audience; running both accounts from one chat brings the maintenance cost of that second channel close to zero.