Consider these three general requirements for image requests.
- At a minimum, the device has connectivity to the internet and supports sending standard HTTPS/HTTP image requests. This example tag request is sent to an Acoustic-managed data collection domain (dcd) provisioned for your account by Digital Analytics Support. Replace the value
dcd.mysite.comwith your assigned Acoustic-managed data collection domain.
<img alt="" src="http://dcd.mysite.com/cm?ci=59990000%7CSITEID123& st=1443555185620&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&tid=1&cg=Category%20ID &se=Search%20Term&sr=56&rnd=1443560080929&pv_a1=attr1&pv_a2=attr2&pv_a3=attr3 &pv1=extrafield1&pv2=extrafield2&pv3=extrafield3">
- The device accepts
httpcookie requests and stores local cookies.
As the device supports standard browser cookies, you can implement Acoustic-managed data collection by using
data.coremetrics.com third-party cookies or an available, delegated first-party data collection domain. If necessary, the visitor cookie can be session-based for cases in which the device does not support cookies with expiration dates, which results in identical visitor and session metrics. All other reporting is fully supported.
- If the device does not accept cookies, third-party cookies are not acceptable, or Acoustic-managed delegated data collection domain is not available.
If so, client-managed first-party data collection can be implemented. The device must be able to host logic for generating Acoustic Digital Analytics visitor ID and session ID values, which are dynamically appended to every image request sent from the device. Ideally, the visitor ID source value is persistent and based on a value defined within the device and accessible through API or OS layer to the code-generating the image requests. The "Session ID" can be randomly generated with each device session or generated by using a device session value. Acoustic Digital Analytics requirements for visitor and session ID formatting are specified in this document. These query string values are referred to as cj* parameters.
Note: Certain mobile service providers, such as BlackBerry Enterprise Server, do not reliably replicate full browser handling of cookies. To track the widest possible range of mobile devices, consider implementing data collection requests without cookies.