Why don’t the Traffic & Conversion Summary totals match the Parent or Child product totals?

The Traffic & Conversion Summary report may not match the combined totals of the Parent or Child product reports for Page Views and Sessions. This is expected behavior and is due to how Amazon calculates these traffic metrics.

Unlike sales and units ordered, Page Views and Sessions are not additive across products.

There are two reasons for this:

The Summary includes traffic that isn’t tied to a specific product

The Traffic & Conversion Summary shows Amazon’s overall marketplace traffic for your account. It includes visits to pages that are not associated with a single ASIN, such as:

• Search results pages
• Browse and category pages
• Amazon Brand Storefronts
• Other marketplace pages

Because these visits cannot be attributed to an individual product, they are included in the Summary but do not appear in the Child product breakdown. As a result, the Summary total is often slightly higher than the combined Child totals.

Parent-level metrics are deduplicated

The Parent view applies additional deduplication.

If a shopper views multiple child variations of the same parent product (for example, different sizes or colours) during a single visit, Amazon counts that visit only once at the Parent level instead of once for each Child variation.

This means the Parent totals for Page Views and Sessions will typically be lower than the combined Child totals.

These differences are expected and reflect how Amazon calculates traffic metrics. MerchantSpring displays the data exactly as provided by Amazon, so variations between the Summary, Parent, and Child views do not indicate missing or incorrect data.