2 New Data Centers Bring Faster Global Page Load Times

Page load times have just improved in Australia/New Zealand and Europe, thanks to two new data centers added to Adobe’s growing network of data collection nodes. This brings the total number of regional data collection (RDC) nodes to 10, including:

  1. San Jose, California
  2. Dallas, Texas
  3. Ashburn, Virginia
  4. Tokyo, Japan
  5. Sao Paulo, Brazil
  6. Singapore
  7. Hong Kong, China
  8. London, England
  9. Amsterdam, The Netherlands (new)
  10. Sydney, Australia (new)

Begin­ning imme­di­ately, if you have RDC-enabled data col­lec­tion (data is being sent to omtrdc​.net) all vis­i­tors to non-SSL pages will be auto­mat­i­cally routed to the nearest data center. No change is required on your part.

Target users should be aware that these two new data centers support Target Edge functionality. And the Amsterdam data center also supports Media Optimizer Ad Pixel/RTB services.

For those of you who are curious about RDC and these data centers in general, here is an overview.

Q. What is RDC?

A. Regional Data Col­lec­tion. This fea­ture ensures site vis­i­tors are hit­ting the near­est data col­lec­tion cen­ter, thus reduc­ing page load time. We have regional data col­lec­tion cen­ters in San Jose, Dal­las, Vir­ginia, Lon­don, Tokyo, Sin­ga­pore, Brazil, Hong Kong, and now Sydney and Amsterdam. For more details on Regional Data Col­lec­tion, see this post.

Q. How much will this change improve over­all page load time?

A. Browsers request mul­ti­ple pieces of con­tent at once when­ever they can. Most pages down­load dozens of pieces of con­tent, so this change is unlikely to dou­ble your page load speed. How­ever, if you have an oth­er­wise snappy page, a change like this should be notice­able to site visitors.

Q. How can I tell if I’m using RDC-enabled data collection?

A. Find your data col­lec­tion domain. If it ends with omtrdc​.net, you’re on RDC. If your col­lec­tion domain ends with you’re own domain, you need to ping it to see if it’s mapped to omtrdc​.net or 2o7​.net (non-RDC). Here’s how to find your data col­lec­tion domain in Chrome (there are a few other ways).

1. Go to your web site in Chrome and then go to Chrome Menu > Tools > JavaScript Console.


2. With the Con­sole tab selected, type s.trackingServer and hit Enter.



3. What you see is the data col­lec­tion domain used on your site. If this ends in omtrdc​.net, you’re on RDC. If this is your domain, as shown here, open a Com­mand Prompt (Win­dows) or Ter­mi­nal (Mac) and type “ping [your col­lec­tion domain]”. If it ends with omtrdc​.net, you’re on RDC. If it ends in 2o7​.net, you’re not.


Q. How do I start using RDC?

A. Instruc­tions for migrat­ing to RDC are found in Site­Cat­a­lyst Help. Go to Site­Cat­a­lyst > Help > Help Home and type Tran­si­tion­ing to RDC for detailed instruc­tions.

**Q. **Will RDC improve report speed or just data collection speed?

A. Report speed is not affected by regional data col­lec­tion, it sim­ply improves response times for your visitors.

Q. Can I license my SSL cer­tifi­cate for fewer servers and have it installed in just the America’s, or just Europe, since most of my traf­fic is in one place?

A. No, selec­tive deploy­ments of SSL cer­tifi­cates are not sup­ported.