Global report suite | Community
Skip to main content
cathyw49544988
Level 5
August 31, 2017
Solved

Global report suite

  • August 31, 2017
  • 13 replies
  • 4635 views

Have a question about global report suite. Anyone know how to setup a global report suites? ( detail procedure or video )?

I found in document, it mentioned that I will need to modify the s_code.js file.

I am wondering. if I create a new report suite and call it global report suite and in the DTM side, I add this one into all the properties. then will this report suites can consider as Global report suite? Any difference between thos one with the one if I setup with the s_code.js?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Alexis_Cazes_

Global report suite is part of what is called multi-suite tagging .

Global report suite is a naming convention and the report suite in itself does not need to be configured differently. The only thing that you need to do is specify the correct report suite Ids list in s.account in AppMeasurement.js (s_code.js is the old library and it is advised that you implement latest of AppMeasurement.js).

Lets say that you are a car company and you have a site section for each country, then under this site section you have a site section for each county and finally a site section for each shop that sale cars.

Then you will want to send all of your data to the the global report suite.

All of the data of a specific country to the country report suite.

All of the data of a specific county to the county report suite

Finally all of the data for a shop to the shop report suite.

The further you go into your site sections then the more report suite will be specified:

Global level s.account="globalreportsuiteid"

Country level s.account="globalreportsuiteid, countryreportsuiteid"

County level s.account="globalreportsuiteid, countryreportsuiteid, countyreportsuiteid"

Shop level s.account="globalreportsuiteid, countryreportsuiteid, countyreportsuiteid, shopreportsuiteid"

Multi suite tagging involve the use of primary server calls and secondary servers calls.

It is important to differentiate primary server calls and secondary server calls. When you do an Adobe Analytics implementation you can specify more than one report suite ID in s.account, which is called multi suite tagging.

  • The first report suite ID in the list will generate a request to Adobe Analytics (by default image request for web implementation). This request will count as primary server call and will be billed fully.
  • Any subsequent report suite listed will also each generate a request to Adobe Analytics. Each of these request will count as secondary server calls. Secondary Server calls are billed with a discount.

Another option to multi suite tagging is to use virtual report suites, please read this doc to see if it fits your requirements.

13 replies

Alexis_Cazes_
Level 10
September 22, 2017

Your code implementation and classification are two distinct things. It is not possible to set a classification at a code level.

At a code level when you set s.eVarX="value" then this value will be sent to analytics and assign in report eVar3. You cannot change this value in eVar3 report, it will be as it is send (unless there are additional processing like VISTA rule or Processing rules set).

Then once you have all of the keys that you want in your base report eVarX you can decide to create additional classification reports for report eVarX. Each classification report value will be directly tied to a key, and more than one key can have the same classified value.

If you put any new value in an evar, in a direct call rule or any rule, that was set prior by another rule, then the new value will overwrite the old value, which will result in loosing initial value.

For data element in DTM, if you cannot see it when you type %siteTitle% then you must have not created the data element correctly. I think we are deviating too much of the initial topic in this post. As it is linked to DTM, I would advise you to create a new POST under Dynamic Tag Management 

cathyw49544988
Level 5
September 22, 2017

Thanks Alexis. I agree.

cathyw49544988
Level 5
November 1, 2017

Alexis,

I really have a lot of interest in using the context variable. as the example you mentioned in the previous message:

/Use your data element to populate your contextData

s.contextData['article_title'] = _satellite.getVar("THE NAME of your DATA ELEMENT");

After I setup the s.contextData['article_title'] variable, will this context variable be able to sent to the adobe server when a rule fire? Do I need to use the process rule to assign this context variable to a eVar or Prop?

Will context variable available to workspace?

Thanks