🎁 : All Benchmark metrics (NC CPA today, and every metric we add next) are for every merchant on Attribuly — no paid plan required.

| | Your NC CPA vs peer P50, with a gradient bar showing Top 25% / Middle 50% / Bottom 25% ranges. One glance tells you if you're competitive. |

| (click ) | 6 metric cards (NC CPA, CPA, CPC, ROAS, CVR, MER) side-by-side, plus Google / Meta / TikTok / Bing per-channel breakdowns. |

| | Upcoming evidence rows will surface NC CPA benchmarks when we flag your spend structure (e.g. "Your Brand Search NC CPA is 36% below peer median — this is a well-tuned budget.") |

This is just the beginning. Over the next 8 weeks we're shipping these — on the house:

| | | Today |

| (total conversions) | | Next 2 weeks |

| | | Next 2 weeks |

| | | Month 2 |

| (Conversion Rate) | | Month 2 |

| (Marketing Efficiency Ratio) | | Month 3 |

| 🤫 | Ask us in-app! Feedback from merchants shapes this column. | Month 3 |

> 🔒 Every benchmark number is aggregated and anonymized — other merchants never see your store, and you never see theirs. It's a one-way mirror: everyone gets the market-level truth, nobody gets anyone's private numbers.

Integration setup: Go to and select MambaSMS to set up the integration.

For destination configuration, navigate to .

We are improving Shopify Shop attribution so that orders and visits from the Shop app can be identified more consistently in attribution paths.

Previously, Shopify Shop events were mainly added during order backfill. This could miss some cases, such as orders that already had tracking events or orders that matched other visits during backfill.

During attribution path cleaning, we will check each order's .

If , a event will be added to the order's attribution path.

When a visit URL contains , the visit will be recognized as .

This rule will not apply if is from the same website.

With this update, Shopify Shop can be identified from both the order channel and visit UTM signals.

## What Is New

You can now build customer segments based on each customer's total order amount.

In , the section now includes a new property:

This condition uses the customer's lifetime total order amount from Shop customer data. It helps you create more precise customer groups based on purchase value, such as high-value customers, low-spend customers, or customers who have not reached a target purchase threshold yet.

## How To Use It

-

-

-

-

## Example Use Cases

### High-Value Customers

Create a segment for customers whose total order amount is greater than 500.

Example:

This segment can be used to identify loyal or high-value customers for VIP campaigns, retention programs, or exclusive offers.

### Customers Below A Purchase Threshold

Create a segment for customers whose total order amount is less than 100.

Example:

`Customer's property: Total spent Condition: is less than Value: 100

`

This segment can help you find customers who have purchased but have not yet reached a meaningful spending level.

### Exact Spend Matching

Create a segment for customers whose total order amount equals a specific value.

Example:

This can help you identify customers with no recorded spending in Shop customer data.

## Currency Display

The amount input displays the store's currency symbol automatically.

For example:

The currency symbol is shown to make the input easier to understand. The segment condition itself is saved as a numeric amount, so the filtering logic remains consistent with the store's Shop customer data.

## What Problem This Solves

Before this update, customer segments could be built from customer attributes and behavior events, but there was no simple way to filter customers by their total order amount.

With this update, merchants can:

## Data Source

This condition is calculated from Shop customer data.

The filtering logic uses:

This means the segment is based on the total amount recorded for each Shop customer.

## Notes

We’ve added a new metric, , to help you better understand how efficiently ad clicks turn into conversions.

is calculated as:

Previously, clicks and conversions were available as separate metrics, but it was harder to quickly evaluate how effectively clicks were turning into conversions. This new metric makes it easier to compare performance across campaigns, ad sets, ads, and other attribution breakdowns.

You can view in both and reports. Open either report and check the column in the data table. If the column is not visible, update your table column settings to include .

Previously, Ads Attribution only showed one date range at a time, so users had to manually switch dates or export reports to compare performance. With date comparison, users can now evaluate performance changes directly in the report and identify what changed between two periods.

You can now use in the Ads Attribution date picker, just like in All Attribution. This lets you compare your current reporting period against a previous period, previous year, or a custom date range directly inside the Ads Attribution report.

: Recapture page data supports Omnisend data display.

Unified Omnisend recovery view: A single view of how Recapture contributes to Omnisend recovery, including revenue, events, and key workflow impact.

Event diagnostics: Gives a quick view of which events are enabled for Omnisend recovery workflows, event‑level revenue contribution, and trend and performance of each event. So you can quickly identify where recovery coverage is strong — and where workflow impact is underperforming.

: Please reconnect your Omnisend integration on the Sources page to enable this capability.

: Recapture page data supports Cartsee data display.

Unified Cartsee recovery view: A single view of how Recapture contributes to Cartsee recovery, including revenue, events, and key workflow impact.

Event diagnostics: Gives a quick view of which events are enabled for Cartsee recovery workflows, event‑level revenue contribution, and trend and performance of each event. So you can quickly identify where recovery coverage is strong — and where workflow impact is underperforming.

: Please reconnect your Cartsee integration on the Sources page to enable this capability.

You can now push your Attribuly‑built audience segments to Omnisend via

Connections > Destinations.

After enabling the destination, Attribuly will keep segment members synchronized to Omnisend.

Existing Omnisend integrations require re‑authorization to unlock this new segment sync capability.