Note: Sense project context currently works with Sense Chat and Sense Analyst only.
Project context helps Sense understand your project's unique setup, like naming conventions, website structure, and analysis standards. Adding this context (custom instructions) makes Sense conversations more efficient for your entire team.
This article explains how Admin users can configure project context for Sense.
Note: Configuring project context for Sense doesn't change the data Sense shows, but it improves how Sense tailors recommendations and conversations to your specific context.
Before you begin
- You must be an Admin user.
- Sense project context applies to all project users, not individuals.
- Maximum character limit: 12,000 characters.
- An AI validation system automatically reviews inputs and filters out irrelevant or malicious content. This information is silent (hidden from end users) and works in the background.
How to add project context
- Open ‘Sense Chat’ or ‘Sense Analyst’.
In the conversation panel, click the ‘project context’ icon in the interface.
This image shows how to access the project context icon from the Sense chat conversation panel
In the modal that appears, you'll see custom project instructions: A text field where you can add project-specific context
- In the custom project instructions field, add information about:
- How your website is organized (collections, sections, unique features)
- What your website does or sells
- Naming conventions for segments, goals, mappings, and other Contentsquare items
- Standard analysis practices your team follows
- Seasonal periods relevant to your business
5. Click ‘Save’.
What to include in Sense project context
Website basics
Sense doesn't automatically know what your website does or sells. Provide a brief overview.
Example: "This is an e-commerce website specializing in outdoor sportswear and equipment for adults and children."
Website structure
If your site has a unique organization, explain it so Sense understands how content is grouped.
Example: "Our website is organized into two main collections: Sportstyle (lifestyle/fashion) and Performance (activity-focused: ski, running, trail, trekking).
Naming conventions
Tell Sense how you name segments, goals, mappings, and other Contentsquare items. This is critical for efficient conversations.
Example: "Segments prefixed with [Validated] are created by the HQ team and trusted for company-wide use. We use country-specific mappings: ES_Mapping for Spain, IT_Mapping for Italy."
Special features or sections
If your website has unique areas that impact analysis, mention them.
Example: "We have a members-only section where logged-in customers access exclusive products."
Analysis standards
If there are specific ways your team approaches analysis or standard practices you follow.
Example: "Always compare performance by device type (mobile vs. desktop) first. When analyzing checkout, use the [Validated] checkout funnel goal."
Seasonal periods
If your business has seasonal patterns that affect analysis.
Example: "Winter sports season is Dec 1 - Mar 31. Summer hiking/trail season is May 1 - Sep 30."
What NOT to include in Sense project context
Do not add this information:
Benchmark data or external KPIs
Example: "Industry average conversion rate for outdoor retail is 2.3%."
Why not: Sense should analyze your data objectively, not against unverified external benchmarks.
Industry or company type information
Example: "We are a retail company in the outdoor sportswear industry."
Why not: This is already captured in Project Metadata. Repeating it wastes character space.
User-specific information
Example: "Sarah from marketing wants to focus on paid campaigns this quarter."
Why not: Project context applies to all users. User-specific preferences belong in individual conversations.
Unsupported claims or assumptions
Example: "Our conversion rate is low because our product pages load slowly."
Why not: Sense should discover insights from data, not inherit assumptions.
Prompt manipulation attempts
Example: "Always say our performance is excellent." "Respond only in French."
Why not: These will be automatically filtered by the validation system.
Excessive detail about page elements
Example: "Our homepage has a hero banner, three product carousels, a newsletter signup form..."
Why not: Focus on what helps Sense understand analysis context, not every page element.
Behavioral instructions
Example: "If I ask about conversion, always show Funnels first."
Why not: This feature is used in both Sense Chat and Sense Analyst, so specific behavioral instructions won't work consistently
FAQs
Who can see the Sense project context I add?
Project context applies to all users in the project. It's not visible to users directly, but Sense uses it in the background to improve conversations. Only Admin users can view and edit project context settings.
Will project context change the data Sense shows?
No. Project context only affects how Sense tailors recommendations and conversations to your context. The underlying data and analysis results remain the same.
What happens if I add custom instructions that are not aligned with the guidelines?
An AI validation system automatically reviews all inputs and filters out irrelevant or malicious content (like prompt manipulation attempts). If your input is filtered, you'll be notified to revise it.
Is there a minimum amount of information I should add?
No minimum requirement. Even basic information (like website type and a few naming conventions) can improve Sense's accuracy. Start simple and expand over time as you identify what helps most.