1. Overview
Deploying Sensefuel’s JavaScript tags correctly is essential to ensure optimal search and recommendation performance. This document outlines best practices, technical requirements, and important considerations related to tag placement, content security, and activation timelines.
2. Deployment Responsibilities
The integration method for the Sensefuel tags is entirely under your control. You may deploy the tags:
- Directly in your website’s source code, or
- Through a Tag Management System (TMS) such as Google Tag Manager (GTM)
Both approaches are fully supported, as long as the placement rules described below are respected.
3. Placement Requirements
3.1 Deploy on All Pages
Sensefuel tags must be present on every page of your website.
This ensures:
- Continuous tracking
- Accurate behavioral signals for AI training
- Proper initialization of the search and recommendation components
3.2 Position in the HTML Document
Tags must be placed as high as possible in the <head> section of your pages.
This is crucial because:
✅ It ensures Sensefuel is loaded early, before the user interacts with the search box.
✅ Recommendations can be preloaded without delay.
✅ The search layer is immediately available, ensuring the best UX.
3.3 Asynchronous Loading
All Sensefuel JavaScript tags load asynchronously.
This means:
- They never block page rendering
- They do not impact core web performance
- They load in parallel with other resources
4. Content Security Policy (CSP) Requirements
If your website uses a Content Security Policy (CSP), you must explicitly allow Sensefuel domains.
Add the following domains and sub‑domains to your CSP configuration:
*.search.sensefuel.live *.sensefuel.live
This ensures that the platform can load resources and operate without restrictions.
5. AI Warm‑Up Period (Mandatory)
5.1 7‑Day Learning Phase
Once the tags are deployed on your website, you must wait at least 7 days before activating Sensefuel for users.
During this warm‑up period, Sensefuel’s AI:
- Observes real user behavior
- Learns from navigation patterns
- Optimizes ranking models
- Prepares the environment for relevant search results
5.2 Activation After Warm‑Up
After the 7‑day period:
- Your Customer Success Manager (CSM) will gradually enable Sensefuel for your visitors.
- Exposure can be progressive (percentage‑based rollout).
6. Forcing the Layer (Internal Testing)
During the warm‑up period, you may want to preview the Sensefuel search layer even though it is not yet publicly activated.
You can do this by:
✅ Enabling the internal toggle in your Sensefuel platform’s deployment interface.
This activates the search layer only for your browser, allowing private testing without affecting users.
7. Optional: First‑Party Tag Deployment
Sensefuel tags can also be deployed as first‑party tags using subdomain delegation.
Example:
search.yourdomain.com
This option may be beneficial for:
- Improved tracking resilience
- Better compatibility with privacy settings
- Higher trust and lower browser restrictions
If you wish to enable first‑party tagging, simply contact your Sensefuel representative.
Want to know more ?
8. Summary Table
| Requirement | Description |
|---|---|
| Deployment responsibility | Your team (code or TMS) |
| Required pages | All pages of the website |
| Placement | Highest possible in <head>
|
| Loading mode | Asynchronous |
| CSP configuration | Allow *.sensefuel.live and *.search.sensefuel.live
|
| Warm‑up time | Minimum 7 days |
| Testing | Forced layer via platform toggle |
| Optional | First‑party deployment with subdomain delegation |