Event Feed

The Event Feed gives you a real-time view of every signup and transaction event Cello receives - whether from a webhook, the Cello API, or auto attribution. Use it to verify your integration is working correctly and to quickly identify missing or malformed fields. The Event Feed shows events from four sources: Auto Attribution, Stripe Webhook, Chargebee Webhook, and Cello API. Each event is validated and assigned a status of OK (all fields valid), Warning (non-critical issues like missing recommended fields), or Error (critical failures like missing required fields). You can filter by source, search by text, and expand any event to inspect its payload with per-field validation. You can access the Event Feed at Integrations → Events Feed in the Cello Portal.

​

List View

The Event Feed displays your most recent events in a table with the following columns:

​

Filtering Events

• Search bar - free-text search across all columns
• Tabs - switch between All, Attributions, and Events
• Filters button - apply additional filters to narrow down results

​

Event Statuses

Each event is validated and assigned one of three statuses:

​

Expanded Event View

Click the arrow on any row to expand it and inspect the event details. The expanded view shows the parsed event payload with per-field validation indicators. Each field is marked as valid, warning, or error so you can immediately see which fields need attention.

​

Field Validation Reference

The Event Feed validates each field in the event payload and shows a status indicator next to it. The required and recommended fields differ depending on the event source.

​

Field Validation for Stripe / Chargebee Webhooks

For Stripe and Chargebee webhook events, the ucc (referral code) and newUserId fields are always required. The email field is recommended and improves attribution tracking, but becomes required if your product uses auto attribution.

​

Required fields

​

Recommended fields

​

Other validated fields

​

Field Validation for Cello API Events

For Cello API events, the ucc (referral code) is always required, and at least one of newUserId or productUserId must be present. For invoice-paid events, the invoiceId, interval, and currency fields are also required.

​

Always required

​

Additional fields for invoice-paid events

​

Timestamp

Must be a valid Unix timestamp. Shows “Invalid” if the format is incorrect.

​

Organization ID Validation

How organizationId is validated depends on whether your product is configured for org-level attribution.

​

Org-level attribution enabled

When org-level attribution is enabled, the organizationId field is required and must not equal newUserId. If organizationId is missing while newUserId is present, the event shows an Error. If organizationId is provided but newUserId is missing, the event shows a Warning.

​

Org-level attribution disabled

When org-level attribution is disabled, any provided organizationId is ignored and the field is not shown if omitted.

​

Field Status Icons

​

Troubleshooting

You can inspect events from your AI client using cello_get_events via the Cello MCP.