How to Improve Website Page Load Speed By Switching Adobe Data Centre
Posted by
Tomas
Balciunas on
19 November 2012
Analytics
Data centres are collections of servers that collect data. Adobe’s digital marketing suite contains a host of tools (such as SiteCatalyst and Test & Target) that send data about your browsing behaviour to be stored in such centres.
That data is then processed and prepared for displaying within the SiteCatalyst or Discover interface, or for download by data warehouse exports.
There are two ways Adobe collects website analytics data.
Data Processing Centres (DPC)
This is the old way of collecting data. Servers are located in San Jose, California and Dallas, Texas. According to Adobe this method of collecting data results in slower page loads for any websites that use SiteCatalyst tracking code and also minor data loss due to cookie redirects. Most old SiteCatalyst and Test & Target implementations use this method of data collection.Regional Data Collection (RDC)
The Regional Data Collection (RDC) is a network of regional Data Collection Centers (DCC) that aims to reduce latency and data loss when collecting data from a website. This new method of collecting data improves the site performance issues noted above in the old method, and therefore results in faster page load speeds.
Adobe published a Map (see image above) of a world wide RDC and something that Adobe calls “Edge Site” dedicated for Test & Target. For all UK and Europe customers the closest RDC and Edge Site is in London.
Recently Adobe announced a new Regional Data Collection (RDC) centre in Brazil although this RDC is not marked on the map.
Adobe is planning to open a new Data Centre in Amsterdam soon.
Which data collection method SiteCatalyst implementation is using?
In order to determine by which method and to which location your SiteCatalyst implementation is sending data to you have to analyse the image request (web beacon) domain. One of the ways to do this is by using Adobe Digital Pulse debugger.For SiteCatalyst implementations use the Digital Pulse debugger look for a “First Party Cookies” or “Third Party Cookies” row. If you find a “First Party Cookies” row it means that your SiteCatalyst implementation is using first party cookies and data is sent to company’s domain (contact us to find out to which Omniture server the data is sent when using first party cookies).
If it is “Third Party Cookies” then your data is sent to one of the following locations:
Non-RDC domains (old data collection method)
- 112.2o7.net - San Jose, California
- 122.2o7.net - Dallas Texas
- d1.sc.omtrdc.net - San Jose, California
- d2.sc.omtrdc.net - Dallas, Texas
- d3.sc.omtrdc.net - London, United Kingdom
Improving your SiteCatalyst implementation
If you discover your SiteCatalyst implementation is not using an RDC domain (data is being tracked the old way) then there is a strong possibility you are losing data and your page load speed is being hurt. You should think about migrating to the new data collection method.For more information and assistance on doing this, please contact us.
No comments:
Post a Comment