Want to know if this job is worth applying to?
Bengaluru, Karnataka, India
Onsite
WPP Enterprise Solutions designs, builds, and operates the growth systems that competitive businesses rely on. In a world where Al is reshaping how companies drive growth, we lead clients in business transformation and marketing modernization, connecting strategy directly to execution. Our 12,000 experts in engineering and platforms, commerce, consulting, content transformation, CRM, and CX work within a unified global operating unit across 40+ markets. WPP Enterprise Solutions works alongside best-in-class partners including Adobe, AWS, Braze, Google, Microsoft, Salesforce, and Shopify, as well as innovators in AI, to deliver growth solutions tailored to the needs of our clients’ businesses. VML, part of WPP, supports WPP Enterprise Solutions by helping brands activate transformation through creativity and experience.
We seek Senior Consultants and Architects with deep, hands-on expertise in Adobe Campaign Classic (ACC), Adobe Campaign Standard (ACS), Adobe Experience Platform (AEP), and Adobe Journey Optimizer (AJO) to help enterprise customers modernize campaign and customer-journey programs. The role leads discovery, current-state assessment, target-state architecture, implementation, integration, testing, coexistence, cutover, and enablement. You will understand how customers use ACC or ACS today, identify use cases suited to AJO, and redesign them for AEP and AJO. Some functionality must be rebuilt, redesigned, retained, or handled through an integration or alternative solution. Candidates must explain product boundaries, assess feature and use-case fit, surface gaps early, and set realistic customer expectations. In AJO, a migrated use case lands on AJO Journeys (profile-centric, event-driven orchestration on AEP Real-Time Customer Profile) or AJO Orchestrated Campaigns (campaign-centric, batch, multi-step workflows on the AEP relational data store). Candidates must design and build on both, and recommend the right path per use case.
· Lead discovery workshops with marketing, campaign operations, data, architecture, security, mobile, and IT stakeholders.
· Inventory the Campaign estate: use cases (batch, scheduled, transactional, event-triggered, real-time); assets (campaigns, workflows, audiences, deliveries, templates, content blocks, personalization, typologies, suppression rules, reporting); data (schemas and extensions, custom resources, relational data, targeting dimensions, identifiers, consent, opt-out, quarantine, bounce, engagement history); and infrastructure (on-premises or Managed Services hosting, network access, firewalls, file transfer, decommissioning needs).
· Reverse-engineer custom logic and document the business rules: technical and marketing workflows (query, enrichment, split, deduplication, reconciliation, update data, JavaScript code activities), custom JavaScript, JSSP, SOAP/JS API calls, SQL functions, stored procedures, custom relational structures, typology rules, input forms, web applications, landing pages, subscriptions, Message Center, Triggers/pipeline, offer logic, external accounts, APIs, middleware, and enterprise integrations.
· Map each use case and dependency to an AJO/AEP target pattern and classify it as reuse, redesign, rebuild, integrate, defer, or retain elsewhere. For custom logic, decide whether to re-express it in AEP/AJO (data model, Query Service, custom actions, external services), redesign or rebuild it separately, or retain it in Campaign.
· Choose the execution path per use case based on the target customer experience, not the shape of the source Campaign workflow. Use AJO Journeys when each profile should progress individually based on behaviour, events, or elapsed time, including many scheduled and recurring Campaign workflows rebuilt as Read Audience or business-event journeys. Use Orchestrated Campaigns for relational or multi-entity data, complex audience construction and enrichment, exact pre-send counts, and multi-level sending. Use action campaigns for simple scheduled or API-triggered sends. Document the rationale, combined patterns, and license prerequisites (e.g., the Journey Optimizer Campaigns package).
· Surface product-fit gaps and operational impacts before committing to scope or feature-parity claims. Advise when Campaign coexistence or another path fits better: Campaign v8 for ACC customers, or the ACS-to-Campaign v8 transition for ACS customers.
· Develop phased roadmaps, effort estimates, dependency plans, risks, and customer decision points.
· Design the AEP foundation: XDM schemas and field groups (profile, event, lookup); identity namespaces, identity resolution, profile enablement, and data relationships; datasets, sources, destinations, batch and streaming ingestion, and event design; data quality and governance; audience qualification and segmentation; and Query Service or other processing for transformation, aggregation, and enrichment.
· Replace common Campaign data patterns with AEP capabilities: Federated Audience Composition on Snowflake, Google BigQuery, Databricks, or other warehouses (closest to ACC Federated Data Access); computed attributes for profile-level aggregates; Data Distiller for scheduled SQL transformations; merge policies; and profile and segmentation guardrails.
· Design customer experiences and build AJO journeys and campaigns across batch and event-driven engagement: event- and segment-triggered orchestration, conditions, actions, custom actions, message content, personalization, and decisioning.
· Apply journey and campaign governance and optimization: business rules, frequency capping, quiet hours, journey priority and arbitration, conflict management, wave sending, content experimentation, and decisioning policies and rankings.
· Define security, access, permissions, governance, and operational controls.
· Configure AJO channels end to end: email, mobile and web push, in-app, web, code-based experiences, content cards, inbox, live activities, SMS/MMS, RCS, WhatsApp, LINE, and direct mail. Cover channel configurations, subdomains, API credentials, feedback webhooks, mobile app and SDK dependencies, channel-specific data and consent requirements, and template approval rules (e.g., WhatsApp/Meta).
· Connect messaging providers: native SMS providers (Sinch, Twilio, Infobip); bring-your-own-provider (BYOP) setups with provider payloads, inbound keyword handling, delivery receipts, and opt-in/opt-out webhooks and flows; and Channel Builder custom channels for non-native platforms or customer-owned gateways (e.g., regional or industry-specific providers), covering endpoint, authentication, throttling, payload structure, and monitoring.
· Design and build integrations using supported APIs, source connectors, file exchange, middleware, or Adobe solution integrations, including custom actions that call external systems from journeys (CRM, loyalty, order, recommendation, call-center, notification services) with request/response schemas, authentication (OAuth 2.0, API keys, mTLS), capping, throttling, retries, and error handling.
· Implement event and API-triggered patterns: unitary and business events, API-triggered and transactional campaigns, Interactive Message Execution / Journey and Campaign APIs, and streaming ingestion via HTTP API.
· Select and configure the journey entry pattern per use case: unitary-event journeys for behavioural and transactional signals; audience qualification journeys on streaming audiences for real-time lifecycle moments; Read Audience journeys, one-shot or recurring with incremental read, for scheduled and batch-initiated programs that previously ran as recurring Campaign workflows; and business-event journeys that release an audience when an operational event occurs (e.g., a price drop or flight delay). Configure identity namespaces, reentrance and wait periods, exit criteria, and time zones.
· Build multi-step journeys where each customer progresses at their own pace: Wait activities; the Optimize activity for conditions, path targeting, and path experiments; reaction events on opens and clicks with timeout paths; Update Profile; Content Decision for offers; external data sources and custom actions for real-time lookups and system writebacks; and Jump activities to split complex programs into reusable journeys.
· Use supplemental identifiers (e.g., order, booking, subscription, or policy IDs), where enabled, to run one journey instance per entity and personalize with its attributes. Decide when per-entity use cases fit journeys versus orchestrated campaign multi-level sending.
· Support phased migration and coexistence from the journey canvas, including Adobe Campaign v7/v8 and ACS actions that let AJO orchestrate while Campaign transactional messaging delivers, until channels and content move to native AJO.
· Design within journey guardrails (one active instance per profile per journey, one Read Audience per journey and concurrent-run limits, entrance and processing throughput per sandbox, Jump and supplemental identifier restrictions, reaction event placement, custom action capping, and versioning impact on live profiles). Flag gaps to the customer early.
· Design the data model with AEP relational (model-based) schemas, built manually or from a DDL or Excel upload: tables, primary and composite keys, version descriptors (e.g., lastmodified), ENUMs, data governance labels, identity fields mapped to identity namespaces, and links with correct cardinality (1-N, N-1, 1-1) to recipient and profile entities.
· Configure target dimensions, including the profile target dimension linking XDM profile and experience event data to relational data; decide what belongs in the profile store versus relational tables to avoid duplication.
· Set up Change Data Capture (CDC) ingestion from supported sources (e.g., Amazon S3, Google Cloud Storage, SFTP, Snowflake, Google BigQuery, Azure Databricks, Data Landing Zone): the _change_request_type field for file-based loads, table logging for cloud warehouses, complete-record loads, deletion handling, and latency planning.
· Build multi-step canvases with targeting, flow control, and channel activities (Build, Read, and Save audience, Enrichment, Change dimension, Combine, Deduplication, Reconciliation, Split, Fork, AND-join, Wait, Alert), including multi-entity segmentation and multi-level sending (e.g., one message per booking, contract, subscription, account, or address linked to a profile) personalized with enriched relational attributes. Configure scheduling, recurring runs, and pre-send count validation.
· Design within orchestrated campaign guardrails (table count and schema size limits, daily change-volume limits, scalar-only audience attributes, uncached audience evaluation, permanent dataset table names, channel availability by license). Flag gaps to the customer early.
· Translate the ACC/ACS relational data model to AEP: map recipient, custom, and relational tables to XDM profile, experience event, and lookup schemas, or to relational schemas for orchestrated campaigns; define primary and secondary identities, relationships, cardinality, and denormalization trade-offs.
· Migrate historical and operational data (profile attributes, subscriptions, consent and opt-out status, quarantine and bounce history, engagement data) via batch backfill, delta loads, and reconciliation reports. Map ACC/ACS denylist and subscription data to the AEP Consent and Preferences field group and AJO subscription lists; load quarantined and bounced addresses into the AJO suppression list via the Suppression API so blocked recipients stay blocked from day one.
· Rebuild Campaign workflow logic according to the chosen path. For journeys, express targeting as AEP audiences (batch, streaming, or edge) and computed attributes, recurring workflows as scheduled Read Audience journeys, and waits, splits, and tests as Wait and Optimize activities. For orchestrated campaigns, rebuild queries, enrichments, splits, union/intersection/exclusion, deduplication, change dimension, and reconciliation as canvas activities. Use Query Service (SQL/CTAS) jobs or source dataflows for scheduled imports/exports and data preparation. Move logic neither canvas supports (JavaScript activities and code, SQL code, loops, file manipulation) to the source system, Query Service or Data Distiller, or external services.
· Re-architect lifecycle programs (welcome, onboarding, renewal, win-back, abandonment) built in Campaign as chained or recurring workflows into journeys, replacing workflow-based state tracking (custom flags, prior-recipient exclusion lists, wait loops) with journey state, reentrance rules, and exit criteria.
· Convert ACC/ACS HTML content, templates, and personalization (<%= %> scripting, JavaScript in content, personalization blocks, conditional content) to AJO content templates and Handlebars/PQL: helper functions, conditional and dynamic content, expression and visual fragments, and decisioning outputs. Validate matching output with seed and test profiles.
· Map Message Center, Triggers/pipeline, and other transactional or signal-driven flows to AJO unitary-event journeys or API-triggered campaigns, and typology, pressure, and fatigue rules to AJO business rules, frequency capping, suppression rules, and quiet hours.
· Migrate ACC Interaction offer logic (catalogs, categories, eligibility rules, weights, typology and presentation rules, inbound and outbound environments) to AJO Decisioning: decision items,
collections, selection strategies, ranking formulas or AI models, and capping. Confirm whether the customer is licensed for Decisioning or legacy Offer Decisioning.
· Rebuild Campaign landing pages, subscription and preference centers, web and survey forms, ACC web applications, and JSSP pages as AJO landing pages, subscription lists, or customer-owned web front ends connected through AEP APIs, writing consent and preferences back to AEP.
· Establish development, test/stage, and production delivery practices with Git version control and a sandbox strategy. Support controlled promotion and release management with AEP sandbox tooling packages (schemas, audiences, journeys, content templates), journey versioning, simulation, and dry-run checks before publishing.
· Build requirements-traceable test strategies and plans covering data and identity validation, audience counts, journey logic, personalization, rendering, API behavior, consent, suppression, channel delivery, and reporting.
· Design dual-run and cutover plans, synchronizing and reconciling consent, opt-outs, quarantine, bounces, profile data, and engagement history as needed.
· Plan deliverability readiness and email domain migration: subdomain delegation (full or CNAME), SPF, DKIM, DMARC, BIMI, one-click List-Unsubscribe headers, Gmail/Yahoo bulk-sender requirements, IP pools and strategy, ramp-up and warm-up, bounce, quarantine, suppression, and opt-in/opt-out handling, and operational monitoring and reporting.
· Rebuild Campaign reporting and tracking with AJO built-in journey and campaign reports, Customer Journey Analytics where licensed, and Query Service on AJO system datasets (message feedback, email tracking, journey step events). Agree with the customer which ACC reports, KPIs, and tracking logs need equivalents.
· Define measurable launch and migration acceptance criteria; support business validation, production readiness, go-live, stabilization, and continuous improvement.
· Hand over with implementation documentation, architecture diagrams, reproducible data mapping specifications, runbooks, testing evidence, and operational and support materials; coach customer teams on the AJO operating model, AEP concepts, changed workflows, new responsibilities, and adoption needs.
Alongside the opportunity to work with some of the most exciting brands around the world, we’ll also prioritise your career development and help you grow your skills. We’ll empower you to make a difference, allow you to be yourself, and respect who you are.
Our culture thrives on our core values, designed for impact-driven individuals: Heart, Brains and Courage.
We lead with Heart, fostering empathy and trust where genuine connections and human-centric work flourish.
We empower your Brains for innovation, valuing relentless curiosity and collaborative intelligence to solve complex challenges.
And we champion Courage, inspiring you to speak up, embrace experimentation, and advocate for bold solutions that push our thinking to be better than yesterday.
WPP is the trusted growth partner for the world’s leading brands. With exceptional talent, trusted data and intelligence and world-class partnerships – all united by our agentic marketing platform, WPP Open – we help clients navigate change, capture opportunity and deliver transformational growth. For more information, visit WPP.com.
WPP (VML/WPP Enterprise Solutions) is an equal opportunity employer and considers applicants for all positions without discrimination or regard to characteristics. We are committed to fostering a culture of respect in which everyone feels they belong and has the same opportunities to progress in their careers.
When you click "Submit Application", this will send any information you add below to WPP (VML/WPP Enterprise Solutions). Before you do this, we think it's a good idea to read through our Recruitment Privacy Policy. California residents should read our California Recruitment Privacy Notice. This explains what we do with your personal data when you apply for a role with us, and, how you can update the information you have provided us with or how to remove it.
