Send interactions (Coming Soon)

Send custom interaction events to Voyado and attach them to existing contacts

Overview

With this destination service, DinMo sends Voyado interactions attached to existing Voyado contacts.

Use this service when DinMo is responsible for sending event data, while Voyado remains responsible for deciding whether and how that event should later be used for automation, personalization, contact history, or other downstream use cases. Voyado interactions are designed to persist custom events on contacts and are tied to a predefined interaction schema.

To use this destination service, you need to:

1. Create a Voyado destination in DinMo

2. Create an event or custom model in DinMo with one row per interaction to send

3. Create an activation to send those records to Voyado

Each exported record is treated as one interaction event.

Learn more about Voyado Interactions here.

Before you start

Before configuring this destination service, make sure:

• your Voyado team has confirmed that interactions are enabled in your Voyado setup

• the target interaction schema already exists in Voyado, or is ready to be created

• the contact identifier you plan to use is available in your DinMo model

Voyado documents interactions as a feature tied to its interaction schema model and notes that availability depends on the relevant Voyado setup.

Destination setup

To start sending interactions, first create a Voyado destination with the Send interactions destination service.

To start sending Interactions, first create a Voyado destination with the Send Interactions destination service.

• Go To Destinations

• Choose your Voyado Engage Platform

• On the next page choose the Destination Option: Send Interactions

• Give it a name

• Save

Your destination is now ready and you can start firing actions.

Activation configuration

Once the destination has been created and your DinMo source model is ready, you can configure an activation.

Interaction schema ID

Select or enter the Voyado interaction schema ID used by this activation.

Each interaction sent to Voyado must reference an existing interaction schema. Voyado provides dedicated endpoints to create, retrieve, and delete interaction schemas, and a separate endpoint to send interaction events.

Run behavior

This destination service behaves like an append-only event export.

Each new record in the source model is treated as a new interaction. Previously exported interactions are not updated or deleted.

Fields mapping

In the Fields mapping section, map the DinMo field that identifies the related Voyado contact.

At least one contact identifier mapping is required.

If your source model contains an event timestamp, you can also map it to the interaction createdDate.

Contact identifier

Choose the field DinMo should use to associate the interaction with the correct Voyado contact.

The identifier should match the one expected by your Voyado implementation.

Created date

Map a timestamp field from DinMo to the interaction event date.

If no created date is provided, Voyado sets the current timestamp automatically.

Payload mapping

In the Payload mapping section, choose which fields from DinMo should be included in the interaction payload.

DinMo sends one interaction per exported record, with:

• the contact identifier

• the interaction schema ID

• the optional created date

• the mapped payload fields

The payload must be compatible with the selected interaction schema. Voyado states that properties not matching the schema will not be sent to Engage, and that interactions not following the schema rules are ignored.

Mapping recommendations

For best results, we recommend:

• using a stable schema for one business event type

• keeping field names explicit and consistent

• avoiding unnecessary schema changes after go-live

• keeping data types stable over time

• using simple scalar fields when possible

If the interaction is related to a product, Voyado recommends using the reserved property name productSku where relevant.

Example payload

{
  "contactId": "cf6d21fa-6e2b-481c-ab38-afa1012233ff",
  "schemaId": "review_submitted",
  "createdDate": "2026-03-20T09:00:00Z",
  "payload": {
    "productSku": "SKU-12345",
    "rating": 5,
    "channel": "email",
    "source": "warehouse_event"
  }
}

Schema management

Interactions rely on predefined interaction schemas in Voyado.

If the schema does not already exist, create it before enabling the activation.

Important limitation

Voyado does not support updating an interaction schema in place. If a schema is deleted, all interactions based on that schema are deleted as well. If it is recreated, the new version must remain backward compatible. Because of this, we recommend validating your schema structure before enabling a production activation.

Personalization and automation usage

Interactions are primarily a data destination.

Once stored in Voyado, they can be used for:

• contact history

• automation triggers configured in Voyado

• message personalization

• selected segmentation use cases

Voyado documents that interaction data points can be used in personalization, and that interactions can be used in automations depending on the Voyado configuration.

Recommended use cases

Use Send interactions when DinMo should send event data to Voyado, but DinMo should not directly trigger the final action itself.

Typical examples include:

• sending review events

• sending product activity events

• sending subscription lifecycle events

• sending appointment or booking events

• sending custom business events for later use in Voyado

When not to use this destination service

Do not use this service if your main goal is to immediately trigger a communication or automation from DinMo.

For those use cases, use Fire custom triggers instead.