Adobe Analytics

Event serialization is the process of implementing measures to prevent duplicate events from entering Analytics reporting. This can commonly occur when a user refreshes the page multiple times, navigates to a certain page multiple times, or saves the web page to their computer (for example, if a customer saves a purchase confirmation page to their computer, every time they view it orders and revenue would be counted again if event serialization was not in place). Event serialization is useful in the following instances:A page may be reloaded or refreshed and repeatedly send an event. Event serialization prevents events from being recounted by using a serial number for each event.The user saves the page to his/her machine for later review. This scenario is quite common on purchase confirmation pages to review purchase receipts. Event serialization prevents the subsequent page reloads from re-counting the events.Note: Data Sources does not support event serialization or de-duplication.Th

Processing time for a SAINT file varies on the size of the file and the number of SAINT files that Adobe's servers are processing. Classification uploads usually take no longer than 72 hours to process.In SiteCatalyst 14, uploads are processed in a queue. Once complete, they are available in the interface. SiteCatalyst 15 and Discover process SAINT uploads in six-hour increments, updated four times a day. Determine when an upload finishesTo check and see if a classification file has finished uploading, do the following:Log in to SiteCatalyst and go to Admin > SAINT Classifications.Under any of the tabs, select the report suite and data set in question.If processing is not complete, either one of the following messages appear: The selected report has a SAINT import that is processing. The selected report has SAINT data that hasn't propagated to all servers yet.No message appears if processing is complete. Minimize SAINT processing timeAdobe strongly recommends that you use the follow

Due to differences in processing mechanisms and platforms, the various types of downloadable and scheduled reports available in Adobe Analytics have different limitations regarding the maximum number of rows it can process in a single request. The following are the limits of each:Word, CSV, Excel, HTML and PDF: The same number of rows visible in the report. By default this limit is 50 rows but can increase up to 200. Breakdown reports have a hard limit of 50 rows.Data Extracts: 50,000 rowsData Warehouse: UnlimitedNote that these limitations are for individual scheduled and downloaded reports; dashboards are limited to the amount of space available within a reportlet.

Bot Rules let you remove traffic that is generated by known spiders and bots from your report suite. Removing bot traffic can provide a more accurate measurement of user activity on your website.After bot rules are defined, all incoming traffic is compared against the defined rules. Traffic that matches any of these rules is not collected in the report suite and is not included in traffic metrics.Removing bot traffic typically reduces the volume of traffic and conversion metrics. Many customers find that removing bot traffic results in increased conversion rates and increases in other usability metrics. Before removing bot traffic, communicate with stakeholders to make sure they can make the necessary adjustments to key performance indicators as a result of this change. If possible, it is recommended to first remove bot traffic from a small report suite to estimate the potential impact.We recommend defining no more than 200 bot rules per report suite.Bot traffic data is stored in a sep

If you do not want a report suite to be available to you and your users any more, you can hide it from view. Hiding a report suite prevents it from being shown in the report suite selector drop-down menu., the Admin Console, or anywhere else that report suites are shown. It makes the report suite's data inaccessible via the Adobe Analytics interfaces until the report suite is unhidden.Note: Data that is sent to a hidden report suite from your site continues to be collected, processes, and billed.To hide the report suite, go to Analytics > Admin > Company Settings. Check the Hidden checkbox to the left of the report suite name.To unhide the report suite, uncheck the Hidden checkbox.To view only hidden report suites under Company Settings, select View > Only Hidden Report Suites.To view only visible report suites, select View > Only Visible Report Suites.The default is View > All. Reference: https://marketing.adobe.com/resources/help/en_US/reference/c_hide_report_suites.ht

As your site collects data, there are many external factors that can drastically affect data collection or reporting. The following is a list of potential explanations as to why certain variables or overall traffic dramatically increases or decreases.Traffic dropsTo troubleshoot dramatic decreases in traffic, place each into two categories: zero data or partial data.Potential causes of completely missing data (reporting zeros) Implementation removal: Sometimes when an organization makes implementation changes or even a site restructure, reimplementing code is overlooked. Working with your developers in reimplementing the code on your site is recommended to resume data collection.Report Suite Latency: Occasionally, a report suite can experience latency due to a number of factors. Many latency issues are resolved within hours. If you are concerned with a specific report suite, one of your organization's supported users can contact Customer Care with the affected report suite ID. The Adob