This guide explains the most common error messages shown by the Force Experiment Tool bookmarklet and what they typically indicate when Webtrends Optimize experiences do not appear as expected.
It is intended to help with troubleshooting and focuses on how to interpret visible symptoms, what they usually mean, and which checks are most useful to do next.
The Force Experiment bookmarklet is a useful tool, but its error messages are indicators rather than final root-cause conclusions. A message can point strongly toward a likely issue, but confirmation usually comes from checking tag availability, page load timing, browser behaviour, and debug output.
How to read bookmarklet messages
When experience(s) do not display, the bookmarklet message(s) can help narrow the problem quickly. In most cases, the result falls into one of three broad categories:
The Optimize tag is unavailable, blocked, or not yet ready
The page did not become ready in time, causing a timeout condition
The tag or experiment started but did not complete normally, often because execution was interrupted
These categories are reflected in the most common messages below.
Common bookmarklet messages
Bookmarklet message | What it usually indicates | What to check next |
Optimize is not active | The Optimize tag is not available to the bookmarklet at the time it checks. This may mean the tag is missing, blocked, still loading, or unable to run normally.
|
|
Optimize has aborted | The Optimize tag has aborted, if no timeout exceeded message is also present this usually indicates an unhandled error either in the tag itself or from one of the Optimize experiences running on the page. |
|
Timeout exceeded | The Optimize tag has aborted, and active state was not reached within the allowed time. This usually points to slow page readiness and optimize has timed out waiting. |
|
Tag context shows Default | The expected Optimize tag context was not established correctly after the tag has loaded. This is usually a sign that something interrupted normal execution rather than a valid tag context. |
|
What each message means in practice
Optimize is not active
This message usually means the bookmarklet could not detect an active Optimize tag when it performed its check. That does not always mean the implementation is absent. It can also mean the tag was delayed, blocked, or prevented from completing startup.
This message is especially worth investigating when the issue appears in some environments but not others. Internal networks, managed browsers, and privacy protections can affect whether the tag loads successfully.
Common explanations include:
The Optimize tag is not present on the page
The tag has not finished loading yet
A browser extension or privacy tool blocked the tag
Firewall, proxy, or network policies prevented the request
An execution issue stopped the tag before it became active
Reload the bookmarklet, after waiting for the page to finish loading, if the experience(s) appear and the error message goes, this suggests delayed loading of the tag.
If the problem persists inspect the page using your browsers devtools to see if the Optimize tag is present on the page and has loaded without being blocked.
Optimize has aborted
This message indicates the Optimize tag has aborted, if there is no timeout exceed message present this usually indicates an unhandled error either in the tag itself or from one of the Optimize experiences running on the page.
Common contributors include:
Javascript syntax errors
Javascript written in a way which is not fail safe
Timeout exceeded
This message usually indicates that Optimize waited for the page to reach the expected readiness state, but that process took too long. This often means the page environment is slow or delayed enough that the experiment could not be applied within the expected window.
Common contributors include:
Slow page resources
Third-party scripts delaying readiness
Heavy client-side rendering
A page mode setting that is not ideal for the site structure
Because of this, a timeout message should usually lead to investigation of load sequence and readiness behaviour first.
Followed by reviewing the Optimize tags page mode and timeout settings.
Default context
When the bookmarklet shows a Default tag context, the most helpful interpretation is that the expected context was never fully established. In other words, Default is usually a symptom of an interrupted or incomplete load process.
This can happen when:
The tag did not load correctly
The tag loaded too slowly to establish context in time
An unhandled error interrupted execution
Underlying causes the bookmarklet can help reveal
Blocked or unavailable tag
If the tag is genuinely unavailable, the bookmarklet cannot force the experience. This is often the simplest explanation when Optimize is not active appears consistently.
Likely causes include missing tag, client specifc browser controls, privacy protections, corporate security tooling, or network-level filtering.
Slow-loading tag or page
If the page or tag loads too slowly, the bookmarklet may check before Optimize is fully ready. In these situations, the issue can appear intermittent and may improve after reloading the Force Experiment tool or retrying later in the page lifecycle.
Unhandled execution error
If a JavaScript error occurs in the page, the test code, or a related dependency, execution can stop before an experience is applied. This is one of the more common explanations for inconsistent behaviour across sessions or environments.
Test-specific issue
Sometimes the tag is working, but a specific experience still does not run correctly. In that case, the bookmarklet may help confirm that the problem is not broad tag inactivity but a more local issue in the test setup or execution path.
Recommended troubleshooting steps
If the issue can be reproduced, these are the most useful next checks:
Confirm the Optimize tag is present on the affected page
Retry after the page has fully loaded to see whether delayed readiness is involved
Check whether browser extensions, privacy controls, or network policies could be blocking Optimize
Use debug mode in OBF and CAPI to identify unhandled errors
Review whether slow page elements or third-party dependencies are delaying execution
Check whether the issue affects all experiences or only one specific test
Review whether the current page mode is appropriate for the page structure
What to share when raising a support request
To help distinguish between a blocked tag, a timeout, and a test-level problem, it is useful to provide:
The affected page URL
The exact bookmarklet message shown
Whether the issue persists after a full page reload
Whether the issue affects all users or only specific environments
Any console or debug errors observed
Whether the behaviour affects one experience or Optimize more broadly
In most cases, the bookmarklet message is enough to identify the right investigation path quickly. Optimize is not active usually points to tag availability, Optimize has aborted usually points to an unhandled error, Timeout exceeded usually points to readiness timing, and Default context usually points to incomplete or interrupted execution.