Contact History/Response History Tracking

Contact history and Response history (CH/RH) for the offers delivered from Journey will be tracked in Centralised history (CH) table of Campaign. Offer delivered by Delivery Email channels, Link connectors or by interact, using link delivery channels are recorded for CH/RH tracking. This tracking is done under respective Campaign Contact history tables.

In Journey when a user assigns an offer with Deliver communication, link connector or with Interact, they need to specify the partition and the audience level for which the history will be tracked. Based on the selected partition and audience level, history tables will be populated in Campaign schema. History related information can be used in Campaign. User can send this information from Campaign to Journey to verify how customer contact and responses are working.

Whenever a user adds a new audience level on Campaign settings, please make sure to restart Campaign web application. Only after starting this, user will be able to synchronize the contact and response history for newly added audience level.

Journey contact and responses will be synchronized with Campaign contact and Response history tables via Kafka topic- UNICA_CH_RH. All the contact and responses on this topic are consumed by Campaign application and they are synchronized in to history tables. Even though Campaign consumes the history records from kafka, they will continue to display on UNICA_CH_RH topic based on kafka configuration, which states how long these messages would be available on Kafka topic.

If there are multiple kafka consumers to Campaign group, contact history and response history that get populated might behave inconsistently. To check consumers on a kafka instance please use below command

kafka-consumer-groups.sh -bootstrap-server <kafka_host>:<port> --describe -group Campaign