Movement Limits

One of the key advantages of Karsa Labelizer is the ability to dynamically adjust the placement of products into clusters based on their current performance. This means that if a product's performance changes in such a way that it better matches the characteristics of another cluster, the system can automatically move it. However, to prevent these movements from leading to undesirable destabilization of your campaigns and disrupting the learning process of Google algorithms, Karsa Labelizer offers detailed settings of limits for these operations.

Enabling Product Movements

First, it is necessary to decide whether you want to allow automatic product movements for the given clusterization at all.

1. Allow moving products when updating

• What it is: A basic switch that enables or disables automatic product movements between clusters when Karsa Labelizer updates data daily and recalculates optimal placement.

• Recommendations:

  • Enabled (Yes): In most cases, it is desirable to have this option active so that your segmentation is continuously optimized and reflects current performance.

  • Disabled (No): Consider temporarily disabling movements in the following situations:

    • During the initial learning phase of Google Ads: When you deploy a completely new campaign structure to Google Ads, it is advisable to let Google algorithms "learn" for about 1-3 weeks without further major changes in the structure. During this time, products may not yet have established actual performance metrics, and movements could be premature.

    • During major external changes: For example, during short-term massive sales or other events that may temporarily distort product performance.

    • For diagnostic purposes: If you want to analyze the performance of a "frozen" structure.

Setting Limits for Product Movement

If movements are allowed, the following limits will help you control their intensity and prevent sudden, extensive changes that could negatively affect the optimization of Google campaigns.

1. Each cluster can lose at most % of products

• What it is: Defines the maximum percentage of products (out of the total number of products in a given cluster) that can be removed from this cluster (moved elsewhere) during one update cycle (usually daily).

• Example: If you set 10% and the cluster has 100 products, a maximum of 10 products can be moved away from it on a given day.

• Importance: Prevents massive "outflow" of products from one cluster at once.

2. Each cluster can gain at most % of products

• What it is: Defines the maximum percentage of products (relative to the original number of products in a given cluster) that can be added to this cluster (moved from other clusters) during one update cycle.

• Example: If you set 15% and the cluster originally had 100 products, a maximum of 15 new products can be moved into it on a given day.

• Importance: Prevents sudden massive "inflow" of products into one cluster, which could also affect its characteristics and behavior.

3. Waiting days before moving product again

• What it is: The minimum number of days that must elapse since the last movement of a product before this specific product can be moved to another cluster again.

• Example: If you set 7 days, a product that was moved today cannot be moved again for the next 7 days, even if its performance would suggest suitability for another cluster. It must first "settle" and demonstrate performance in the new cluster.

• Importance: Prevents constant "pouring" of products between clusters, gives products time to acclimatize and collect relevant data in the new environment.

4. Limit (in percent) how much can be stabilization value changed

• What it is: The maximum allowed percentage change of the so-called stabilization value for each cluster during one update cycle.

• Stabilization value: This is a metric that represents the total conversion value, number of products, or another parameter chosen by you or determined by the system. Products are moved between clusters so that this defined stabilization value of each cluster changes only as much as this percentage limit allows.

• Example: If the stabilization value is the total conversion value of the cluster and the limit is set to 5%, then product movements (outgoing and incoming) must not cause a change in the total conversion value of this cluster by more than +/- 5% during one update.

• Importance: This is a very powerful tool for maintaining the overall characteristic and performance level of the cluster over time, even though individual products may change. It ensures smooth transitions and protects against abrupt changes that could confuse Google algorithms.

---

By carefully setting these parameters for allowing and limiting product movements, you ensure that your clusterization will not only dynamically respond to changes in performance but also maintain the necessary stability for long-term effective functioning of your Google Ads campaigns. In the next section, we will focus on New Products Strategy.