My first post here ;Starting a brand new implementation

1. Talk to your stakeholders and categories the data you want to track. You will understand that there is going to be generic data that you would want to track across all sections of your websites like page name, server, site section, sub site sections (might be multiple level down). Try to avoid to create one eVar report for each business requirements. You will find out that each time there is a release, your stakeholders will want to track a functionality but you will soon find out that eVar and prop reports are limited so try to find a solution to group data in same report (if allocation and expiration is same and you want to persist them at the same time). You can use classification rule builder to plit the data in their own reports.

 2. Currency code needs to be one of supported values https://experienceleague.adobe.com/docs/analytics/implementation/vars/config-vars/currencycode.html?lang=en

Make sure to reference the correct value as needed otherwise there is going to be processing issues. Also make sure to use the same in report suite otherwise there will be conversions.

3. Use purchaseID to make sure your purchases are not duplicated: https://experienceleague.adobe.com/docs/analytics/implementation/vars/page-vars/purchaseid.html?lang=en In some instances the thank you page can be reloaded or accessed and the purchase event will fire. Without the purchaseID, your will have inflation of orders and revenue

4. Make sure to respect the s.products syntax. Do not use any of the following characters in any of the section for the names", ; |" these are reserved characters and have a specific meaning in s.products. https://experienceleague.adobe.com/docs/analytics/implementation/vars/page-vars/products.html?lang=en

5. Configure the expiration and allocation of your variables correctly. The persistence of the eVars is done server side and not client side.

6. There are predefined events for checkout and purchase workflow, use those. use custom events for anything else. https://experienceleague.adobe.com/docs/analytics/implementation/vars/page-vars/events/events-overview.html?lang=en

7. Be aware of size limit for each variables, props are limited to 100 char and eVars to 250 chars

8. Make sure to sanitise any data related to URLs, remove any PII data or tokens.

9. Never gather PII data into Adobe Analytics, it is not allowed. removing any data is costly.

10. Implement a data layer. This will require some effort from your development team but it is worthwhile in a log run. Your tagging efforts will be easier and data quality will improve. Example: https://dev.to/alcazes/generic-data-layer-1i90

11. Finally use tagging, coding and release standards.

You are going to do mistakes which is normal, also your reporting requirements might evolve from one week to another, that is why it is important to plan and categories what type of data your business would need. If you start to architecture your tagging correctly early, the less issues you will face