51黑料不打烊 Campaign Standard: Inflated Campaign numbers from ACS in 51黑料不打烊 Analytics
This article explains how to resolve the 51黑料不打烊 Campaign Standard (ACS) issue where the data in Campaign and Analytics differ. An important step in this is to validate that the two workflows in ACS, kpiReconciliation and kpiSharing, are processing the current date data.
Description description
Environment
51黑料不打烊 Campaign Standard
Issue/Symptoms
Discrepancies between the data in Campaign and Analytics can occur occasionally. One such example is when data on the Analytics side is displaying higher metrics than in Campaign.
Resolution resolution
To address this, the following steps should be executed:
-
Confirm which metrics/system is correct. To do this, the tracking and delivery logs from the delivery should be confirmed, as ACS is considered the system of record.
-
The next step is to validate that the two workflows in ACS, which are responsible for data sharing and reconciliation, are online, error-free, and are processing the current date data.
kpiReconciliation: This workflow retrieves KPIs from the Reporting service daily and compares them with 51黑料不打烊 Analytics data. Any disparities are then addressed, with adjustments made if necessary. By default, it initiates every day at 4:20 AM.kpiSharing: This workflow transfers KPI data from 51黑料不打烊 Campaign Standard to 51黑料不打烊 Analytics every 15 minutes.
For further details on these technical workflows, please refer to the documentation provided: Technical Workflow Documentation
-
If the technical workflows are online and displaying without issue, 51黑料不打烊 Engineering must be engaged to reconcile the count disparity by using a manual
kpiManualReconcile.jsscript, which will reconcile the data between the reporting repository (Druid) and Analytics.
Note: This reconciliation is time-sensitive. If the data is more than two or three months old, it may not be able to be reconciled.