Project Settings
Edit each project's name, URL, setup guide, timezone, and analytics forwarding from a single page.
Project Settings
Each project has its own name, URL, install guide, timezone override, and analytics-forwarding toggles. Edit them from the project page when something changes — owners and admins can; members and viewers can't.
Open the project from your dashboard and click Edit to reach the settings page. The header reads Edit Project; the form has a single Save button at the bottom and the changes apply immediately. The Edit button is only visible to owners and admins.
Editable fields
Platform
Read-only after creation. The underlying runtime — Custom JS or Shopify. To switch runtimes, create a new project for the new platform.
Setup guide
Choose which installation walkthrough is displayed for this project (e.g. Webflow, WordPress, Wix for Custom JS). The runtime stays the same; only the install instructions change.
Project name
Friendly name shown across the dashboard. Change anytime; this does not affect the snippet or test history.
Project URL
Used for snippet verification (so we know which domain to look at) and as the default base URL when building tests in the wizard.
Reporting timezone override
Optional. Sets the day boundary for reports on this project. Leave blank to inherit the account's default reporting timezone.
Analytics forwarding
Toggle Google Analytics 4 or Google Tag Manager on to forward Otter A/B events into your existing analytics stack. Each event carries the test ID and name, the assigned variant's ID and name, and (for conversions and revenue) the goal name and type so you can join or segment on either side.
Google Analytics 4 (via gtag)
experiment_impressionA visitor is assigned a variant.otterab_conversionA visitor converts on any goal.otterab_revenueA visitor converts on a revenue goal (carries the value).
Google Tag Manager (via window.dataLayer)
otterab_experiment_impressionA visitor is assigned a variant.otterab_conversionA visitor converts on any goal.otterab_revenueA visitor converts on a revenue goal (carries the value).
Two GA4 directions, not one
The GA4 toggle on this page forwards Otter A/B events into GA4. The separate GA4 Integration article covers the other direction: pulling existing GA4 events out of your property to use as goals on Otter A/B tests. They're independent — turn on either, both, or neither depending on what you need.
What to set, and when
Set the timezone override only when you really need it. If your account reporting timezone matches the project, leave the override blank. Mixed timezones across projects can make cross-project comparisons confusing.
Turn on forwarding if your team lives in GA4. If your stakeholders monitor performance from a GA4 dashboard, forwarding test impressions and conversions gives them context for what they're seeing — without making them log into a second tool.
Don't change platform — make a new project instead. Switching runtimes mid-flight breaks history and snippet semantics. A new project is a few clicks and keeps the old data intact.
Frequently asked questions
Quick answers to the questions teams ask most about this part of Otter A/B.