Eva Product ID: How Cross-channel Product Matching Works
Eva Product ID: How cross-channel product matching works
Overview
Eva Product ID is the unified product layer that allows EVA to combine data from different sales channels into a single, analyzable entity.
Instead of treating Amazon and Shopify products as separate items, EVA links them under one shared identity. This enables you to track performance, profitability, and trends across channels without manually merging data.
This system is what makes cross-channel product analysis possible in Analytics.
What is Eva Product ID
Eva Product ID is a system-generated identifier that represents a single product across multiple sales channels.
A single Eva Product ID can include:
- an Amazon listing (ASIN-based structure)
- a Shopify product or variant (SKU-based structure)
Once linked, these separate channel entries are treated as one product in Analytics.
This allows EVA to:
- combine performance metrics
- calculate unified totals
- present a single product view
The Logic Behind Product Matching
Product matching does not happen automatically at the Analytics level.
It is created and managed in the Catalog, where products from different channels are connected.
The process works as follows:
- Amazon products (ASIN-based) and Shopify products (variant-based) exist as separate datasets
- In the Catalog, these products are mapped together
- EVA assigns a shared Eva Product ID to the matched entries
- Analytics reads from this unified layer instead of raw channel data
This means Analytics does not “merge” products dynamically.
It simply reflects the structure already defined in the Catalog.
When products are combined
Matched products are only combined under specific conditions.
Multiple channels must be selected
Eva Product ID is only applied when more than one channel is included in the analysis.
- If both Amazon and Shopify are selected → products appear unified
- If only one channel is selected → products appear separately
Products must be mapped in the Catalog
If a product has not been matched:
- it will not have a shared Eva Product ID
- it will appear as separate entries even if it represents the same item
Why this only works in Trends Overview
Not all Analytics views operate on the same data structure.
Trends Overview is designed to:
- work at the product level
- use the unified product dataset
- display combined metrics across channels
Other views:
- may operate at summary or campaign level
- do not use the same unified product structure
Because of this, cross-channel product matching is only visible in Trends Overview.
What changes when products are matched
When products are linked under a single Eva Product ID:
- performance metrics (e.g. sales, profit, sessions) are combined across channels
- trends reflect the total behavior of the product
- comparisons are made at the product level, not per channel
This removes the need to:
- manually compare Amazon vs Shopify results
- calculate totals across different systems
What happens when products are not matched
If products are not mapped in the Catalog:
- each channel entry remains separate
- no Eva Product ID is assigned
- performance is fragmented across multiple rows
This can lead to:
- duplicate-looking products
- incomplete performance evaluation
- misleading comparisons
Key Value of Eva Product ID
Eva Product ID enables:
- Unified performance tracking Analyze a product’s total impact across all connected channels
- Accurate profitability analysis Combine revenue and cost data into a single product view
- Simplified reporting Eliminate the need for manual data merging
- Consistent product-level comparisons Compare products based on full performance, not partial data
Pro Insight
If a product exists in both Amazon and Shopify but appears as separate entries in Analytics, it means the products are not yet mapped in the Catalog.
Matching them correctly is what enables unified analysis.