Troubleshooting Digital Analytics integration - Number of records mismatch

When a flowchart runs, Unica Campaign detects if there is a mismatch between the number of IBM Digital Analytics keys and Unica Campaign audience IDs in the mapped translation table. A warning occurs if the number of registrationIDs does not match the number of audience IDs.

If a mismatch is detected, Unica Campaign writes a warning message to the flowchart log file asking you to verify that the mapped translation table contains updated records.

This behavior is intended to detect and prevent discrepancies between the IBM Digital Analytics keys and the corresponding Unica Campaign audience IDs in the mapped translation table. Consider the example where there are registration IDs in the IBM Digital Analytics segment which have not yet been added to the translation table because the ETL routines have not completed. In this case, you might have 100 customers from an IBM Digital Analytics segment, but only 95 CustomerIDs in Unica Campaign. The results are skewed now (100 records vs. 95 records) but they will be fine when the ETL routine completes.

To resolve this problem, (re)match the online and offline keys according to your corporate policy and repopulate the translation table with up-to-date data. The user must rerun the flowchart after the mapped translation table is updated.