Connect Bevy to Marketo with API credentials so member and chapter changes update Marketo leads. A community admin creates three custom lead fields in Marketo, then enters the Marketo client ID, client secret, and Munchkin account ID under Settings → General.
Membership tracking uses the Marketo REST API. Bevy creates or updates a Marketo lead by email and can push mapped profile fields plus the custom fields below. For how this option fits with Munchkin and event programs, see Marketo integration - Introduction.
Before you start
- Have Marketo Admin access so you can create custom lead fields and a Custom Service (client ID and client secret with read/write access).
- Copy your Munchkin account ID (format like
123-ABC-123) from Marketo Admin. - Confirm you can open Settings → General in Bevy as a community admin. If the Marketo section is missing, contact your Customer Success Manager or Bevy Support.
Note: Social features in Marketo are recommended so social profile fields can map cleanly. Use Marketo’s documentation for Custom Service setup and social features if those Admin paths have moved in your Marketo experience.
Create custom lead fields in Marketo
Create these custom lead fields before you turn on membership tracking. Use the API names below unless your Bevy team remapped them.
| Marketo field (API name) | Type | What Bevy writes |
|---|---|---|
webServicesAPISource |
String | Always Bevy on each lead push. |
bevyUserGroupIDs |
String | Comma-separated numeric chapter IDs for the member’s active chapters. When someone leaves a chapter, Bevy removes that chapter ID from the list. |
bevyEventLastRegisteredDate |
Datetime | Date/time of the member’s most recent event registration in Bevy (when a registration exists). |
Tip: If your Marketo fields use different API names, set the matching field-name settings under Settings → General → Marketo (for example Marketo webServicesAPISource field name). Leave the defaults if you created the fields with the names in the table.
Enter API credentials in Bevy
- Sign in to the Bevy admin dashboard as a community admin.
- Go to Settings → General (
/accounts/dashboard/#/admin/settings/general/). - Open the Marketo section.
- Enter Marketo client ID.
- Enter Marketo client secret.
- Enter Marketo Munchkin account ID (example:
123-ABC-123). - Click Save at the bottom of the page.
Membership tracking turns on when all three values are saved. There is no separate membership checkbox. You do not need to select Use Marketo JavaScript Lead Tracking or Use event-specific Marketo programs for this option alone.
When Bevy updates a Marketo lead
After credentials are saved, Bevy queues a lead update when members:
- Join or leave a chapter (including unsubscribing from a chapter mailing list in Bevy).
- Update profile data that your community maps to Marketo.
Updates usually appear in Marketo within about five minutes. You cannot change that timing.
- Bevy sets
webServicesAPISourcetoBevyon each push. - Bevy refreshes
bevyUserGroupIDsto the member’s current active chapter IDs (comma-separated). - When the member has event registrations in Bevy, Bevy can set
bevyEventLastRegisteredDateto the most recent registration time.
Important: Bevy does not change Marketo’s global lead subscription / unsubscribe flag. Chapter mail preferences in Bevy are not the same as Marketo’s global unsubscribe. Use bevyUserGroupIDs (and your own Marketo smart campaigns) to react to chapter membership changes.
Note: Bevy matches leads by email. If Marketo has more than one lead with the same email, Bevy skips that sync rather than guessing which record to update. Communities that use SSO often have limited Bevy profile data, so fewer mapped lead fields may change.
What this option does not do
- It does not load Marketo’s Munchkin script on community pages — that is Marketo integration - Set up JavaScript lead tracking.
- It does not create Marketo event programs or set Registered / Attended program statuses — that is Marketo integration - Set up event programs.
- Example request payloads live in Marketo integration - Payload examples.
If leads never update after a correct save, see Marketo integration - Test and troubleshoot.