Orleans · Ottawa

Bilingual campaign operations for Orleans, where half the audience searches in French

Orleans holds the largest francophone concentration in Ottawa, and a business serving it is running two languages through one account, one website and one report. That is an operations problem rather than a translation problem, and it is where most bilingual accounts quietly go wrong. The keyword list was produced by running the English one through a translator. The language setting is understood to target the language of the search, which is not what it does. The French ads point at English pages. And the report shows one blended cost per acquisition, so nobody can see that one language is subsidising the other, or which one it is.

Why Orleans is its own case

Take the keyword list first, because everything else inherits its mistakes. French search behaviour is not English search behaviour with different words. Queries are longer, accented and unaccented spellings both occur in volume and have to be covered, and real usage in this market mixes borrowed English terms with French ones in ways a dictionary translation will not produce. A list built by translation also inherits English negatives that do not apply and misses French ones that do, and because the French corpus is thinner, broad match and automated bidding have less to learn from and drift further when they guess.

Then the setting that causes the most damage per character. Language targeting in the major ad platforms is based on the user's interface and content language settings, not on the language of the query itself. A person browsing with a French interface who happens to type an English brand name is in the French audience; an English-interface user typing a French query is not. Treating it as query-language targeting produces an account that appears to be running French and is mostly not.

Then structure. The languages belong in separate campaigns rather than in ad groups inside one campaign, for three practical reasons: budget can be set and protected per language, negatives stay separable, and the reporting splits without any additional work. Sharing a campaign means one language quietly consumes the budget of the other, and the report cannot tell you it happened.

Then the landing page, which is where money is actually lost. A French ad pointing at an English page hurts twice, once because the visitor leaves and once because ad relevance and landing page experience are inputs to what the click costs. Translating the page is the cheap half; keeping the two versions in step as the offer changes is the half that fails six months later.

One geographic footnote that only applies out here. Ottawa and Gatineau are a single metropolitan area split by a provincial boundary, so a radius drawn from an Orleans address reaches into Quebec, where consumer rules and French-language obligations are not the same as Ontario's. That is a deliberate decision to make, not an accident to discover in a location report.

The work, as it applies here

Google Ads account audit

A structural read of a bilingual account: whether the languages are separable, whether language targeting is doing what the team believes it does, whether the French negatives are French, and whether either language is being funded by the other without anyone deciding that.

GA4 & GTM implementation

Instrumenting language as a first-class dimension rather than inferring it from the URL after the fact, so behaviour, conversion rate and value can be reported per language across a site where both versions share a template.

Automated client reporting

Reporting that carries English and French as separate lines by default, with the blended figure available but never the headline, so a language that is underperforming is visible in the first minute rather than in the third quarter.

FAQ: Orleans

Can we just translate our English keyword list into French?

It is the most common shortcut here and it reliably underperforms. Translation gives you the words people would use if they were writing a sentence, not the words they type into a search box, and it misses the accented and unaccented variants, the borrowed English terms that are in genuine use in this market, and the longer query patterns French searchers tend to produce. Build the French list from French search data and from what your own French-speaking customers actually say, then check it against the English list for gaps rather than deriving it from one.

Does language targeting in Google Ads target the language of the search?

No, and this is the single most expensive misunderstanding in a bilingual account. It targets people based on their interface and content language settings, not on the language of the individual query. So a user whose browser and account are set to French is in your French audience whatever they happen to type, and an English-interface user typing a French phrase is not. The practical consequence is that language targeting is a coarse audience filter, and the thing that actually matches a French query is a French keyword.

Should French run as its own campaign or as an ad group inside the English one?

Its own campaign, in almost every case. Budget is set at the campaign level, so sharing one means the language with more volume quietly absorbs the spend and nobody has decided that. Negatives applied at the campaign level stay where they belong instead of leaking across languages. And the reporting splits for free, which matters more than it sounds, because a split that requires a filter is a split nobody applies. The cost is a slightly larger account, which is a good trade.

Our radius targeting from Orleans reaches into Gatineau. Is that a problem?

It is a decision rather than a fault, and it should be made deliberately. Ottawa and Gatineau are one metropolitan area across a provincial boundary, so a radius that makes sense on a map crosses into a jurisdiction with different consumer rules and different French-language obligations for businesses operating there. If you genuinely serve that side, target it on purpose and account for what selling there requires. If you do not, exclude it, because the alternative is paying for clicks you cannot convert and diluting the location data you use to make the next decision.

Our French cost per acquisition looks terrible. Should we turn it off?

Not before checking three things, because in a badly built bilingual account the French numbers are usually measuring the account rather than the audience. Are the French ads landing on French pages, or on English ones. Is the French campaign sharing a budget it keeps losing. Are the conversions on the French side even being tracked, or does the French version of the form sit on a page the tag never fired on. Those three explain most of the gap. If the French numbers survive all three, then it is a real result and worth acting on.

How do we report on two languages without doubling the length of the deck?

Report the same small set of metrics twice rather than reporting twice as many metrics. One table with a row per language and columns for spend, conversions, cost per acquisition and revenue tells the whole story in one glance, and the blended figure goes underneath as a total rather than at the top as the headline. The rule worth holding is that no chart in the deck should combine the languages without also showing them apart, because the combined number is the one that hides the problem.

Reading that applies

Also covered by this page

These 31 places raise the same questions as Orleans and are answered here rather than on a page of their own. Every one of them is inside the City of Ottawa.

  • Vanier North
  • Vanier South
  • Overbrook
  • Viscount Alexander Park
  • Ramsayville
  • Beacon Hill North
  • Beacon Hill South
  • Rothwell Heights
  • Avalon
  • Fallingbrook
  • Chapel Hill
  • Chapel Hill South
  • Convent Glen
  • Queenswood Heights
  • Queenswood Village
  • Chateauneuf
  • Bilberry Creek
  • Hiawatha Park
  • Cardinal Creek
  • Notre-Dame-des-Champs
  • Sarsfield
  • Vars
  • Carlsbad Springs
  • Bearbrook
  • Piperville
  • Marionville
  • Vanier
  • Blackburn Hamlet
  • Beacon Hill
  • Cumberland
  • Navan

Kodelytics Inc. works remotely from one address in Kanata and has no office, phone line or staff in Orleans. This page describes how the work applies to businesses there, and claims nothing else.

Start a conversation