Written by: Michał Sobieraj, Operations Manager, Digital Colliers
Substack shipped a feature last week that flags which newsletters on the platform are AI-written. Readers can now see, at the publication level, whether a human sat down and typed the thing. That's a small product change with a large downstream implication: provenance is starting to migrate from a paid-media compliance concern into an owned-channel expectation.
If you run lifecycle email for a retail brand, you don't have that signal yet. Your ESP doesn't tell subscribers which sends were drafted by a model, edited by a copywriter, or spat out of a template with dynamic blocks. Your internal team doesn't have it either. That gap is going to matter sooner than most brand teams think.
Owned channels are where the pressure lands next
Paid acquisition has been getting more expensive for two years running. DTC customer acquisition costs are up roughly 40% since 2023, and Meta CPMs have kept climbing through 2024 and into 2025. UK eCommerce grew about 3% in 2024, so the top line isn't bailing anyone out either.
When acquisition gets that expensive, retention email and SMS carry more of the revenue. That's exactly the moment your subscriber list becomes a governance surface. If a reader can tell your welcome flow was generated by the same model that writes half their LinkedIn feed, the channel loses the thing that made it worth defending.
What a content ledger actually looks like
Most brands can't answer basic questions about their own sends. Who drafted this subject line. Which model, if any. Was the body block human-reviewed or auto-approved. What prompt template produced the product description that got pulled into the hero.
The minimum data model isn't complicated. For every content object that ends up in a send, you want:
- A source field: human, model-assisted, model-generated
- The model name and version if applicable
- The prompt template ID or copywriter ID
- A reviewer ID and timestamp for the last human edit
- A confidence or QA state before the block is eligible for send
That's five fields. You attach them at the CMS or PIM layer, not at the ESP. The ESP just reads them. When a legal, brand, or eventually a regulator question shows up, you can answer it in a query rather than a Slack archaeology session.
The regulatory clock is already running
This isn't only a brand-trust argument. The EU AI Act's Article 50 transparency obligations apply from 2 August 2026, and they cover AI-generated content that interacts with people. High-risk obligations kick in from 2 December 2027, with fines reaching up to €15M or 3% of global turnover for serious violations. If your lifecycle program touches EU subscribers, and it almost certainly does, you're going to need to demonstrate what was model-generated and how it was disclosed.
The pattern I keep seeing: brand teams assume their ESP vendor will handle this. ESPs are not going to handle this. They don't own the content, they don't own the drafting workflow, and they have no visibility into which Notion doc or Figma frame the copy came from. The ledger has to live on your side.
What the left-behind risk actually looks like
Public estimates now put a meaningful share of long-form content on platforms like LinkedIn as AI-generated. Wherever that number lands, the direction of travel is one-way. Readers are getting better at spotting model prose, platforms are starting to label it, and the brands that can prove human authorship (or disclose model authorship cleanly) are going to look qualitatively different in the inbox by mid-2026.
Brands that don't build the ledger will find themselves in one of two spots. Either they can't disclose because they don't know, which is a regulatory problem. Or they disclose everything as model-generated because that's the safe default, which is a brand problem. Neither is where you want to be when acquisition math is already tight and roughly 30% of SKUs at a typical multi-channel brand lose money per order after returns and ad spend.
Where to start this quarter
You don't need a platform to begin. A shared table with the five fields above, wired into whichever tool your copy team already uses, is enough to start capturing provenance on new sends. Backfilling last year's campaigns is a separate project and probably not worth doing. What matters is that from the next send onward, you can answer the question a regulator, a journalist, or an unusually observant subscriber is going to ask.