> For the complete documentation index, see [llms.txt](https://docs.simola.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.simola.io/getting-started/quickstart.md).

# Introduction to Simola

Simola automates and tests web form submissions. It runs realistic browser simulations on your landing pages.

Use Simola for lead-gen forms, onboarding flows, and data collection. You catch blockers before users or campaigns are affected.

### How Simola works (at a high level)

1. You create a **campaign** for one landing page and one goal.
2. You configure how to find the form, fill fields, and submit.
3. You verify the page, run a test simulation, then activate.
4. You run volume using **simulation groups** (data + schedule).
5. Every scheduled record produces an **individual simulation** run.

### Why Simola

Modern forms have validations, scripts, popups, and anti-bot checks. These can silently break submissions. Simola tests the full flow end to end.

### What you can do with Simola

* **Validate real submissions, end to end.** Catch broken fields, missing mappings, blocked buttons, and wrong success pages.
* **Test your landing page under heavy load.** Run high-volume simulations to see if the page stays responsive and submissions keep succeeding.
* **Reproduce production-only failures.** Trigger edge cases like rate limits, bot checks, flaky third-party scripts, and timing-sensitive popups.

### Campaign goals: Form Testing vs Form Submission

Both goals submit your form in a real browser simulation. The difference is what you optimize for.

* **Form Testing**: validate and monitor the flow. It can enable extra controls like **traffic simulation** and **unique IP retention**.
  * Start: [Form Testing](/campaigns/campaign-creation/form-testing.md)
* **Form Submission**: run automated submissions at scale using your data and schedule.
  * Start: [Form Submission](/campaigns/campaign-creation/form-submission.md)

### Core concepts

* **Campaign**: the landing page, goal, field mapping, and automation.
  * Start here: [What is a Campaign?](/campaigns/what-is-a-campaign.md)
* **Simulation group**: data source + schedule + distribution. This is where you define volume.
  * Learn more: [What is Simulation Group?](/campaigns/what-is-simulation-group.md)
* **Individual simulation**: one run for one record, with a status and artifacts.
  * Learn more: [What is Simulation?](/campaigns/what-is-simulation.md)
  * How-to: [How to check simulation status?](/campaigns/how-to-check-simulation-status.md)

To do a quick sanity check, run a single [Test Simulation](/campaigns/integrations/test-simulation.md).\
To run volume on a schedule, create simulation groups for your campaign goal.

{% hint style="info" %}
Next: [Getting Started](/getting-started/getting-started.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.simola.io/getting-started/quickstart.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.