Oracle PeopleSoft and Marketo integration

What moves between them

Employee and company records flow from Oracle PeopleSoft into Marketo. ml-connector polls Oracle PeopleSoft's employee directory service to fetch employee records with hire dates, titles, departments, and company assignments. Those employee records are mapped to Marketo Leads and Sales Persons with corresponding names, job titles, and company associations. Company and vendor master data from Oracle PeopleSoft are synced to Marketo Companies so prospect and account lists stay current. The sync runs on a schedule tied to your payroll and HR cycles, ensuring Marketo reflects the latest organizational structure without manual data entry.

How ml-connector handles it

ml-connector stores both Oracle PeopleSoft and Marketo credentials encrypted and handles the authentication differences between them. For Oracle PeopleSoft, it accepts the customer-specific hostname, port, and node name since each installation is self-hosted and unique, and it uses either HTTP Basic Auth or OAuth2 bearer tokens depending on the PeopleTools version. For Marketo, it manages the Munchkin ID and OAuth2 client credentials, refreshing the bearer token when it approaches expiry. ml-connector polls Oracle PeopleSoft on a schedule to retrieve employee directory and company records, filtering by date ranges to retrieve only recent changes. Each batch is mapped to Marketo Leads and Companies according to your field mapping, then written to Marketo in batches of up to 300 records per request. If Marketo returns rate-limit responses (HTTP 429), ml-connector backs off and retries. Because Oracle PeopleSoft's REST endpoints are read-only inquiry operations, the sync is one-directional, and every record carries a full audit trail and deduplication key so records can be replayed if a write to Marketo fails.

A real-world example

A mid-market B2B software company uses Oracle PeopleSoft to manage its global employee directory and company information across multiple operating entities. The sales and marketing teams use Marketo to manage leads, companies, and marketing campaigns. Before the integration, the marketing team manually exported employee lists from Oracle PeopleSoft and imported them into Marketo each month, leading to stale contact records and lost sales opportunities when employees changed roles or left the company. With Oracle PeopleSoft and Marketo connected, new employee hires flow into Marketo automatically within hours of their hire date in Oracle PeopleSoft, updated titles and department assignments keep account relationships current, and terminations are removed from Marketo's sales person list so outreach stops going to invalid contacts.

What you can do

• •Sync employee records from Oracle PeopleSoft as Marketo Leads and Sales Persons with names, titles, departments, and company associations.
• •Map company and vendor master data from Oracle PeopleSoft to Marketo Companies so prospect and account lists stay current.
• •Poll Oracle PeopleSoft on a schedule tied to your HR and payroll cycles, capturing only recent changes with date-range filtering.
• •Handle Oracle PeopleSoft's self-hosted authentication (HTTP Basic Auth or OAuth2) and Marketo's OAuth2 client credentials, with automatic token refresh.
• •Track every record in a full audit trail with deduplication and replay capability when a write to Marketo fails.

Questions

Which direction does data move between Oracle PeopleSoft and Marketo?

Data flows from Oracle PeopleSoft into Marketo. Employee records, job titles, departments, and company master data sync from Oracle PeopleSoft to Marketo as Leads, Sales Persons, and Companies. Because Oracle PeopleSoft REST endpoints are read-only inquiry operations, the integration is one-directional and does not write data back into Oracle PeopleSoft.

How does ml-connector handle Oracle PeopleSoft's self-hosted architecture?

ml-connector accepts the customer-specific hostname, port, and node name for each Oracle PeopleSoft installation, since each customer deploys their own unique environment on premises or on Oracle Cloud Infrastructure. It authenticates with either HTTP Basic Auth (OPRID and password) or OAuth2 bearer tokens depending on the PeopleTools version, and it polls the employee directory and company service operations on a schedule to retrieve changes.

What happens if Oracle PeopleSoft returns a large result set when polling for changes?

ml-connector filters Oracle PeopleSoft queries by date ranges so that only recent employee and company changes are retrieved in each poll. This prevents oversized result sets and ensures the sync stays current. Field mappings between Oracle PeopleSoft employee entities and Marketo Leads and Companies are configured per customer so the correct job title, department, and company associations flow through on every sync.