Contexts
Create reusable customer situations and use them to test how AI engines answer for different shopper needs.
What context means
A context is the situation of the person asking the AI. For example: "oily but dehydrated skin, looking for pore care, shopping for K-beauty in the US." Save those situations once, then test the same prompt through different shopper needs.
Context does not rewrite the visible prompt. AEKO stores it separately and passes it to the AI as user-situation instructions at call time. That lets you compare which brands appear for the same question under different needs.
Where to manage it
Analyze → Context
The Context tab now contains both review-derived contexts and saved contexts. You can create saved contexts manually even if no store or review integration is connected.
Saved contexts
Add reusable customer situations with a title and summary. They appear in tracking modals and can be archived when they are no longer useful.
Review contexts
When Shopify or Cafe24 reviews are connected, AEKO can surface recurring problems and use cases from real customer language.
Using context in tracking
When you select one or more contexts while tracking a prompt, AEKO creates one tracked variant per selected context. You can test the same prompt for needs like "sensitive skin," "gift purchase," or "checking low-irritation ingredients."
Example
Prompt: "Recommend Korean sunscreens I can buy in the US"
Context: "Oily, acne-prone skin. Wants low white cast and something easy to wear before makeup."
Different from brand matching
Context changes the shopper situation behind an AI run. Brand-name variants such as 코스알엑스, COSRX, and cosrx are mention-matching keywords and live under Settings → Domain Management.