Zuddl adds shareable live attendee reports and CRM sync logs with retry
Zuddl's November 2025 product updates add password-protected links to live attendee reports, sync logs for Salesforce, HubSpot and Marketo with one-click retry, and coupon limits that count by ticket rather than order.
Zuddl, an event management platform for conferences, webinars and field events, listed three November 2025 updates on its product updates page. The first lets organizers share a live attendee report through a password-protected link. The second adds integration logs for CRM and marketing automation syncs, with filtering, error details and retry. The third changes how coupon redemption caps are counted. Each item links to a support or documentation article, and the page lists the month rather than a specific release date.
The details
- Live attendee reports can be shared through password-protected links with per-viewer column selection.
- Changing the passcode revokes report access.
- Sync logs cover Salesforce, HubSpot and Marketo and filter by event, date or action type.
- Failed syncs show the exact API response and can be retried from the logs.
- Coupon limits can count each ticket rather than each order.
Context
Zuddl released an Open API for events, sessions, speakers and attendees in late 2025. It introduced its Sidekick and Ask Zuddl AI agents on January 29, 2026, added automatic Salesforce campaigns in July 2026, and released an agent for Slack and Microsoft Teams in August 2026. CRM sync logs relate to the Salesforce, HubSpot and Marketo integrations Zuddl already offered.
Not disclosed
- How long sync logs are retained.
- Whether shared attendee reports can be scheduled or exported.
- Which Zuddl plans include these features.
- Vendor
Zuddl- Category
- Events & Webinars
- Announcement type
- Feature update
Report an error
Vendors and readers can flag a factual error in this story, or ask for an image or logo to be removed. Email Cora, the editor, with the link. Image and logo removals happen within one business day. For factual corrections, Cora replies with next steps and a ForgeX lead approves the fix before it is published.




