Where Does Demandbase Non-English Intent Come From?
Demandbase collects non-English intent signals through direct access to the bidstream via our B2B DSP (similar to English intent). This connects us to over one million web publishers, giving us visibility into the content of their articles.
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 and Best Practices for Creating Keyword Sets.
General Non-English Keyword Tips
See the following recommendations when creating non-English keyword sets:
- For easy reference, use a standardized naming convention for your keyword sets. For example, Product A - English, Product A - French.
- To convert English keywords into a specific language, open the English keyword set and copy all of the keywords. Paste and translate them in Google Translate and then copy the translated keywords back into Demandbase.
Tip: Create a new keyword set and enter keywords using the text view, instead of the list view. Using text view allows you to paste multiple keywords at once. - Each non-English keyword set should have between 25 and 50 validated keywords. If a keyword set includes fewer than 25 validated keywords, you should find additional keywords similar to the validated ones to reach the target of 25 keywords.
- For a single global advertising campaign, it’s recommended that you have a single keyword set with multiple languages of the same keywords (since an advertising campaign can only have one keyword set associated with it). This maximizes the number of intent-based impressions served during the campaign.
- For non-ad campaign keyword sets, use one language for each keyword set. Since teams are usually dispersed globally and manage their own regional GTM, we see each of these regional GTM teams managing their own keyword sets in their own native languages.
- Accents are considered different characters. For example, É and e are different.
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
Final Non-English Keyword Intent Review
After you create non-English keyword sets, you’ll want to review the results. To do so, return to the keyword sets one day after you save them 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 prevalent than English intent so don’t be surprised if many of the keywords are marked as problematic. However, it’s highly recommended that you keep the non-English keywords in the keyword set. As time passes, more non-English keywords are added to our vocabulary and marked with a green check mark.
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. |