What Your Subscription System Should Connect To

Ask a subscriptions team to draw their systems on a whiteboard and you usually get the same picture. The subscription system sits in the middle, with half a dozen arrows coming off it. Some of those arrows are proper connections. Some of them are a person, a spreadsheet and a Tuesday morning.

Nobody needs every arrow to be an API. But you do need to know what each one is, which way the data goes, and what happens when it stops. That's what this post is about.

Start with one rule

Every piece of data should have one owner. The subscription system owns subscriptions, entitlements and the circulation record. The payment gateway owns card details. The email platform owns send and open data. The accounts package owns the general ledger.

Problems start when two systems both think they own the same thing. If your email platform and your subscriber file each keep their own list of who has unsubscribed, they will disagree. If finance and circulation each keep their own list of who has paid, month-end becomes an argument.

So for each connection below, the question isn't just "can these two talk?" It's "which one is right when they don't match?"

Payments

Card payments usually come in through a gateway. The gateway holds the card, and the subscription system should hold the order, the payment reference and whether it succeeded. You shouldn't store card numbers yourself, and a good connection means you don't need to.

What matters is the round trip. A payment taken on the website has to create or extend the subscription. A failed renewal payment has to show up against the subscriber, so someone can chase it before access or copies stop. Direct debit has the same shape, with collections and failures coming back from your provider. We've written separately about direct debit and continuous card payments.

Website, paywall and apps

This is the connection readers notice first. The website should ask the subscription system who's entitled to what, rather than keeping its own list. We covered it in detail yesterday in linking your paywall to the subscription file, so the short version here: one source of truth, a live lookup where you can, and only the data the website needs.

If you sell auto-renewing subscriptions to consumers, the website link also carries cancellations. Under the new rules, a reader who signed up online must be able to end the subscription online, and that has to reach the subscription system rather than sit in an inbox. Our guide to the subscription rules has the detail.

Email marketing

Most publishers send email from a dedicated platform, and the list comes from the subscriber file. That part is easy. The part that goes wrong is the return journey.

Unsubscribes and objections have to come back. The ICO is clear that people have "an absolute right to stop you using their information for direct marketing" (ICO guidance on the right to object). If someone unsubscribes in the email platform and the next list you send comes fresh from the subscriber file, they're back on it. The ICO's guidance on electronic mail marketing expects you to keep a "do not contact" list of anyone who opts out.

So make sure opt-outs land on the subscriber record, and that every selection checks them before export. Bounces are worth bringing back too. A hard bounce is often the first sign a B2B reader has changed job.

Mailing house and printer

For print titles, the mailing file is the most important file you send. It's also the one most likely to travel by email attachment, which is the worst way to send a list of names and addresses.

Use secure file transfer instead, with the file produced straight from the subscription run, not tidied in a spreadsheet on the way. Keep a record of exactly who was in each file, so a missed copy query or an audit question can be answered later.

A mailing house handling your subscriber data is acting on your behalf, and the ICO says that when a controller uses a processor, "there must be a written contract that binds the processor" (ICO guidance on controller and processor contracts). That contract should cover security and what happens to the data when the work ends. It's worth checking yours is in place and up to date.

Finance and the accounts package

Finance needs invoices, payments, credit notes and deferred revenue from the subscription system. Usually this doesn't need a live connection. A clean, regular export that ties back to the sales ledger is often better than a clever integration nobody understands.

What matters is that the numbers reconcile. Cash received in the gateway should match payments in the subscription system, which should match what finance posts. Our post on the month-end subscriptions pack goes through what to include.

Reporting and BI

Dashboards are best built on a copy of the data or a reporting connection, not by running heavy queries against the live system. That keeps the subscription system quick for the people using it, and stops a big report from getting in the way of a renewal run.

Keep every connection tight

Each connection is a door into personal data, so a few habits apply to all of them:

  • One key per system. If the website, the email platform and a reporting tool all use the same login, you can't turn one off without breaking the others.
  • Only what's needed. A paywall needs entitlements, not addresses. A mailing house needs addresses, not payment history.
  • Read-only where you can. If a system only needs to look things up, it shouldn't be able to change a subscription.
  • Logged. You should be able to see what each connection asked for, and when.

The worst integration failures are the quiet ones. The nightly sync that stopped three weeks ago. The unsubscribe feed that broke after a password change. Nobody notices until a reader complains.

For each connection, decide who gets told when it fails and how. Then test the awkward cases before go-live and again after any change: a renewal, a failed payment, a cancellation, an unsubscribe, a change of address. Check each one turns up where it should.

Where we fit in

Avio, our subscription platform for larger publishers, has a read-only REST API for websites and paywalls, with scoped keys, rate limits and every call logged. We've connected it to card payment gateways, CRM systems and email platforms, and set up secure file transfer to fulfilment and mailing houses. Most day-to-day data leaves Avio as exports from saved selections, with a run history of who was in each file.

In Adeptis, our all-in-one platform for smaller publishers, orders paid through Stripe on your public sites come in for review, and subscription runs and selections export to CSV for your mailing house or email platform.

If you'd like to go through your own whiteboard of arrows, get in touch and bring the list.

Rob Sherwood

Rob Sherwood is Managing Director of Adept Data Services. He has spent his career in subscriptions and circulation, at WDIS, Optima and CDS Global before founding Adept.

More about Rob at rob-sherwood.co.uk

Talk to people who know publishing

Tell us what you're trying to fix. You'll speak to someone who has run circulation and subscriptions for a living, not a sales script.