Offline-to-online sync layer for marketing automation tools

The moment that drives someone here is when they realize their in-store or offline campaign data — point-of-sale, event check-ins, loyalty redemptions — never makes it back into their marketing automation tool in time to influence the next send. They end up exporting CSVs manually, or running parallel systems that never fully agree with each other. One complaint puts it plainly: 'the online features are not connected to the offline side.'

This gap persists because the big marketing automation vendors are structurally focused on digital channel management. Offline touchpoints require warehouse integrations, POS connectors, and event data pipelines that vary by industry — unglamorous plumbing work that doesn't make a good product demo slide. So vendors gesture at it with 'custom integration' docs and leave implementation to the customer or a systems integrator.

What's currently wrong for this exact case: integrations 'are not straightforward in sandboxes,' which means even technically capable teams burn weeks testing connections that fall apart when systems update. There's no lightweight middle layer that normalizes offline event data into the shape that marketing automation tools actually ingest.

This is a business and not a feature because the offline data problem recurs every single day — a new transaction, a new event, a new redemption — and every break in the sync costs a marketer a window to re-engage a customer. A retailer running loyalty campaigns is losing attribution and suppression accuracy continuously, not once. The buyer is an ops or marketing technology team that's already paying for the automation tool and getting less than half the value because the data feeding it is incomplete.

What to build

Build a connector service that ingests offline event streams — POS transactions, loyalty redemptions, event check-ins — normalizes them into a standard contact-activity schema, and syncs them on a configurable schedule into Adobe Campaign, with a mapping UI that doesn't require engineering to maintain.

Where to start

Start with Adobe Campaign users running loyalty programs in the cannabis or specialty retail vertical, where offline-to-online suppression (don't email someone who just bought in-store) is a concrete, measurable revenue problem with a short feedback loop.

The hard part

Every retailer's POS system is different, so the first painful trade-off is deciding whether to build three deep connectors (Square, Lightspeed, Oracle MICROS) and say no to everything else, or build a generic CSV/webhook ingestion layer that works everywhere but requires more setup from the customer.

How it makes money

Monthly subscription priced per number of offline event records synced per month, with a setup fee for custom POS connector work.