Setup Analytics Feedback

/help/tutorial-web-sdk/setup-analytics.md

1. In the Create e-commerce data elements section step 6 says to leave the Force Lowercase and Clean Text boxes unchecked, but the screenshot shows the clean text box checked. It probably doesn't really matter which is updated...the text or the image. There are plenty of reasons why clean text for a product ID would be a good thing.

2. In the "Create Additional Rules" section, after step 3, you need to include a step to click "Keep Changes" before you can return to the rule and add a condition

3. There are a few pages like https://luma.enablementadobe.com/content/luma/us/en/products/men.html that accidentally trigger the product view event because it has /products' in the URL.

4. The note about remembering to set the global variables was awesome. One thing that would have also been helpful is reminding to set the product list items variable when dealing specifically with the cart and product pages

5. When creating the processing rule, we set the Product name to prop1 and the screenshot shows that prop1 has a name of Product Name. However, the tutorial didn't have any prior instructions to go into the Analytics Admin and rename prop1 to Product Name.

6. The real-time reporting aspect is a nice way to see the data quickly. However, there's not a lot of explanation of what these reports are. And then we're pulling metrics against a prop, which is just awkward on its own. I get why it's being done, but if you have a workspace that will need 30-60 minutes to process anyway, then why not just stick with workspace and not use the real-time reports? There are even some pre-built templates that might make this easier anyway.

Open /help/tutorial-web-sdk/setup-analytics.md and review the six reported discrepancies against the linked Luma page and the screenshots. Check each affected instruction, including the save step, variable setup, processing-rule naming, product-view behavior, and reporting explanation. Done means the tutorial text and images agree and all requested guidance is addressed.

Written by the indexing model from the issue text.