Most teams only need four implementation values from Webless: your company
identifier, your script URL, your tag ID or IDs, and any API or SSO
credentials relevant to your rollout.
Launch checklist
Gather the values Webless provisioned for you
Confirm the values below before you touch your templates or integrations.
| Value | Where you use it |
|---|---|
| Company identifier | Search API and Data API requests |
| Script URL | Hosted tag installation |
| Tag ID or container IDs | Hosted tag and navbar placement |
| API key | Data export API |
| SAML provider ID and ACS URL | Okta setup |
Choose your launch path
Pick the smallest integration that fits your needs.
Hosted tag
Use the hosted Webless tag if you want Webless to render the experience
inside your site.
Custom frontend
Use the backend APIs if you want to build your own UI around search,
summaries, suggestions, and CTAs.
Verify the browser experience
Open your website and confirm the Webless experience appears where you
expect it.
- Check that the script loads successfully.
- Check that the target container exists before the script runs.
- Check that no console errors appear.
- Check desktop and mobile behavior if you use navbar entry points.
Add optional workflows
Expand the rollout only after the core experience works.
- Add embedded forms.
- Connect Slack support handoff.
- Send events to Clay.
- Configure Okta SAML.
- Set up data export.
Before you ask for help
- Capture the full script URL you deployed.
- Capture the exact container ID on the page.
- Capture the page URL where the issue happens.
- Capture a screenshot of the browser console if an error appears.