← Back to selected work

From marketing lead to sales follow-up.

Connecting selected APAC leads to the global Salesforce workflow, with consistent data and a clear next step for sales.

My roleEnterprise Software Engineer
UsersMarketing operations & sales teams
FocusMarketo–Salesforce integration

PRODUCT MISSION

Help regional marketing leads become actionable follow-up for global sales teams.

Problem & goal

Pharmaceutical leads from APAC needed to be available in both the regional system and the global Salesforce organization for follow-up and revenue tracking. The standard Marketo sync already existed, but did not cover this particular cross-region workflow.

The goal: automate the missing connection while preserving the global team’s existing business rules.

Solution

A targeted integration through IBM Integration Bus and Salesforce REST APIs. It validates and maps incoming data, attaches a follow-up task to an existing contact, or creates a new lead and task when needed.

User journey

From regional marketing to global sales follow-upAPAC marketing sends selected pharmaceutical leads from Marketo to the global Salesforce workflow. The integration validates and maps the data. If a contact already exists, it adds a follow-up task to that contact. Otherwise, it creates a lead and a task. Invalid requests return errors for correction and reprocessing.APAC marketingSelected pharma leadsGlobal salesFollow-up in CRMGLOBAL SALESFORCE WORKFLOWMarketoSend lead dataValidate & mapCheck required fieldsExistingcontact?YesAdd taskTo the contactNoCreate lead + taskReady for sales follow-upInvalid dataReturn a clear errorCorrect the data, then reprocessFrom regional marketing to global sales follow-upAPAC marketing sends selected pharmaceutical leads from Marketo to the global Salesforce workflow. The integration validates and maps the data. If a contact already exists, it adds a follow-up task to that contact. Otherwise, it creates a lead and a task. Invalid requests return errors for correction and reprocessing.APAC marketingSelected pharma leadsMarketoSend lead dataValidate & mapGlobal Salesforce workflowExistingcontact?YesNoAdd taskTo the contactCreate leadAnd a taskReady for global sales follow-upIf data is invalid:Return an error → correct → reprocess
Simplified business flow. The custom integration connects a specific regional lead flow to the global team’s existing rules.

My role

I defined data contracts and built the Salesforce REST API used by the integration. My work covered field mapping, required-field validation, lead-processing logic, and error logging.

Decisions

Extend the established sales workflow.

The incoming leads needed to fit the way the global team already worked. We retained those business rules and added a targeted regional connection.

Agree on the data before moving it.

Field mappings and required values became an explicit contract between systems. Validating the payload at the boundary helped keep incompatible or incomplete records out of the workflow.

Give failed records a clear next step.

Error logging and explicit success or failure responses helped the teams identify records requiring correction and reprocessing.

Impact

The integration automated a previously manual path for selected regional leads and supported Salesforce workflows serving 400+ sales representatives. Follow-up could use the global team’s expected records and tasks.

400+ describes the sales population served, rather than measured adoption or a conversion increase.

How I would measure the handoff

Track valid leads arriving successfully, time from marketing submission to a sales task, duplicate creation, and unresolved integration errors. These are proposed measures; no conversion lift is claimed.

What I took away

A useful integration carries the meaning of the workflow along with the data: what counts as a valid lead, when to reuse a record, and who needs to act next.