2.3.1 cmSetClientID

The cmSetClientID(...) function is required and sets values for 'Client ID', 1st Party method ('Client Managed' or 'IBM® Managed'), 'Data Collection Domain' and 'Cookie Domain'. This function must be called on every page sending data to IBM Digital Analytics.

<head> <script type="text/javascript" src="//libs.coremetrics.com/eluminate.js">
</script> <script type="text/javascript">
// Client Managed First Party
cmSetClientID("99999999",true,"data.coremetrics.com","thesite.com");
// IBM Managed First Party 
cmSetClientID("99999999",false,"<dcd>.thesite.com","thesite.com");
</script> </head>
<body> ... <script type="text/javascript"> cmCreatePageviewTag("FAQ Page 1", "FAQ");
</script> </body>

Europe Data Centers - Data Collection Domains

The Europe Data Center uses the following production data collection domain:

// Client Managed First Party
cmSetClientID("99999999",true,"data.de.coremetrics.com","thesite.com");

Sending Data Tag Requests to Multiple Client IDs

It is possible to copy data tags to two or more Client IDs by specifying a semicolon-delimited list of ID values. The IDs specified must all be production IDs or test IDs: a mix of test and production IDs is not allowed. If sending tags from multiple sites where each site also copies tags to a dedicated 'aggregate' ID, the first ID specified in the list should be the 'aggregate' ID. The 'aggregate' ID reports data tags copied from multiple sites.

- Example of sending tag requests from site #1 to the 'aggregate' ID and site-specific ID #1, where 99999999 is the 'aggregate' ID and 11111111 is the site-specific ID:
```
cmSetClientID("99999999;11111111",true,"data.coremetrics.com","site1.com");
```
... and from site #2 to the 'aggregate' ID and site-specific ID #2 (ID 22222222):
```
cmSetClientID("99999999;22222222",true,"data.coremetrics.com",
"site2.com");
```

Note that copying requests to two or more ID's increases total server calls assessed by (1*the number of IDs specified). In the example above, each tag sent from the page is copied to 2 ID's, resulting in 2x total server calls assessed.

IBM Digital Analytics Account, Sales and Provisioning teams is able to provide specific information regarding what ID's, if any, have been contracted for 'aggregate' data collection and the Monthly Million Server Call volume contracted for each ID.

Sending Data Tag Requests to Multisite Analytics ID and Site IDs

Data is sent to an Multisite Analytics 'Site ID' by using a pipe delimiter (|) in the Client ID parameter of cmSetClientID(...).

Note: Do not use these characters in <SiteID> values: ampersand (&), pipe (|), single quote ('), or comma (,)

Example of sending tag requests to Multisite Analytics Client ID '88888888' and a Sub-ID, where <SiteID> is the configured Multisite Analytics Sub-ID:
```
cmSetClientID("88888888|<SiteID>",true,"data.coremetrics.com","site1.com");
```
Example of sending tag requests to 1) a regular Client ID '99999999', 2) an Multisite Analytics Client ID '88888888' and 3) a Site ID, where <SiteID> is the configured Multisite Analytics Sub-ID:
```
cmSetClientID("99999999;88888888|<SiteID>",true,"data.coremetrics.com",
"site1.com");
```

It is possible to copy tag requests to multiple Multisite SiteIDs.

cmSetClientID("59990000|SITEID-1;59990000|SITEID-2",true,"data.coremetrics.com",
"site1.com");

Tag requests sent from this page generate identical reporting for both SITEID-1 and SITEID-2. At the Global ID level, each tag is reported once for each SiteID it is copied to. For example, if a PageView tag is sent, two total 'page views' are reported for that page ID in Global ID 59990000 reporting.

Note: Sending tags to more than one SiteID costs one server call per specified SiteID.

Parameter	Required	Description
Client ID	Required	Unique 8-digit IBM Digital Analytics-assigned account code associated with a single analytics data warehouse and reporting instance.
Data Collection Method	Required	Boolean true or false: True indicates 'Client Managed' 1st Party. False indicates 'IBM Managed' 1st Party or '3rd Party' as applicable.
Data Collection Domain	Required	The target domain for IBM Digital Analytics data collection requests. If Data Collection Method = false: Data Collection Domain should be set to the IBM Managed 1st Party data collection domain. Example: ("<1stpartydcd>.thesite.com"). If Data Collection Method = true: Data Collection Domain should be set to "data.coremetrics.com".
Cookie Domain	Required	The domain for Client Managed cookies. Cookie Domain should be set to the 2nd level site domain ("thesite.com") of the domain serving the tagged page(s). In cases of extra domain levels prior to the uniquely identifying site domain value, this might be a 3rd or higher level. Example: "thesite.co.uk". If Data Collection Method = false: IBM Digital Analytics Visitor and Session cookies are set under the IBM Managed Data Collection Domain ("<1stpartydcd>.thesite.com"). Other IBM Digital Analytics cookies are set in the Cookie Domain. If Data Collection Method = true: ALL IBM Digital Analytics cookies are set in the Cookie Domain.