To track external websites using our Yamaha Adobe Analytics account, there are three main elements:

1. Consent Management.

2. Website Data Layer Development.

3. Tagging Implementation using Adobe Launch.

4. Adobe Analytics: differentiating between data from different domains.

1- Consent Management:

• It is mandatory to collect explicit consent from website visitors before tracking them.
• Our recommendation is to always have external websites under the yamaha-motor.eu domain. This way, OneTrust licence can be used for the external website.
• YME's current One Trust license isn't valid to be used on multiple domains (external domains). Therefore, a license change would be required if we were to use the current One Trust license owned by YME.
• Therefore, there visitor's consent shall be collected by the distributer(s) while making it clear to the website visitor that the collected data is shared with YME detailing the purpose(s) for which the data is collected. This was confirmed with YME Privacy department.

2- Website Data Layer Development:

To secure data consistency between data collected from different domains:

• The tracked events on external websites need to have the same event info and structure as we have for the same events on our corporate website.
• The website data layer shall be developed by the distributer so that YME can support using our internal tools maintaining consistent tracking for the same events across domains.
• A data layer requirements document shall be created by EPAM as they were responsible for developing the data layer on our corporate website.
• This document will act as a manual for distributers to have the external website's data layer as required.
• The tracking of external websites shall only be initiated once YME (EPAM) confirms that the data layer on the external website meets the requirements. 
• This way:
  • Tracked events on all domains are consistent and have the same definitions and conditions.
  • It is manageable to track more domains using a plug-in solution if we have consistent and similar data layers for the events that we track across domains.

3- Tagging Implementation using Adobe Launch:

• A new duplicated property for the external website in Adobe Launch shall be created with the same rules as in the property used for the corporate website.
• YME (EPAM) shall implement the tagging in Adobe Launch as done for the corporate website.
• One main addition in Adobe Launch will be needed which is to have the dimension "Server" populated with the domain of the source website to differentiate between data from different domains in Adobe Analytics. 

4- Adobe Analytics:

• A separate virtual reporting suit to be created in Adobe Analytics for each external domain.
• As our Adobe Analytics license is based on the amount of server calls, it is important to have a reliable estimate for the amount of events tracked on external websites (shared by the distributer / owner of the external website) when renewing the license. This way, we don't face any issues with the capacity of our license (over consumption) before the end of the license validity period. In case of over consumption, all tracked domains including the corporate website is impacted.
• These traffic/events estimates are required from the distributer(s) before the renewal of the Adobe Analytics license so that YME accounts for the total number of server calls that is needed during the validity period of the new license.

Alternative solution to tracking external websites using Adobe analytics:

• If the goal is finding a privacy friendly tracking solution, then we recommend Matomo to be used as a web tracking tool for the external website.
• Based on the discussion with YMES (the current case), the tracking is mainly needed for paid campaigns run by an external agency.
• In this case - tracking specific conversions for specific campaigns - an advertising pixel like Meta or Google pixel could be used to track conversion for paid campaigns.