# Change Labelizer settings after setup

> Adjust a Labelizer project after setup when your target, account structure, feed filters or schedule changes.

You can adjust a [Labelizer](/docs/labelizer/labelizer) project after setup when your target, account
structure, feed filters or schedule changes.

Before changing settings, check the project you are editing and make sure it belongs to the
correct Google Ads account.

## Open project settings

Go to Labelizer and open the project you want to edit.

Project settings are a stepped flow: General, Configuration, Merchant Center, Advanced (optional
labeling settings), Preview (dry run) and Overview (status and activation). You can jump to any
step at any time. Changes are only stored when you click Save, and unsaved changes are discarded when you move to another step, so save before you leave a step.

## Settings you can review

Depending on the project setup, you may need to review:

- Target metric, such as ROAS or CPA.
- Target value. Target CPA, index margin and click multiplier support fractional values. Target
  ROAS is entered as a whole percentage.
- Date range.
- Conversion lag.
- Conversion actions.
- Merchant Center connection.
- Feed filters.
- Custom label slot.
- Schedule.
- Advanced settings: AOV segmentation and Group by item_group_id.

Several fields can be refreshed individually if the cached data is stale. Look for the refresh
button next to the Merchant Center account, data sources, feed labels, custom label slot (to reload
which slots are already in use), campaign feed labels, campaign countries and conversion actions.

Changing these settings can affect future runs and the buckets Labelizer produces.

## Be careful with account changes

A Labelizer project belongs to one Flowboost project, and through it, one Google Ads account.

If you need the same setup for a different Google Ads account, [create a separate Labelizer
project](/docs/labelizer/set-up-labelizer-for-the-first-time) for that project.

## Changing the schedule

If the project has a recurring schedule, update the schedule when you want Labelizer to run more
or less often. Scheduled runs only execute when the project is activated. Activate the project
from the Overview step before relying on scheduled runs.

You can also run Labelizer manually after making changes if you want to check the new output
before the next scheduled run.

## Changing feed filters

Feed filters decide which products are included. After changing filters, use the Preview step to
run a dry run and check the bucket output before saving or activating. A small filter change can
include or exclude many products.

## Changing the custom label slot

If Labelizer writes results back to Merchant Center, the custom label slot matters. Before
changing it, check whether the selected custom label is already used by another workflow, campaign
structure, feed rule or reporting process.

## Check project status in the Overview step

The Overview step shows the project status and a readiness summary for General,
Configuration and Merchant Center. Each section has a status indicator and an Open button to jump
directly to that area.

The status reflects whether the project is Active, Needs attention, Ready to activate or Setup
incomplete. If the project shows Needs attention, review the indicators in the Overview before
running again. The Overview also shows the next scheduled run time adjusted for the connected
Google Ads account's timezone.

## After you change settings

Run the project again and review the results.

Check whether:

- The expected products were included.
- The bucket distribution looks reasonable.
- The run finished successfully.
- Labels were synced if feed sync is enabled.

## Enable automatic AOV segments

Open **Advanced** and enable **AOV segmentation**. Keep one
custom-label slot selected. Run a preview and review the automatic weighted AOV boundary and the
low, high and unknown segments before syncing.

This mode combines AOV and performance into values such as `high-aov_over-index`. Prepare campaign
filters for those values first. Use purchase conversion actions with actual order revenue. Both
ROAS and CPA projects are supported and their existing performance targets remain in place.

See [How Labelizer decides each bucket](/docs/labelizer/how-labelizer-decides-each-bucket) for the
calculation and the treatment of products without purchase history.

## Group variants by item_group_id

Open **Advanced** and enable **Group by item_group_id** when your feed uses `item_group_id` for
variants such as sizes or colours. Labelizer then adds up the performance of all variants in a
group and gives every variant the same bucket. Products without an `item_group_id` keep their own
bucket.

Grouping reads item groups from Merchant Center, so connect Merchant Center and select the catalog
feeds first. The preview still labels each variant on its own, so check the result after the next
real run. See
[How Labelizer decides each bucket](/docs/labelizer/how-labelizer-decides-each-bucket#optional-grouping-by-itemgroupid)
for details.