Product Release Jul 2026 · PTC, DiD & Engine 9.2

July 2026 Release: Profit Target Calibration (PTC), Causal DiD Impact Evaluation & Cluster Homogeneity

Coordinated ROAS bidding via Profit Target Calibration (PTC), 180-day causal DiD clusterization evaluation, zero-order SKU stability, and fast setup.

Direct Answer · Key Summary

June and July 2026 launch Profit Target Calibration (PTC) for cross-group ROAS alignment alongside 180-day Difference-in-Differences (DiD) clusterization evaluation. Predictive Engine 9.2 supports up to 12 campaign groups with calm zero-order SKU scoring and sub-second portal creation.

What shipped in this release
  • Profit Target Calibration (PTC) aligns ROAS goals across productive clusters while respecting break-even floors.
  • Difference-in-Differences (DiD) clusterization evaluator uses 180 days of history with seasonal adjustment and MDE.
  • Engine 9.0 & 9.2: supports up to 12 cluster campaigns, calm scoring on zero-order SKUs, and post-move locks.
  • Sub-second clusterization creation via API (677 ms), 5-step Production Go-Live checklist, and automatic Merchant Center XML export.
Karsa.ai Portal View Click to inspect ⤢
Karsa.ai Portal bidding view showing coordinated cluster Target ROAS settings and campaign metrics
Targets & Budgets in Karsa.ai Portal: coordinated cluster ROAS hierarchy and spend-limit diagnostics.
Methodology Infographic · Jul 2026 Release Cluster Homogeneity Engine, Coordinated PTC & Causal DiD Evaluation
Cluster homogeneity engine for up to 12 campaigns and Difference-in-Differences causal impact evaluation ENGINE 9.0 & 9.2 · CLUSTER HOMOGENEITY Stable Predictions Including Zero-Order SKUs C0 opt Cluster C1 Cluster C2 Cluster C3 Top Cluster Up to 12 Campaigns (active clusters + optional C0) Productive ROAS hierarchy (C2+) + GMC XML export CREATION ENDPOINT SPEEDUP 177× faster 120 s → 677 ms Sub-second creation API + calm zero-order SKU scoring CAUSAL IMPACT EVALUATION (DiD + MDE) Separates Net Lift from Market Seasonality Go-live marker Control baseline Net DiD Lift • 180-day pre-launch baseline + Minimum Detectable Effect • Non-Karsa control traffic removes seasonal swings • PTC aligns productive Target ROAS (C2 upward) • 5-step Production Go-Live checklist
Homogeneity Engine: Up to 12 campaigns (active clusters + optional C0) · 177× faster API creation
Causal DiD Evaluation: Separates net lift from market seasonality over a 180-day baseline

1. Predictive Engine 9.0 & 9.2: cluster homogeneity and up to 12 campaigns

During June and July 2026 we shipped Predictive Engine 9.0 followed by 9.2, focused on internal cluster homogeneity and scalable campaign structures:

  • Up to 12 campaigns: Supports larger multi-category stores across active clusters plus optional C0 when conversion volume justifies finer splits.
  • Calm zero-order SKU scoring: Sparse and no-sale items remain steady across nightly runs without random flips, backed by post-move locks.
  • Sub-second API creation: Backend optimization cut the clusterization setup endpoint from 120s down to 677ms (177× faster).

2. Profit Target Calibration (PTC) with productive ROAS hierarchy

Segmentation only delivers its full return when each campaign carries an appropriate Target ROAS. Profit Target Calibration (PTC) brings structured statistical support to bidding decisions:

  1. Coordinated hierarchy: Keeps Target ROAS ordered across productive clusters (C2 up to the top group) while respecting entry C1 and optional C0 roles.
  2. Pre-computed edit verification: Evaluates target adjustments across a two-month baseline and two-week follow-up window (omitting incomplete recent dates) alongside Approve / Reject controls.
  3. Go-Live checklist & automatic XML export: Switching a clusterization to Production opens a five-item readiness warning and generates your hosted Google Merchant Center supplemental feed.

3. Causal Difference-in-Differences (DiD) clusterization evaluation

To give finance leads and PPC directors statistical proof rather than raw before-and-after snapshots, July expanded the Difference-in-Differences (DiD) Impact Evaluator:

  • Uses 180 days of prior history with Minimum Detectable Effect (MDE) confidence bands and post-launch learning exclusion.
  • Adjusts against control campaign traffic so stores measure net segmentation lift accurately across seasonal demand swings.

Frequently asked questions

Why should Target ROAS be coordinated across productive clusters instead of edited in isolation?

Productive clusters from C2 upward form an ordered bidding hierarchy, while entry group C1 and optional C0 stay exempt. PTC evaluates the full setup together so productive targets keep logical spacing above break-even.

How does Karsa.ai measure net clusterization lift when market demand rises or falls seasonally?

Raw before-and-after totals confuse seasonal peaks with software lift. Karsa.ai's Difference-in-Differences (DiD) clusterization evaluator uses 180 days of history, non-Karsa control traffic, and Minimum Detectable Effect (MDE) bands to isolate net impact.

Start a 30-day free trial of Karsa.ai with your own product feed.

Connect your product XML feed and read-only Google Ads access, review your clusters in the Karsa.ai Portal, and run live for 30 days.

Try for free Book a demo
30-day free trial · Merchant Center supplemental feed (custom_label) · 0% commission on ad spend