Frakture’s bots will attempt to render elements such as the above by parsing source codes according to the syntax you supply us. However, each of the non-revenue elements above might be paired with an optional “Override” column, which is a human-editable column – it’s editable right there in the console Source Code Dictionary page – where you can correct the automated reading or supply missing elements.
Just type the preferred value into the Override field, and the equivalent element field will update in real time. For example, if bots have misinterpreted your code’s Goal as “Acquisition”, you can type into the Goal Override field a corrected value such as “Fundraising” – and you’ll see the Goal change accordingly. (As will any downstream reports that make calculations with the Goal element.)
Because Override values are lodged separately in the database from automated defaults, deleting an override entry will snap the code back to its bot-assigned default.
Adding a value to a transaction’s Source Override column will reassign that transaction to that specific source code in the Source Code Dictionary (and subsequently the Source Code Summary data tables). It will not alter that message’s attribution status if it is also assigned a Message ID.
Adding a value to a transaction’s Message ID Override column will change the message that transaction is assigned to for the purpose of Attributed Revenue calculation. Use this override if you are trying to correct revenue that is being attributed to the wrong message (e.g. email/ad/sms).
Every message can have multiple source codes attached to it. These source codes are used for transaction attribution with our last-click attribution algorithm.
One of the source codes is considered the Primary Source Code — it’s a first-among-equals source code that is used to categorize the statistics for the message. Frakture uses a set of heuristics to determine which of the potentially many source codes should be considered the Primary. In some cases, you may want to change the Primary Source Code — whether to change attribution, or change how a message is grouped.
Within the spreadsheet view of the Message table, you can override the Primary Source Code for a particular message. Entering a value in the Primary Source Override for a message (row) will:
(A) Attach that source code to the message, which can then be used for the attribution algorithm to assign transactions to it. This can sometimes take an overnight attribution cycle to complete.
(B) Assign that source code as the Primary Source Code for the message, to be shown up in reports, etc. This can also take an overnight cycle to complete.