About

MarTech Ledger is an independent, source-linked historical record of marketing platform releases, announcements and retirements. It is built and maintained by Andrea Veggiani, who has worked for 25 years on marketing strategy and technology architecture, with hands-on production experience on most of the platforms tracked here.

The two sites have different jobs. This one records what happened, with a source for every entry and no opinion. andrea.veggiani.com is where the interpretation lives: what a release means, and which architecture decisions it changes. Where one of those articles is really about a platform or a capability, its page shows it once, labelled as the author's view.

It is built for people who need the dated facts behind platform decisions: MarTech architects, implementation partners, analysts, and vendor product-marketing and competitive-intelligence teams. It is not a buyer's guide and does not rank or recommend platforms.

Disclosure

The author is a MarTech solution architect and holds active certifications on several of the platforms tracked here (among them Adobe, Braze, Bloomreach and Salesforce), and implements them for clients. MarTech Ledger is a personal project, not produced, funded or reviewed by any company or vendor.

That experience is why the record exists, and also why it is built so that it does not depend on anyone's opinion, including his:

• every platform is read by the same pipeline, from its own public release notes and documentation, with the same rules for states, dates and classification;
• entries are generated by AI from those sources and checked by automatic rules, not individually by a person, and are labelled as AI-generated (how AI is used);
• every entry links to public evidence, so it can be checked: product changes to vendor sources, signals under the source policy, which allows one documented exception;
• no vendor pays for, reviews or influences what is recorded, and the site carries no ads, sponsorships or lead generation;
• opinion stays on andrea.veggiani.com and is always marked as such when linked from here.

The aim is simple: a vendor-neutral, dated, verifiable answer to "what did this platform actually ship, and when?"

Product and company names, logos and trademarks belong to their respective owners. They are used only to identify the products recorded here; no affiliation with or endorsement by any vendor is implied.

What “Beta” means

The Ledger is open to everyone and still growing. The Beta label next to the name means:

• Coverage is still growing. 15 platforms, with release history from 1 January 2026. Sources and platforms may be added; what is read, and how often, is listed on Sources and Status.
• Methods can still change. The extraction rules, the capability taxonomy and the way states and dates are recorded are refined as the record grows. Every change to a published record is listed in Corrections, with the value before and after.
• Doubts stay visible. An entry with an open doubt is marked under review and left out of the Release Matrix and side-by-side views until it is resolved.
• Links stay stable. Feature pages keep their URLs; the old address of a merged or renamed record stays online and points to the current one.

The label will be removed when coverage and methods are stable.

Corrections

Anyone can contest an entry: readers, practitioners and vendors. Every feature page and every market signal has a Report an issue button. It opens a short form with the record ID, its state and its source already filled in: add what is wrong and, ideally, a link to better evidence. Your email address is optional and used only to reply about that report. Reports are delivered through Web3Forms, a form-processing service.

• Reports are checked against the public sources permitted by the source policy, with the same rules as every other entry. A vendor's word alone does not change a record; a public source does.
• A confirmed correction updates the entry in the next build and is listed in Corrections and on the record itself, with the value before and after, the reason and the evidence. The entry keeps the dates it was first recorded.
• While a report is being checked, the entry can be marked under review, which keeps it out of the Release Matrix and side-by-side views.

The Lifecycle history on a feature page lists recorded product states. Record last updated is the record's update date, not a review date. Corrections are listed separately under Record corrections and in the corrections register.

There are no public comments: the record stays a record.