Every action and interaction made by your project is written to a log file. It’s a very detailed file and you can use it for debugging, tracing and analysis.
If you click to Export the Project Activity, a CSV file will be downloaded for opening in Excel or any other spreadsheet program.
The exported project activity data is structured into columns like this:
The columns are:
Date & Time - date and time (in GMT) that the event happened
Process ID - every new sequence of events is given a unique Process ID. Every sequence starts with an incoming message or a trigger.
Connected ID - this is the Process ID of a related sequence of events. For example, let’s say an email arrives, fires a trigger that adds points to the sender and then a Watch trigger fires when points are incremented. The arriving email will create a unique Process ID and so will the Watch trigger – so we’ll have two Process IDs for the two chains of events. These sequences are related and hence the Watch trigger sequence will show the arriving email Process ID as a Connected ID.
Status - this is either activated or ignored. Ignored is used for conditions if the condition is false and whenever there is an error.
Audience ID - this is the unique ID for the audience member, if it’s known. Note that when a message fire arrives, an entry is written to the log file but the audience ID isn’t know yet until the next step of processing.
Audience Detail - if it’s known then this is the audience member’s account used.
Type - this is category of event such as SMS, trigger, call etc.
Action - the action taken by Conducttr.
Character - the character, if relevant that received or sent the message.
Value - extra details that relate to the event. In the case of:
- message: this is the Character account used
- change value: this is the amount and source of the change
- condition: this is the amount and source of the comparison
Attribute - this is what’s being affected or is affecting the result. In the case of:
- outgoing message: this is the alternative used
- incoming message: this is the message text (for emails this is the Subject)
- change value: this is the Attribute changed
- condition: this is the Attribute being compared to the Value
- for triggers: this is the matchphrase
Result - this is the result of the action. In the case of:
- outgoing message: this is the content ID
- change value: the new value of the Attribute
- conditions: whether the comparison was true or false
- group actions: this is the new group membership (could be empty in the case of Remove from group)
Logic - only used for Triggers and Actions. This is the trigger id or action id
Title - title of the entity given by you
Beat - if known, the beat to which this event is related
Scene - if known, the scene to which this event is related
Msg ID - this is used for outgoing messages and gives “proof” that the message was delivered. The message id is generated by the receiving system (i.e. twitter, facebook, email domain) and written here to allow Conducttr Support to trace a message.
Remarks - if something goes wrong then the error message will be written here
Note that regardless of the time zone of your project, dates and times are stored in the log file as GMT. This means that the data you're looking for may be in the calendar day before or after the date you want to investigate.