​
Secure authentication

The app is installed from the **Integrations **menu inside Zuddl and authenticates with the REST endpoint, Client ID, and Client Secret which is accessible from Admin › Web Services / LaunchPoint. Using OAuth instead of static keys means tokens inherit Marketo’s role permissions and can be revoked with a single click.

​
One-time field mapping

During setup, you drop Zuddl fields onto Marketo counterparts in a visual map—First Name to firstName, Ticket Tier to a custom pick list, Dietary Restriction to a text field—and set an update policy (overwrite, only-if-blank, or never). Mapping one-time prevents post-event VLOOKUPs, keeps data types intact for smart lists, and lets marketing automate segmentation immediately. If you surface a new UTM field later, drag it onto a Marketo property, and the next registrant carries it through automatically.

​
Program & Status Sync

Zuddl can clone a “Base Program” you choose or attach to an existing one. Each new registrant is initially assigned the status of Registered; upon check-in, the status is updated to Attended, while no-shows remain Registered. Because the integration utilizes Marketo’s native status values, you don’t need to rebuild Smart Campaigns—dashboards for MQL counts and influence reporting become visible the moment people walk through the door.

​
Custom activities for deep engagement

Poll votes, Q&A posts, booth scans, and dwell-time buckets post to two custom activities—Event User Activity and Event User Profile—complete with metadata such as Session ID, Question Text, or Booth Name. These granular events feed lead-scoring rules and trigger Smart Campaigns without crowding the default activity log. A “Asked Question” filter, combined with an attendance time of greater than ten minutes, becomes a high-intent signal for SDR follow-up.

​
List push for registration

Any static or smart list can flow from Marketo to Zuddl as an invite list; toggle auto-register and new list members bypass the public form, receiving instant confirmation and calendar blocks. This saves VIPs from typing duplicate data and ensures last-minute additions (for example, a new C-level contact tagged by an AE) appear on the attendee list in seconds.

​
Error Handling & API Hygiene

Zuddl batches 200 records per call and respects Marketo limits—16 REST calls per minute for registrations, 10 for activity pushes. If a limit or maintenance window blocks calls, the integration queues events and retries with exponential back-off, then posts a sync-recovered log entry. Admins review one dashboard to confirm no action slipped through.

​
Governance & duplicate control

The default matching rule uses Email + Company, but you may lean on Marketo’s fuzzy-email or custom key logic; Zuddl simply inherits the winner.

​