Each source code in the Source Code Dictionary can encode a great deal of additional information about the solicitation that carried it: to whom was the solicitation targeted, for what purpose was it sent. Frakture provides standard names for common elements that might further describe a source code; our Level 2 service provides the ability to automate recognition of elements declared by your organization’s source code syntax(es) with human visibility and manual overrides.
The most commonly used are described in the Source Code Dictionary documentation page, but many additional fields are also available and might be used by your organization. They’re detailed in full below.
Apart from the date all source metadata is open-ended text that you’re free to use according to your own taxonomies. Suggested entries below are merely that – suggestions: unless specifically noted there is no menu of preferred or expected nomenclature required to optimize other components of the Frakture infrastructure. If you’re best served not by terms like “Holiday Fundraiser” but by shorthand abbreviations or numerical keys, use whatever suits you. The most important thing is to be consistent with these terms across different codes, because reports will break out counts and sums along the axes defined here.
An identifier for a specific client; intended for use by agencies and consultants who might service many distinct clients.
The responsible marketing entity. The converse of “Account”: it’s intended for use when the client has multiple vendors responsible for different projects, such as an ads shop and an email shop.
Channel for message delivery, such as SMS, Bing Ads, or Direct Mail.
YYYYMMDD format of the source code date. Sometimes different from the core message “publish date”, and usually obtained by automatically parsing the source code.
Frakture recommends a three-part campaign hierarchy – Campaign -> Message Set -> Message. While other elements can also be used for hierarchies, maintaining these three helps with standard roll-up reporting.
Name of the messaging campaign. Typically the top-level clustering of many related codes, often deployed over many different channels.
Name of the set of messages within a campaign – the Ad Set in online ads, testing sets for emails, etc.
The specific message variant in a message set. The exact individual Ad in an AdSet for online ads.