My first post here ;Starting a brand new implementation

[AbhijitB]

What are the top 5-10 things I should know and common mistakes to avoid. Sorry if I this has already been asked. 

Thank You again

[Alexis_Cazes_ · Accepted solution]

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?...

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... 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=e...

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-overvi...

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

[yuhuisg]

Here are mine, which repeats some of what Alexis has mentioned already.

Assuming that you have already gathered all of the business requirements and going straight into the implementation part:

1. Set your eVar allocations and expirations correctly. Don't just use the defaults blindly. Think clearly about what you're collecting and how that data is being reported.
2. Set your Marketing Channels correctly. You could use the defaults, but make sure they align with your business requirements.
3. Configure your internal domains properly. Remember: subdomains are ignored in the configuration.
4. Make use of Classifications. Don't think of it as an advanced feature. There's a lot of power in it.
5. Use Adobe Launch + Adobe Client Data Layer + Adobe Web SDK for your implementation. Setup Processing Rules accordingly in Adobe Analytics to set your props/eVars/events properly.

[AbhijitB]

Thank You for your response, @yuhuisg  and @Alexis_Cazes_ .

The final objective of the Adobe Analytics Implementation for my b2b site is as follows:

See all clicks, user count, visits, page views for each Company/account that visits the web site.

So if users from Target or Best Buy visit the site, I want to know what did these users from Target and Best Buy do in terms of clicks, page views, so that I can compare and contrast their behaviour.

Should I use Adobe Launch + Adobe Client Data Layer + Adobe Web SDK for this implementation ?

There is no one else in my org who knows anything about Adobe implementations and hence not sure whom to ask and where to start ?

[yuhuisg]

---

@AbhijitB wrote:

So if users from Target or Best Buy visit the site, I want to know what did these users from Target and Best Buy do in terms of clicks, page views, so that I can compare and contrast their behaviour.

I think this is your key consideration. If you're able to add campaign tracking codes to the links from Target/Best Buy/etc to your website, then do so and setup a Marketing Channel specifically for such traffic. Otherwise, you'll have to rely on Referring Domains, which won't be as accurate given the prevalence of mobile apps and private browser windows.

I'd say that implementing with Adobe Launch + Adobe Client Data Layer + Adobe Web SDK is the way forward for all Adobe-related tracking.