Adobe attempts to partner with clients to ensure that a high-traffic event is successful. Scheduling traffic spikes is the starting point in that partnering process.
Advanced server-side data balancing with several dedicated personnel are used to make sure that all customers have the most up-to-date reports possible. As your organization notifies Adobe of spikes in traffic, Adobe can make sure that the sudden increase in traffic is a positive experience. Failure to notify Adobe of increases in traffic can increase latency during critical reporting periods.
The following topics are helpful to know when working with Adobe in more traffic to your report suite.
There are two common categories of latency:
Real-Time data latency: This type of latency only affects Real-Time reporting. It consists of basic metrics like page views and counter events. It does not include advanced processing-intensive reporting like eVars or unique visitors.
If a report suite's Real-Time data goes latent due to a spike in traffic, it can often be resolved quickly once identified. Adobe can adjust allocated resources to help get back to normal latency.
Full processing data latency: This level of data is the most processing-intensive, and therefore is the most sensitive to unannounced traffic increases. Recovery to normal latency levels typically takes several hours or more. This estimate is not a service-level agreement, but rather a general statement that it takes time to fully catch up processing data.
When customers notify Adobe of traffic spikes for each report suite, Adobe does everything possible to ensure that it has a minimal impact on reporting.
- Organizations that have scheduled traffic spikes receive priority if data starts going latent. The importance of this concept is especially critical during the holiday season, as many organizations schedule traffic spikes.
- If Adobe notices that you significantly overestimated/underestimated expected traffic compared to previous years, they may contact you to ensure accuracy.
- It is important to schedule a traffic spike every year, even if your organization receives the same spike each year. Many organizations release new apps, combine report suites, and migrate/retire report suites throughout the year. Adobe has no way of knowing for certain which report suites receive extra traffic unless your organization schedules a traffic spike each time. While Adobe uses historical data to get an estimate, it is important that any extra resources are placed on the right report suite.
Adobe wants to make sure that your experience with up-to-date reporting is consistent. To do this task most effectively, Adobe highly recommends the following:
- Schedule all traffic spikes according to Required Lead Time for Traffic Increases. It is especially important that any traffic spikes anticipated in the months of November-December are scheduled by September 15. If you miss the deadline, schedule your spike as soon as possible. Less lead time is better than none, and Adobe works with the current resources to best accommodate your report suites.
- If Adobe contacts you regarding a scheduled traffic spike, be sure to communicate which type of latency you are most concerned with. Some organizations rely on Real-Time reporting more than others. Understanding which type of reporting you use can help Adobe prioritize accordingly.
- Communicating with your Account Manager the most important reports and when you pull them can help them advocate for you.