Skip to main content
The weekly performance report is an email Layers sends every Monday at 12:00 PM Eastern Time. It gives you a quick read on how search, merchandising, and discovery performed on your storefront over the past 7 days, without needing to open the dashboard. Use this email when you want a passive, at-a-glance recap of the previous week. It covers the kind of view you might otherwise open Analytics dashboards or Insights to check.

Prerequisites

  • Your store must be connected to Layers and past onboarding. See Install if you have just installed Layers.
  • Your email address must be verified, and your role on the store must include permission to view analytics. See Manage roles and permissions.
  • Forward storefront events to the Beacon API so the report has search activity to summarize.

When you receive the email

Layers sends the report once a week, on Mondays at 12:00 PM ET, covering the prior ISO week (Monday through Sunday). You will not receive an email for a given week if any of the following are true:
  • Your store had no search activity in the last 7 days.
  • The store is flagged as a development store.
  • You have not verified your email address.
  • Your role on the store does not include permission to view analytics.
  • You have opted out of the Weekly reports email topic.
These conditions apply per user. If you opt out or have an unverified email, other eligible users on the store still receive the report. If a week is skipped, Layers resumes automatically the next Monday if the store becomes eligible again.

What the email contains

Each report is scoped to a single store and summarizes the last 7 days. It includes:
  • Headline metrics for the week, with a comparison against the prior week.
  • Highlights of the top-performing searches, collections, and recommendation blocks.
  • Notable changes that warrant a closer look in the dashboard.

Insight sections

Use these sections to decide what to review next. You only see a section when there are relevant findings to show.
  • Opportunities: Growing demand, sales spikes, and products you could make easier for shoppers to find. A sales spike is an opportunity, not a problem just because sales changed sharply.
  • Needs attention: Active problems and merchandising fixes worth reviewing, such as a storefront block receiving no requests or a search whose results shoppers ignore.
  • Setup notes: Lower-priority configuration checks, such as unused audiences or merchandising rules ready for review. You see at most two setup notes, and they never become the report’s priority highlight.
  • What Layers did for you: Automatic ranking and curation changes. Use Test Text Search to review demoted products for incorrect tags.

Badge colors

Each insight has a badge with a plain-language label. Read its color as a guide to what you should do, rather than treating every unusual change as a warning:
  • Red: An active problem affecting your store, such as a storefront block receiving no requests or a sharp drop in search engagement.
  • Amber: A fix to review, such as low search engagement or a sales window that may not fit your collection’s sort.
  • Green: An opportunity, such as a sales spike or growing search demand.
  • Gray: A setup note or an automatic curation update, not an urgent problem.

Take the next step

Each insight gives you a specific next step and two links:
  • Open in Layers opens the relevant product, rule, search, or dashboard page. If the only action is to check an installation, this link opens the installation guide instead.
  • Learn more opens the documentation for that kind of finding.
For example, a sales spike can suggest moving a product higher in its collections while demand is up. A rule ready for review asks you to confirm that it still matches your current merchandising. The description uses the latest detected figures so you can compare it with the value alongside it.

Rules off the default sort during a test

A setup note can tell you that merchandising rules use a different sort from their collection’s default. Those rules only apply when shoppers choose that sort, but the difference may be intentional during an A/B test. Layers skips affected rules when it can link them to a running Layers experiment. If you have a running ABConvert or Intelligems test, Layers keeps the note but names the test and explains that the setup may be intentional. The note has lower priority than other setup checks. Layers cannot confirm which rules those external tests use, so check your test setup before changing a rule or the collection’s default sort.

Who receives it

Layers sends the report to every user on the store who can view analytics and has a verified email address. This includes the store owner, organization managers, and any team member whose role grants analytics access, such as Merchandiser, Analyst, or Member. To add someone as a recipient, invite them to the store with a role that can view analytics. See Manage team members. Each recipient manages their own subscription, so one user opting out does not affect anyone else.

Opt out

To stop receiving the weekly report, use the unsubscribe link in the footer of any weekly report email. This unsubscribes you from the Weekly reports topic only. Other Layers emails, such as account and billing notifications, are unaffected. To resubscribe, use the subscription preferences link in the footer of any other Layers email, or contact Customer Care.

Troubleshooting

A setup note appears during an A/B test

Check the test named in the note before changing your merchandising. A running external test does not prove that the affected rule belongs to it. If the difference is intentional, leave your setup in place while you review the test.

You did not receive a report

Check the eligibility conditions, your Weekly reports subscription, and your spam folder. Contact Customer Care if you meet the conditions but still do not receive the report.

Next steps