How to handle multi country site in adobe analytics?

Hi @aagk123 ,

I think you have several possible options here which comes down to different report suite configurations available within Adobe Analytics.

1. Use one global report suite and send all data into it. Then use virtual report suite to segment your data based on locale.

2. Use multi-suite tagging where send all of your data to one global report suite and one to each specific geolocation.

3. Send data to only country specific report suites.

All of these have cost implications and features limitations which have been explained beautifully by other experts in these threads-

https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-questions/when-would-you-recommend-a-virtual-report-suite-to-segment-adobe/m-p/679179

https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-questions/report-suite-consolidation/m-p/697037#M52447

As for Adobe Launch, depends if you want to create each locale as a separate entity, then you would need to create a separate property for each one.

Hi @aagk123 
as @isha__gupta mentioned, multiple options.

It really boils down to whether there are stakeholders who want to see the big picture, meaning the global data. This will typically be manager / C-level people.

I personally prefer the single report suite approach with creating virtual report suites for different countries.
Ideally, make sure to capture the page country information in a dedicated prop or eVar. This can come from information in the data layer or potentially also from the URL if it exposes this information in its structure.

From there on, it is fairly straight forward

• create a segment for each country
• create a virtual report suite (components > virtual report suites) by dropping your segment(s) on the drop zone (see my example for external traffic below)

Once saved, you will see the virtual report suites marked with teal dots in front of them in your report suite selector.

I agree with both @isha__gupta and @bjoern__koth, there are many approaches, and you will need to assess what is right for you and your business.

When dealing with multiple countries, remember that while a VRS can be set up to use a different time zone from the global suite, Adobe only supports a single currency... now, there is a convert currency option in reporting, but it's based on the current exchange rate as opposed to the exchange rate when the purchase occurred.

There may still be options, such as choosing what the canonical currency should be, and making sure that all purchases are converted to that when sending the data to Adobe... or maybe you would want to do a custom solution like pass the amount, the currency designation, and a "current exchange rate" (if this is possible) so that you can create your own custom reporting based on a combination of the fields.

You may also want to have a dimension for language, but if you are using Activity Map, you might want to establish link and region overrides so that they all report in a single language, so that the content rolls up together.. rather than having to add up each link usage by all the different possible languages.