Setup together
Install the snippet, create goals, set up the first test, guided instead of alone with a manual.
?Support and documentation
The most common questions by topic. We answer the rest directly.
The direct route
For setup and analysis you get someone who built the product.
Install the snippet, create goals, set up the first test, guided instead of alone with a manual.
Not sure whether a result holds? Send the report link and we will look at it together.
Theme quirks, consent managers, revenue tracking, API and MCP, there is someone with access to the code for that.
Documentation
Each entry answers one question and says where the setting lives.
One script tag with your website ID goes into the <head> of every page. You find it under Website setup → Installation.
Before your first test it checks whether the snippet, the goals and the purchase events arrive.
Under Installation → First-party tracking you enter a subdomain, for example t.your-domain.com. The snippet then loads from there and is blocked less often.
Under Website setup → Environments. A test can be limited to one environment, and the preview counts nothing.
You change text, images and buttons by clicking in the editor. For logic like conditions or calculations, use JavaScript and CSS. Both work in the same variation.
As a redirect experiment: the variation redirects to a different path on the same website. The exposure is counted before the redirect and campaign parameters are carried over.
Yes, through reusable sections and asset management. Upload an image once and use it in several experiments.
Through a preview link that counts nothing. It expires after 24 hours, and there is a QR code for your phone.
Click, form, page view, custom event and revenue. Every test has one main goal, all others run alongside.
Create a revenue goal and call abdriven.track('Purchase', { value, currency, eventId }) on the order confirmation. The order number as eventId prevents double counting.
For metrics that must not get worse while you improve something else, returns, support requests, drop-offs. abdriven reports when a winner is doing damage elsewhere.
abdriven can pass the exposure to tools already on the page, such as GA4, Matomo or Hotjar. It does not install any tool.
The sample size planner uses your current conversion rate and the smallest difference you want to see. Progress shows next to the result later.
It shows how large the difference probably is. If zero is inside it, there is no result yet. With several variations abdriven corrects for that automatically.
It compares the planned with the actual distribution. If it is clearly off, do not use the result.
As a report link: read-only, no login, aggregated numbers only, with an expiry date and revocable at any time. For your own analysis there is also CSV export.
Yes. abdriven follows page changes in the app and removes variations that no longer fit. Hash routes such as #/page are not followed.
With data-consent="required" the snippet waits until your banner calls abdriven.consent(). If you load it only after consent, you do not need the attribute.
Through API tokens for your own scripts, webhooks and Slack for notifications, and the MCP server if AI agents should create experiments or summarise results.
Through the backup in the monitoring area. Keep the database outside the public directory, and automatic off-site copies are not built in yet.