You must include cj* parameters in all requests when you implement client-managed, first-party data collections.

For client-managed first-party data collection, the following query string values are required if the device does not accept or properly handle standard cookies (third party or Digital Analytics managed first-party data collection is not implemented).

Incomplete, missing, or malformed cj* query string parameter values cause the data collection tag to be rejected and not reported.

If no cj* parameters are sent with the request, Digital Analytics data acquisition servers attempt to set visitor ID and session ID cookies. If the device does not accept cookies, the image request is accepted as anonymous data. Anonymous image requests increment simple aggregate anonymous metrics in the Digital Analytics Top Line Metrics report for page views, orders, product views, items, and revenue. Other anonymous tag data is not reported. No other report, application, or export in Digital Analytics will display anonymous metrics.

Required cj* query string parameter values

&cjen=1

• Enable client-managed cookies through inline query parameters (always 1).

&cjuid=70161209681625076771130

• The visitor ID is a 23-digit numeric value. This value represents a unique and persistent client device or application installation in reporting. Do not include leading zeros in this value.

&cjsid=1267643383

• The session ID is a 10-digit session value. This value represents a session for a visitor. Typically, a visitor (cjuid) is associated with multiple sessions over time. A session in Digital Analytics reporting is the unique combination of cjuid and cjsid.
• If more than one client ID (ci=value) is specified, a pipe (|) delimited list of cjsid (session ID) values must be sent equal to the number of ci=values. For example, if ci=value is ci=11111111;99999999, then make cjsid=value a pipe-delimited list such as cjsid=1234567890|1234567890. The cjsid values can be the same value for multiple client IDs. This delimiter requirement does not apply to multisite analytics ID|Site ID combinations, which always send only one cjsid= value with each tag. Do not include leading zeros in this value.

&cjvf=1

• The valid session flag is always set to 7 in the first tag for a new visitor and a new session or to 3 for the first tag of a new session for an existing visitor. Subsequent tags for that. visitor/session (cjuid/cjsid) combination all use the value cjvf=1 (same visitor/same session).
• If more than one standard 9-series client ID (ci=value) is specified, a pipe (|) delimited list must be sent. For example, cjvf=1|1. This requirement does not apply to multisite Analytics GlobalID|SiteID client ID values, which always send only one &cjsid= and &cjvf= value with each tag.

Example 1: A complete first-party pageview image request, which includes cj* inline visitor ID and session ID parameters:

http://data.coremetrics.com/cm?ci=99999999&st=1443558077994&vn1=4.1.1&ec=utf-8
&vn2=mobile&pi=Page%20ID&ul=http%3A%2F%2F127.0.0.1%2Fmobileguide
%2FTagTester_mobileguide-examples.html&cjen=1&cjuid=73954275346114435560269
&cjsid=1443558078&cjvf=7&tid=1&cg=Category%20ID&se=Search%20Term&sr=56
&rnd=1443559342348&pv_a1=attr1&pv_a2=attr2&pv_a3=attr3&pv1=extrafield1&pv2=extrafield2
&pv3=extrafield3

Example 2: The pipe (|) delimiter between the multiple &cjsid= and &cjvf= values must not be URL-encoded.  The semicolon (;) delimiter between each Client ID (?ci=) value must be URL-encoded as %3B.

http://data.coremetrics.com/cm?ci=11111111%3B88888888&st=1443558077994
&vn1=4.1.1&ec=utf-8&vn2=mobile&pi=Page%20ID&ul=http%3A%2F%2F127.0.0.1
%2Fmobileguide%2FTagTester_mobileguide-examples.html&cjen=1
&cjuid=73954275346114435560269&cjsid=1443558078|1443558078&cjvf=7|7
&tid=1&cg=Category%20ID&se=Search%20Term&sr=56&rnd=1443559342348&pv_a1=attr1
&pv_a2=attr2&pv_a3=attr3&pv1=extrafield1&pv2=extrafield2&pv3=extrafield3

Example 3: A complete first-party pageview image request sent to a single multisite Analytics 5-series client ID value of 59990000|SITEID123.  The pipe (|) delimiter between the 5-series ID and SiteID values must be URL-encoded as %7C.

http://data.coremetrics.com/cm?ci=59990000%7CSITEID123&st=1443558077994
&vn1=4.1.1&ec=utf-8&vn2=mobile&pi=Page%20ID&ul=http%3A%2F%2F127.0.0.1%2Fmobileguide
%2FTagTester_mobileguide-examples.html&cjen=1&cjuid=73954275346114435560269
&cjsid=1443558078&cjvf=7&tid=1&cg=Category%20ID&se=Search%20Term&sr=56
&rnd=1443559342348&pv_a1=attr1&pv_a2=attr2&pv_a3=attr3&pv1=extrafield1
&pv2=extrafield2&pv3=extrafield3