Different tracking log tables not clear | Community
Skip to main content
Marcel_Szimonisz
Community Advisor
Marcel_SzimoniszCommunity Advisor
Community Advisor
August 6, 2021
Solved

Different tracking log tables not clear

  • August 6, 2021
  • 1 reply
  • 1370 views

Hello all,

there following tracking log tables in adobe campaign:


 

trackingLogRcp, trackingLogVisitor - are clear to me
trackingLog - i understood/assumed this should be place to merge all of your tracking logs. Also this table somehow throws error since the day the instance was deployed

 


I assumed that all real time messages are saved to trackingLogRtEvent but they are logged to trackingLogEventHisto

 

Can someone help me out here as i could not find anything in the documentation

 

Thanks,

Marcel

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by SergeAs2

Hi Marcel,

 

nms:trackingLog schema is a template schema that trackingLogXXX schemas inherit from. Same applies for nms:deliveryLog. Hence it has no corresponding physical SQL table. TrackingLogs are not merged into a single table. You may refer to this page for a description of the datamodel.

 

Real-time events, broadlogs and trackings logs are stored in different tables depending on which instance you look at:

  • On the Real-Time execution instance:
    • RT events / broadlog / tracking logs: nms:rtEvent, nms:broadLogRtEvent, nms:trackingLogRtEvent
    • Batch events/ broadlog / tracking logs: nms:batchEvent, nms:broadLogBatchEvent, nms:trackingLogBatchEvent
  • On the Control instance (Marketing), all the data coming from RT is synced and consolidated via technical OOTB workflows into same tables regardless of batch or RT events:
    • Events / broadlog / tracking logs: nms:eventHisto, nms:broadLogEventHisto, nms:trackingLogEventHisto

Thanks,

Serge

1 reply

S
Adobe Employee
SergeAs2Adobe EmployeeAccepted solution
Adobe Employee
August 16, 2021

Hi Marcel,

 

nms:trackingLog schema is a template schema that trackingLogXXX schemas inherit from. Same applies for nms:deliveryLog. Hence it has no corresponding physical SQL table. TrackingLogs are not merged into a single table. You may refer to this page for a description of the datamodel.

 

Real-time events, broadlogs and trackings logs are stored in different tables depending on which instance you look at:

  • On the Real-Time execution instance:
    • RT events / broadlog / tracking logs: nms:rtEvent, nms:broadLogRtEvent, nms:trackingLogRtEvent
    • Batch events/ broadlog / tracking logs: nms:batchEvent, nms:broadLogBatchEvent, nms:trackingLogBatchEvent
  • On the Control instance (Marketing), all the data coming from RT is synced and consolidated via technical OOTB workflows into same tables regardless of batch or RT events:
    • Events / broadlog / tracking logs: nms:eventHisto, nms:broadLogEventHisto, nms:trackingLogEventHisto

Thanks,

Serge

    Terms & ConditionsAccessibility statement

    Loading footer...