Labs
Evaluate experimental Vendo features without treating them as production contracts.
Last reviewed October 11, 2026
Labs is the area of Vendo for prototypes, proofs of concept, and features still being evaluated. Open Labs in the top menu. The left menu shows the Labs catalog.
The in-app catalog is the source of truth. Experiments can be added, renamed, moved, or removed without the stability guarantees of a generally available feature.
Some catalog entries link to experiments inside Labs. Others link to early versions of features elsewhere in the app.
Before You Use an Experiment
- Read its in-product description.
- Unless your Vendo representative has approved production use, use test data or a reversible scope.
- Record the success criteria and any affected downstream workflow.
- Keep a supported fallback for data, analysis, or activation that matters to the business.
Do not use an experiment as the only path for a production process. Do not assume its route, schema, output, or saved state will remain compatible.
Give Useful Feedback
When you report a problem, include:
- The workspace and experiment name
- The action you attempted
- The expected and actual results
- Whether the data was test or production data
- Screenshots, affected record identifiers, and approximate time
- Whether the result blocks an existing workflow
Use the in-app feedback path where it is available, or contact your Vendo representative.
Graduation
When a feature leaves Labs, its experimental contracts do not all become stable automatically. After the feature moves, use its production documentation. Do not use old Labs instructions as setup guidance.
Messaging delivery reference
Messaging Alpha is not generally live yet. Contact us to learn more.
This reference describes the Messaging experiment on Vendo staging. Its Mail Provider setup and delivery behavior remain pending production release.
On staging, open Messaging Settings and select Amazon SES or Mailgun from the Mail Provider table.
The following concepts explain how Vendo processes email activity. They are reference information, rather than settings or live metrics.
| Concept | Meaning |
|---|---|
| Source webhooks | An email source has its own callback URL. Vendo verifies provider signatures before processing feedback. |
| Message records | Vendo links provider message IDs to campaigns and recipients. Feedback can include the recipient, subject, and clicked URL. |
| Lifecycle events | Vendo uses shared event names for Amazon SES and Mailgun. Each event retains its provider context. |
| Raw webhook audit | Vendo stores accepted callback receipts to support processing, recovery, and troubleshooting. This is not a complete archive of every provider payload. |
Email lifecycle events
Available feedback depends on the provider and its tracking configuration. Providers do not emit every event in this reference.
email.send: The provider accepted the message for delivery.email.delivery: The recipient mail server accepted the message. This does not confirm inbox placement.email.open: The provider reported an open.email.click: The provider reported a tracked link click.email.bounce: The provider reported a bounced message.email.complaint: The provider reported a spam complaint.email.reject: The provider reported a rejected message.email.delivery_delay: Delivery is delayed or temporarily failed.email.rendering_failure: Amazon SES reported that it could not render the message.email.subscription: Amazon SES reported a subscription change.email.send_failed: The provider rejected Vendo’s send request.
Permanent bounces and complaints associated with campaign recipients suppress future sends to those addresses in the same workspace.
Provider feedback can arrive more than once or out of order. Vendo avoids duplicate lifecycle records and prevents older feedback from reversing recipient progress.
The campaign overview still includes prototype metrics. These event definitions do not establish a complete campaign reporting dashboard or a reporting model.