You can view sample code to further understand the implementation. The following information outlines the additional requirements and configurations:
The parameter names ( pageName , purchaseID , and so forth) are case-sensitive and will not properly record data unless they appear as designated in the table displayed in Query Parameters .
Encode Query Parameters
The values for each of the query string parameters must be URL encoded. URL encoding converts characters that are normally illegal when appearing in a query string, such as a space character, into an encoded character beginning with % . For example, a space character is converted into %20 .
Maximum Variable Length
Each variable has a maximum length. This length is specified for each variable in Analytics Variables . Exceeding the maximum length for a variable causes the value of this variable to be truncated for storage and display in Analytics.
Characters with character codes above decimal 128 are invalid, as are not-printing character codes under 128. HTML formatting ("<h1>") is also invalid, as are trademark, registered trademark, and copyright symbols.
Secure (<https:> vs. Non-Secure (<http:>) Image Requests
On pages that are accessed via https (secure protocol), the URL portion of the image request changes to accommodate a different set of data collection servers.
The following information illustrates the different URLs used for secure and non-secure image requests.
- The * in the URL above denotes a data-center specific URL that is provided to you by your Adobe Consultant. Adobe uses several data centers, and it is necessary to implement the correct URL your organization has been assigned. Any code downloaded out of Admin Console within your company account has the correct data center supplied automatically. Code provided from external sources may need to be corrected in order to point to the correct data center.
- For clients who use multiple report suites, they should be listed only in the directory section, and not the domain section of the URL, as shown below.
- The * in the URL above denotes a data-center specific URL that is provided to you by your Adobe Consultant. Adobe uses several data centers, and it is necessary to implement the correct URL to which your organization has been assigned.
URL and Referring URL
The URL and Referring URL may be populated from the server in the g= and r= variables. Use the Request ServerVariables ( HTTP\_REFERRER ) or Request ServerVariables (URL) (IIS/ASP) , or the appropriate variable for your server/scripting technology. The referring URL ( r=) is extremely important for tracking referring URLs, domains, search engines, and search terms.
If pageName is not being used, it is imperative that the Current URL field is uniquely populated. If neither pageName nor Current URL (g=) is populated, the record is invalid and is not processed. At a minimum, the URL is a required field in order to process the record.
Effects of Caching
HTML and other Web pages can be cached by browsers or servers that are between the visitor and the website that is serving the content. Caching prevents an accurate count of page views and other events unless a "cache-busting" technique is employed.
However, in creating a server-side image request, this randomization does not occur. Page reloads and cached pages (either in the browser's cache or in a proxy server) are not counted in certain cases when using server-side image requests.
SSL ( https: ) pages are not, by definition, ever cached so this warning applies only to non-secure ( http: ) pages. Additionally, pages with parameters ( https://www.samplesite.com/page.asp?parameter=1 ) or certain file extensions ( .asp , .jsp , etc.) are also not cached.
Contact your Adobe Consultant or Account Manager to obtain your organization's nameSpace value.