1. Start with a clear include rule
Each automation needs at least one include rule. GUIDE or SEND LINK is easier to explain than a broad everyday word. A match on any include rule is sufficient; several matches in one comment do not create multiple messages.
The default word/phrase operator respects letter and number boundaries. The word price matches “PRICE please” but does not match “priced”. A phrase must remain contiguous after whitespace normalization.
2. Use contains and exclusions deliberately
Contains matches a contiguous substring without word boundaries. It can match price inside priced, so use it only when that broader behavior is intended.
Exclusions take precedence: a comment matching both an include and an exclude rule is ignored. Keep your negative examples in the preview check so a future edit does not broaden the campaign unexpectedly.
3. Check the saved language policy
Case handling follows the saved matching locale. Exact mode preserves accents; cafe is not café. For Turkish automations, the Turkish keyboard option can treat i/ı, ş/s, ç/c, ğ/g, ö/o and ü/u alike.
This is not spelling correction or semantic matching. Changing the draft policy does not rewrite historical versions. Review the locale and mode before activation.
4. Preview a small test set
Preview does not send real messages. Use comments written specifically for the test and record the expected result.
- Test the keyword with upper/lower case and punctuation.
- Test a longer word containing the keyword.
- Test a negative phrase and a comment without keywords.
- For Turkish, test both keyboard spellings under the selected policy.