Marketo integration for learner marketing
Marketers run Marketo campaigns on learning activity. Intellum sends users and enrollments to Marketo every 12 hours, and Marketo campaigns can create or update Intellum users. An Intellum admin sets it up in Settings › Apps.
Common uses of the Marketo integration
- Customer marketers send coursework completion reminders through Marketo based on enrollment status.
- Demand gen managers market certifications to leads using completion data from Intellum.
- Marketing ops managers create Intellum accounts from Marketo form fills or list imports.
How the Marketo integration works
An admin adds a Marketo connection in Settings › Apps with the Munchkin ID, Client ID and Client Secret. Intellum checks the connection and pulls the available lead fields. Email matches users to leads by default.
With user sync on, mapped user fields export to leads. With enrollment sync on, enrollments arrive as a custom object linked to each lead. Both run every 12 hours. Admins can also turn on an inbound endpoint that Marketo smart campaigns call to create or update a user within seconds.
How to set up the Marketo integration
An Intellum admin connects Marketo, sets link fields, maps user fields and picks enrollment fields. The same admin can turn on the inbound endpoint and build the Marketo campaign that calls it.
- A Marketo account with REST API access
- Munchkin ID, Client ID and Client Secret from a LaunchPoint service
- An API user with lead read access and custom object permissions
How the Intellum and Marketo integration handles access and data
- Authorization: Marketo REST API credentials from a LaunchPoint service. Inbound calls from Marketo use an access token.
- Personal data: learner personal data, such as name, email, company and job title, moves to Marketo leads.
- Inbound calls: create or update users only. They do not change enrollments.
- Link fields: changing them after data exists creates duplicate leads, so set them before the first sync.
- Enrollment fields: changing them creates a new custom object version and leaves existing records as they are.
What to know about the Marketo integration
- Data moves every 12 hours, and large first exports can span several cycles.
- Enrollment data does not flow from Marketo into Intellum.
Questions about the Marketo integration
Yes. With the inbound webhook on, a Marketo smart campaign can create or update a matching Intellum user within seconds. It handles users only and does not sync enrollments into Intellum.
Users and enrollments. Mapped user fields such as email, name, company and job title export to Marketo leads, and enrollments arrive as a custom object linked to each lead, with status and key dates.
A Marketo account with REST API access and a LaunchPoint service, which provides the Munchkin ID, Client ID and Client Secret. The API user needs lead read access and custom object permissions.
Every 12 hours, with a 12-hour lookback, through Marketo bulk import. Large first exports can take several cycles to finish. Inbound user updates from Marketo arrive within seconds.
See the Marketo integration working with your stack
Walk through this integration, and the questions IT will ask, with an Intellum expert.