Omnichannel marketing

The challenge.

A marketing journey crosses campaign tooling, customer data, channel vendors, delivery feedback, and support history. Each channel needs its own execution path while remaining understandable as one lifecycle.

My contribution.

Worked across Adobe marketing integrations and supporting engineering for email, SMS/RCS, direct mail (DM), outbound telemarketing (OTM), and push notifications.

Implementation.

• Email: integrate transactional requests with Message Center SOAP payloads, campaign event processing, BCC content capture, and sent/open/click/bounce history.
• SMS and push: work across channel payloads, transactional dispatch, preference/quiet-hours integration points, and downstream messaging adapters.
• Direct mail: support Adobe Campaign JavaScript workflow automation, attribute/file validation, vendor-file generation, deduplication, rollback, and contact-history processing.
• OTM: support vendor-setting lookups, encryption-manifest generation, encrypted-file handoff, notifications, and passback/history pipelines.
• Connect Adobe exports and events with AWS services, Databricks transformations, operational monitoring, and communication evidence.

Design decisions.

Digital API dispatch and offline vendor-file handoff require different execution and recovery mechanisms; they share event tracking rather than one universal sender.

Campaign configuration, integration code, vendor execution, and communication history are separate responsibilities with explicit contracts.

Validation.

Channel-specific validation combines payload checks, file validation, source-to-target reconciliation and workflow testing.