Campaign: AEP-Campaign sync record mismatch

This article explains why delivery-log records can appear to be missing in Adobe Experience Platform (AEP) when they are exported from Adobe Campaign Classic (ACC) through the out-of-the-box ACC → AEP connector. The issue is most visible during validation exercises or low-volume use cases where record counts are compared across systems shortly after delivery activity is generated.

Description description

Customers may observe that delivery-log or feedback records present in the ACC source tables are not yet visible in AEP, resulting in an apparent record-count mismatch between ACC and AEP.

This behavior is typically noticed when:

  • feedback or broadLog records are validated shortly after creation
  • multiple records are created very close together in time
  • downstream use cases depend on near-real-time synchronization of the latest communication activity
  • low traffic volume means there is no immediate subsequent export cycle to pick up the remaining records

In these cases, ACC and the upstream source can appear consistent, while AEP shows fewer records at that point in time. The data that does arrive in AEP is correct, but the latest records may not yet have been exported.

Resolution resolution

The root cause is the designed export-window logic used by the ACC → AEP connector. During each run, the connector exports records whose timestamp is strictly less than the current maximum timestamp found in the source set. Records whose timestamp is exactly equal to that current maximum are intentionally excluded from the current run and are expected to be exported in a later run.

This design exists to avoid duplicate exports when additional records with the same maximum timestamp are still being created or committed. In continuously active systems, those records are typically exported during the next cycle. However, in low-volume or decisioning-sensitive scenarios, this creates a delay window where the newest delivery-log records are not yet available in AEP, which can be interpreted as a sync defect or record omission.

recommendation-more-help
experience-cloud-kcs-help-kbarticles