Configure Website Settings
Overview
Your website has two separate settings areas in Explore: Edit Website and Website Tracking Settings. This article covers both, since they're often confused with each other.
Edit Website page
Access this by clicking your active website name in the header and selecting Edit Website.
Display Timezone
Sets the timezone used when displaying dates and times throughout the platform, including the timestamps in the downloaded csv report.
This setting now also affects experiment scheduling. If you set an experiment to start on a day in the future, that start date is interpreted using your selected Display Timezone - not the server's default timezone. Double-check this setting before scheduling experiments with a specific start or end date in mind.
Website Consumption Limit Control
Lets you set a traffic limit for this specific website, measured in Tested Visitors (see What is Omniconvert Explore? for the definition).
This is useful when you manage multiple websites on a single Explore account. For example, if your plan includes a total of 200,000 Tested Visitors across your account, and you have 5 different websites, you can divide that limit between them - allocating more to your highest-priority sites and less to others - rather than letting one website consume the entire account limit.
Visitor Exclusion Rules
Found under Exclude visitors from experiments on the Edit Website page. Lets you add rules based on IP, Cookie, Header, Country, or Custom Code to exclude specific visitors from seeing any live experiment.
For each rule, set:
-
Type - the condition to match against: IP, Cookie, Header, Country, or Custom Code.
-
Operator - how the value should be matched (e.g. "is (equal)").
-
Value - the specific value to match.
Press the trash icon to remove a rule, or Save to apply your changes. Each saved rule appears in the list, and you can add multiple rules.
If a visitor matches an exclusion rule, the tracking code does not run for them at all - not just the experiments, but tracking itself. This is different from segmentation, which controls which visitors see a specific experiment while still tracking them normally.
Base Currency
The currency all Sale Goal transactions are converted into for reporting, relevant for Multi-Currency Support. Changing this requires contacting Omniconvert support.
Webhooks
Found under Website Settings → Webhooks (a separate tab from General settings). This sets a website-wide webhook that fires for status changes on any experiment on this website.
When any experiment on this website is activated, paused, or expires, Explore sends a POST request describing the change to the URL you set here.
Leave the field empty to disable this website-wide webhook. Requests are queued, so they arrive shortly after the change rather than instantly.
Press Save once you've entered your webhook URL.
All timestamps in the payload are in UTC.
Website Tracking Settings page
Access this by clicking your active website name in the header and selecting Tracking Code, then finding the tracking settings section.
Loading Tolerance
A safety mechanism built into the tracking code itself - separate from any individual experiment. If your website's connection is too slow, the tracking code "fails safe" and stops entirely for that page load: no experiment changes are applied, and no data (pageviews, goals, conversions) is recorded at all.
A higher Loading Tolerance means the tracking code waits longer before giving up. The minimum value is 1000ms (1 second).
Because this affects the tracking code broadly, a slow-loading page can silently suppress data across every active experiment on that page - not just one. If you notice missing conversions or lower-than-expected traffic in your reports, a low Loading Tolerance combined with a slow website is a common cause. See Differences Between Omniconvert & Analytics Tools for more on this.
Collect Location Data
Controls whether the tracking code saves location data (city, region, country) alongside events like pageviews, goals, survey answers, and leads. This data becomes visible in downloaded conversion and lead lists.
Allowed Origins
An extra security measure that restricts which domains tracking events can be sent from, preventing faked or unauthorized submissions. The default value is * (any domain). We recommend specifying your actual domain(s) instead. Wildcard subdomains are supported, e.g. https://*.example.com.
This is enforced by the browser using CORS - Explore doesn't do anything special beyond setting this value.
Press Update Settings once you've made your changes.