Planned maintenance: Tue Dec 8, 11:30pm–12:30am ET (8:30–9:30pm PT / Wed 5:30–6:30am CET). Brief downtime possible (up to 15 minutes).

Status page
Skip to main content

How can we help?

Need help? Check out our documentation or contact support

Search

Marketo integration - Test and troubleshoot

  • Updated

Test Marketo sync on a sandbox, then switch credentials for production. Use this page when an event program, lead, or registration does not appear in Marketo after setup.

These steps assume you already completed the Marketo setup for your community. Modes overview: Marketo integration - Introduction. Field and credential setup: Marketo integration - Set up membership tracking. Event programs: Marketo integration - Set up event programs. Request shapes: Marketo integration - Payload examples.

Test on a Marketo sandbox, then switch to production

  1. In Marketo, use a sandbox Custom Service (client ID and client secret) and the sandbox Munchkin account ID.
  2. In Bevy, go to Settings → General → Marketo and enter those sandbox credentials. If you use event programs, also set the sandbox folder, channel, prefix, and optional Clone event program ID so they match the sandbox.
  3. Save, then run a short test (publish a test event, register, check in as needed). Wait about five minutes, then confirm the program and lead updates in the Marketo sandbox.
  4. When you are ready for production, replace the Marketo client ID, client secret, and Munchkin account ID with your production values (and update folder, channel, prefix, and clone ID if those differ in production). Click Save.

Note: After you save production credentials, new publishes and membership or registration updates sync to production Marketo. Events that already synced to the sandbox keep their sandbox Marketo program IDs in Bevy until they are reconciled. Past events do not sync automatically when you turn the integration on — contact Bevy Support if you need help reconciling sandbox vs production or re-triggering past events.

Checklist for a successful test

  • Custom lead fields exist in Marketo (unless remapped in Bevy): webServicesAPISource (string), bevyEventLastRegisteredDate (datetime), and bevyUserGroupIDs (string, long enough for a comma-separated list of chapter IDs). Field setup: Marketo integration - Set up membership tracking.
  • Social features in Marketo are enabled when you rely on social profile field mapping.
  • For event programs: the Bevy programs folder and Marketo Event Program Channel exist in the Marketo instance you pointed credentials at, and Use event-specific Marketo programs is on. Setup: Marketo integration - Set up event programs.
  • The test event is published in Bevy. Draft or unpublished events do not create Marketo event programs.
  • You waited about five minutes after the action. Membership and event-program updates queue in Bevy; you cannot change that timing. Overview: Marketo integration - Introduction.

Tip: Bevy maps custom field API names on the backend. You will not see those fields in every Marketo UI surface until a lead push has run and the fields exist with the expected types.

Event program did not appear in Marketo

  1. Confirm the event is published in Bevy (not draft).
  2. Confirm Use event-specific Marketo programs is on and the Marketo client ID, client secret, and Munchkin account ID are saved for the Marketo instance you are checking.
  3. Confirm the Marketo Event Program Channel name in Bevy matches a channel that exists in that Marketo instance. If you renamed the channel in Marketo, update the Bevy field. Routing tips: Marketo integration - Best practices.
  4. If Clone event program ID is set, it must be the numeric Marketo program ID (digits only). An alphanumeric value can block create/clone.
  5. Wait about five minutes, then search Marketo for the new Event program. Bevy stores the Marketo program ID after a successful create so later registration and check-in updates target that program.

If the program still does not appear, contact Bevy Support with the Bevy event ID and whether you expected a clone or a new Event program on the channel.

Lead or registration data did not sync

  • Confirm the three custom lead fields exist with the correct types (or that Bevy’s field-name settings match your remapped API names). Missing or too-short bevyUserGroupIDs often surfaces as a Marketo field length error.
  • Bevy matches leads by email. If Marketo already has more than one lead with the same email, Bevy skips that sync (including adding the person to the event program) rather than guessing which record to update. Resolve or merge duplicates in Marketo, then retry the Bevy action or ask Bevy Support to re-trigger.
  • Registration sets program status to Registered; check-in sets it to Attended — only after the event’s Marketo program exists. If the program never created, fix event-program sync first.
  • Membership and registration updates usually appear within about five minutes. Example payloads: Marketo integration - Payload examples.

Missing Visited Web Page activity

When someone opens a Marketo email link, lands on a Bevy page, and registers, Marketo activity history often shows a web visit, a Bevy-driven lead update, and a program status change. If the Visited Web Page activity is missing:

  • Confirm Marketo has cookied the visitor (Munchkin can associate the browser session with the lead).
  • Confirm the correct Munchkin account ID is saved in Bevy and that JavaScript lead tracking is enabled so Munchkin loads on community pages — see Marketo integration - Set up JavaScript lead tracking.

UTM review on visit query parameters: Marketo integration - Best practices.

Common Marketo API errors

What you see What to do
Marketo API error about converting a value like ME14488A1 to a number (often tied to Clone event program ID) In Settings → General → Marketo, set Clone event program ID to digits only — the numeric Marketo program ID. Clear the field if you are not cloning.
Value for field bevyUserGroupIDs exceeds max length (or similar field length error) Confirm the bevyUserGroupIDs custom field exists as a string and is long enough for a comma-separated list of chapter IDs. Recreate or widen the field in Marketo if needed, then retry. Field setup: Marketo integration - Set up membership tracking.
Multiple lead match / duplicate lead (Marketo code 1007) More than one Marketo lead shares that email. Merge or fix duplicates in Marketo. Bevy will not push the attendee into the event program while duplicates remain.

Important: Bevy does not transform field values before sending them to Marketo (for example, country stays an ISO two-letter code). Fix unexpected values in Marketo or ask Bevy Support about mapped fields — do not expect Bevy to rewrite payloads mid-sync.