> ## Documentation Index
> Fetch the complete documentation index at: https://epsilo.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Quick start for operators
> Get oriented with the Epsilo 3.0 workspace, workflows, tables, and the four stages you operate in before you optimize a single campaign.
You are running paid ads across many storefronts, each marketplace locked in its own ad manager. Epsilo 3.0 puts them in one close-loop workspace: it sits on top of Seller Center and your retail media networks, syncs performance in, and pushes actions out, so you run every storefront, campaign, and automation from one place. This guide orients you before you start.
## Prerequisites
Before you begin, confirm you have:
* **Workspace access**: You can log in and see your team's workspace
* **Storefront access**: Your assigned storefronts appear in the storefront section
Missing either? Contact [support@epsilo.io](mailto:support@epsilo.io).
***
## How Epsilo connects to your platforms
Epsilo layers on top of Seller Center and retail media networks through two processes:
* **Data sync**: Epsilo pulls performance, campaign settings, products, and placements on a short interval. Most tables refresh every few minutes, so data is near real-time.
* **Action execution**: Changes you make in Epsilo push to the network via API in near real-time.
Make changes in Epsilo, not in the network's ad manager in parallel. Simultaneous edits in both places conflict.
***
## The workspace you land in
Epsilo 3.0 is a close-loop layout: the list and the detail sit side by side, the numbers that matter stay pinned in front of you, and your critical campaigns are one click away.
| Surface | What it does |
| - | - |
| **Split-panel layout** | Select a campaign on the left, its full detail opens on the right. No new tab, no lost place in the list. |
| **Today performance bar** | Spend, GMV, ROAS, and Live time pinned at the top of every screen. |
| **Quick-filter chips** | Suggested budget, Low live time, Under-spend, Health. One click isolates what needs attention. |
| **Watch list** | Pin any campaign to the rail; it stays across pages and sessions. |
| **Icon rail and Sidepeek** | The left sidebar collapses to an icon rail; any record opens in a side panel without leaving your view. |
| **Command palette** | [Cmd K](/docs/console/command-palette) is a global launcher to jump anywhere or act, from anywhere. |
***
## Organize your work into workflows
A **workflow** is a saved page that holds the views and tables you use daily, pinned in the left rail so you reopen your working setup in one click instead of rebuilding it each morning.
* **Create one**: right-click a section in the left rail, choose **Set workflow**, then **Private** or **Shared**.
* **Private workflow**: visible only to you.
* **Shared workflow**: visible to everyone in your workspace, so the team operates from the same setup.
* **Edit the layout**: open the page editor to drag tables and views into a grid, then rename or reorder the workflow from its context menu.
Workflows are how you personalize the workspace around a job: a daily-check workflow, a mega-sale workflow, a single-brand workflow. Save a configured table as a [view](/docs/tables/view-modes-and-saved-views), then drop that view into the workflow that needs it.
***
## Working in tables
Tables are the main working surface in Epsilo. Each table shows a live dataset (campaigns, ad objects, placements, or keywords) with metrics, attributes, and actions per row.
### Table configuration
Every table has controls at the top:
| Control | What it does |
| - | - |
| **Time period** | Sets the date range for performance metrics. Use "Advance custom" for non-consecutive ranges. |
| **Filter** | Applies one or more conditions to narrow the rows shown. Filters can use AND/OR logic. |
| **Sort** | Orders rows by one or more columns, ascending or descending. |
| **View by** | Changes the aggregation dimension on supported tables (for example, GMV by day, week, or month). |
| **Cohort** | Sets a comparison period. Performance values show as subtext so you can compare against a prior period. |
**Properties** (the rightmost kebab menu) controls which columns are visible. Columns are categorized as:
* **Dimensions**: fixed identifiers like storefront name, SKU name, company
* **Attributes**: current-state values not tied to a time period, like campaign status or daily budget
* **Metrics**: performance and calculated values like ad spend, ROAS, and GMV
### Taking action
Click the **kebab menu (⋮)** on any cell to edit or execute an action on that row.
For changes at scale, there are two approaches:
* **Bulk action**: select specific rows manually, then act on only those rows. Tables load 10 rows at a time; "Select all" selects only the currently loaded rows.
* **Mass action**: click the kebab menu on a **column header** to act on every row in your filtered dataset, including rows not yet loaded. Use this for large-scale updates like changing bids across thousands of keywords.
See [bulk and mass actions](/docs/tables/mass-bulk-action) for the full model, with rollback safety on mass edits.
### Saving views
Once you have configured a table, save it as a **view**. Views store your filters, sort order, and column selection. Each user's views are private by default, so your changes do not affect teammates. To use a teammate's view, clone it from their view list. Drop your saved views into a [workflow](#organize-your-work-into-workflows) to assemble your working page.
***
## Campaign structure
Epsilo uses a consistent three-level hierarchy across every platform. Open one campaign in the split panel and every layer is one view away.
### Campaign level
The top-level container, matched one-to-one with an ad tool (for example, Shopee • Product Ads, Lazada • Sponsored Discovery, TikTok Shop • GMV Max). Groups your ad objects under a shared purpose.
Managed here: daily budget, campaign status, timeline, campaign objective (where applicable).
### Ad object level
The product or SKU being advertised. Each ad object sits inside a campaign.
Managed here: ad object budget, status, timeline, ROAS target (for GMV Max), ad object bidding.
### Ad placement level
The specific location where an ad runs: a keyword, a discovery slot, or an automated placement. Each placement sits inside an ad object.
Managed here: bidding price, placement status.
See [campaigns and ad objects](/docs/concepts/campaigns-and-ad-objects) for the full model across networks.
***
## Operate in four stages
Everything you do in Epsilo maps to one of four stages. The docs and the in-app onboarding follow the same order.
Connect ad networks and storefronts, invite your team with the right access, and label your catalog with asset tags.
Build a campaign for any ad tool from one create form, then operate every layer inline in campaign detail.
Apply suggested budgets, schedule changes, distribute budget across the portfolio, and run scripts that act while you sleep.
Know which storefronts make money and which bleed: missed GMV, ad live time, coverage, and competition.
### Automate while you sleep
Stage 3 is where hand-tuning becomes a system. Three tools, from simplest to most powerful:
* **Scheduling**: set any attribute (status, budget, bid, target ROAS) to change automatically at a specific date and time. Use it for campaign-day ramp-ups and post-sale wind-downs. Start with [schedule budget](/docs/scheduling/schedule-budget).
* **Budget distribution**: dynamically reallocate daily budget across ad objects in a campaign by performance, using a ROAS-based, GMV-based, or custom model. Set it up when your campaign structure is stable. See [distribution models](/docs/budget-distribution/distribution-models).
* **Scripts**: rule-based automations that watch performance and act when conditions are met, updating bids, budgets, and status continuously without manual review. See [scripts](/docs/scripts/scripts).
### Console over all of it
[Console](/docs/console/ask-botep) runs across every stage. Ask it a question in plain language from anywhere, then turn any answer into a [Live artifact](/docs/console/live-artifacts) you refine, present, and share. Console reads the same live data you see in the workspace, so every answer is an action you can take.
***
## Common questions
A view is one saved table configuration (filters, sort, columns). A workflow is a saved page that holds several views and tables together. Save the table as a view, then drop that view into the workflow you open for the job.
No. Filters, sorting, and column selections save to your personal view. Teammates can clone your view, but your real-time changes stay invisible to them until you share a workflow.
Tables sync on a short interval, so brief discrepancies during a refresh cycle are normal. Actions you take in Epsilo push through in near real-time regardless.
Mass edits carry rollback safety. For other changes there is no automatic undo, but everything is logged. Open the kebab menu on any attribute to see its change history, or trace every change in the [history log](/docs/tables/history-logs).
Bulk actions apply only to the rows you manually selected (limited to loaded rows). Mass actions apply to every row in your filtered dataset, including rows not yet loaded. Use bulk for small targeted edits; use mass for large-scale updates.
***
## Next steps
* Assemble your working setup with [views and saved views](/docs/tables/view-modes-and-saved-views)
* Connect your first network in [connect ad networks](/docs/concepts/connect-ad-networks)
* Automate spend allocation with [budget distribution](/docs/budget-distribution/distribution-models)
* Explore [scheduling](/docs/scheduling/schedule-budget) and [scripts](/docs/scripts/scripts) for ongoing automation
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.