Best Practices for Creating Non-English Intent Keyword Sets

  • Updated

Demandbase collects non-English intent signals through direct access to the bidstream via our B2B DSP (similar to English intent) and other proprietary and licensed data sources. This connects us to over one million web publishers, giving us visibility into the content of their articles.

Important: We track exact matches of intent keywords on content.

Using natural language processing, AI, and proprietary techniques, Demandbase scans articles for keywords from our library. We then provide unique user views for the most relevant keywords. 

These views are aggregated weekly and scored based on relative strength of activity (low, medium, high). We also track “trending intent” indicators when intent activity increases significantly.

See Understanding Demandbase Intent, Best Practices for Creating Keyword Sets, and Set Up Demandbase Intent: Create Keyword Sets.

Best Practices for Non-English Intent

Consider the following when creating non-English keyword sets. 

Naming Conventions & Organization

  • Standardized Naming: Use a consistent naming convention for easy reference. For example, Product A - English, Product A - French.
  • Single Keyword Set for Global Ad Campaigns: For a single global advertising campaign, use one keyword set containing multiple languages of the same keywords. This maximizes intent-based impressions.
  • Single Language Keyword Sets for Non-Ad Campaigns: For non-ad campaign keyword sets, use one language per keyword set. This supports regional GTM teams managing their own keyword sets in their native languages.

Keyword Quantity & Quality

  • Keyword Set Size: Ensure each non-English keyword set contains 25 to 50 validated keywords. If a set has less than 25, add related keywords to reach the minimum.

Keyword Creation & Translation

  • Representative URLS: Use the Suggest from URL feature to find websites your target customers are likely to visit, so Demandbase can extract relevant keywords.
  • Generative AI for Translation:
    • Don’t use Google Translate to translate your keywords. Google Translate’s literal translations often miss nuances and cultural context crucial for intent-based marketing, and accuracy varies widely. 
    • Leverage Generative AI tools powered by large language models (LLMs) like Gemini or ChatGPT, which use transcreation. Transcreation adapts the message while preserving its intent, style, tone, and context. 
    • Copy all the keywords in an English keyword set, paste and translate them in ChatGPT or Gemini, and then copy the translated words back into Demandbase as a new keyword set. Tip: Enter keywords using the text view to allow pasting multiple keywords at once.

Intent-Data-keyword-list-text.png

Important: Accented characters are distinct (e.g., É is different from e). Case is ignored for keywords (i“Resume” and “resume” are the same). Special characters like dashes (-) and apostrophes (‘) are removed.

Final Non-English Intent Review

After you create non-English keyword sets, review the results. Wait one day after saving, then return to the keyword sets and check the validation status. Validated keywords have a green check mark next to them. Keywords that could not be validated have a red exclamation mark next to them.

Tip: Non-English intent is less common than English intent so it’s expected that many of the keywords are initially marked as problematic. However, we highly recommend that you keep the non-English keywords in the keyword set. Over time, Demandbase expands its non-English keyword vocabulary, and these keywords may eventually be validated and marked with a green checkmark.

Intent-Data-keyword-status.png

 

The following table lists the validation statuses for keywords:

Status Definition Recommended Action
Validated This keyword is in our vocabulary and is eligible for collecting content. None
Pending validation The keyword needs to be validated to determine if it can be added to our vocabulary. Save the keyword set to start the validation process. The process takes up to 24 hours.
Validating The keyword is being validated to determine if it can be added to our vocabulary. Wait for the validation process to finish. The process takes up to 24 hours.
Too much content The keyword cannot be added to our vocabulary because it is too broad.

Add to the keyword to make it more specific or remove it.

Tip: Consider making the keyword plural or adding words to the keyword phrase to return a smaller set of account results.

Not enough content The keyword cannot be added to our vocabulary because it is too specific.

Wait 30 days for the keyword to be revalidated or revise it.

Tip: Consider shortening the keyword phrase to make it less specific or remove and replace it.

Too long The keyword cannot be added to our vocabulary because it exceeds the recommended phrase length of eight words. Shorten the keyword phrase to less than eight words.
Excluded The keyword cannot be added to our vocabulary because it is too broad and has been added to the Exclusion List. Revise the keyword.
Ineligible The keyword cannot be added to our vocabulary for a reason other than the above statuses. Double check the spelling and contact Support if there are any more issues.

Non-English Intent Languages

Demandbase supports 133 languages.

  • Afrikaans
  • Albanian
  • Amharic
  • Arabic
  • Armenian
  • Assamese
  • Aymara
  • Azerbaijani
  • Bambara
  • Basque
  • Belarusian
  • Bengali
  • Bhojpuri
  • Bosnian
  • Bulgarian
  • Burmese
  • Catalan
  • Cebuano
  • Chewa
  • Chinese (Simplified)
  • Chinese (Traditional)
  • Corsican
  • Croatian
  • Czech
  • Danish
  • Dogri
  • Dutch
  • English
  • Esperanto
  • Estonian
  • Ewe
  • Filipino (Tagalog)
  • Finnish
  • French
  • Galician
  • Georgian
  • German
  • Greek
  • Guarani
  • Gujarati
  • Haitian Creole
  • Hausa
  • Hawaiian
  • Hebrew
  • Hindi
  • Hmong
  • Hungarian
  • Icelandic
  • Igbo
  • Ilocano
  • Indonesian
  • Irish
  • Italian
  • Japanese
  • Javanese
  • Kannada
  • Kazakh
  • Khmer
  • Kinyarwanda
  • Konkani
  • Korean
  • Krio
  • Kurdish (Kurmanji)
  • Kurdish (Sorani)
  • Kyrgyz
  • Lao
  • Latin
  • Latvian
  • Lingala
  • Lithuanian
  • Luganda
  • Luxembourgish
  • Macedonian
  • Maithili
  • Malagasy
  • Malay
  • Malayalam
  • Maldivian
  • Maltese
  • Māori
  • Marathi
  • Meitei
  • Mizo
  • Mongolian
  • Nepali
  • Northern Sotho
  • Norwegian (Bokmål)
  • Odia
  • Oromo
  • Pashto
  • Persian
  • Polish
  • Portuguese
  • Punjabi (Gurmukhi)
  • Romanian
  • Russian
  • Samoan
  • Sanskrit
  • Scottish Gaelic
  • Serbian
  • Shona
  • Sindhi
  • Sinhala
  • Slovak
  • Slovene
  • Somali
  • Sotho
  • Southern Quechua
  • Spanish
  • Sundanese
  • Swahili
  • Swedish
  • Tajik
  • Tamil
  • Tatar
  • Telugu
  • Thai
  • Tigrinya
  • Tsonga
  • Turkish
  • Turkmen
  • Twi
  • Ukrainian
  • Urdu
  • Uyghur
  • Uzbek
  • Vietnamese
  • Welsh
  • West Frisian
  • Xhosa
  • Yiddish
  • Yoruba
  • Zulu

Was this article helpful?

0 out of 0 found this helpful