After a Labelizer project is configured, you can run it manually or let it run on a schedule. Each run reads the selected account data, calculates product buckets, and stores the results in the project.
Live runs that sync labels to Merchant Center require a Core subscription. Without one, a subscription dialog appears when you click Run, and you can choose to run a preview instead. A preview run calculates results but does not write any labels.
Run Labelizer manually
Open Labelizer and find the project you want to run. Click Run.
If the button is disabled, check whether:
The project is active.
The workspace has a Core subscription for live runs.
The project settings are complete.
A run is already in progress.
Watch run progress
When a run starts, Flowboost shows the latest status in the project list and run timeline.
You can also open the Status updates dialog for a detailed breakdown. It shows a table of run steps, each with a status, timestamp, and message. The steps are: Queued, Labelizer run, Merchant Center enrichment, and Merchant Center push.
Runs may take longer for large accounts or large product feeds.
Review bucket results
After a successful run, open the project to review the bucket distribution.
Labelizer groups products into buckets such as:
Over-index.
Index.
Near-index.
Under-index.
No index.
You can also open the View graphs page to see a donut chart and a per-bucket breakdown. The bucket distribution is also visible directly on the project list.
Use these buckets to decide which products deserve more budget, less budget, or more data before making changes.
Preview runs (analysis-only) never sync labels to Merchant Center. If a run was started from the subscription dialog, it is a preview run regardless of other settings.
Schedule future runs
Open project settings to enable scheduled runs. Choose the frequency, time, and day that fits your workflow.
Scheduled runs only execute when the project is activated. If the project is not yet active, scheduled runs will not start.
If a run fails
Check the run status and project settings.
Common causes include:
The selected Google Ads account is no longer available.
Conversion actions could not be loaded.
Feed access is missing.
The project is not fully configured.
After fixing the issue, run the project again.



