Voyado

Datafly Signal syncs identified contacts to Voyado Engage server-to-server using the Engage Contacts API (v3). When a visitor identifies themselves — signs up, logs in, or submits a form — Signal creates or updates their Engage contact with their name, email, phone, locale, and marketing-consent preferences.

Prerequisites

Before configuring Voyado in Signal, you need a Voyado Engage tenant and an API key.

Step 1: Find Your Tenant Name

Your tenant name is the first part of your Engage URL. If you sign in at https://acme.voyado.com, your tenant name is acme. Use the matching staging tenant (https://acme.staging.voyado.com → acme.staging) when testing against a staging environment.

Step 2: Create an API Key

1. In Engage, go to Configure > API connections.
2. Create a new API key. Voyado recommends a unique key per integration, so name it something identifiable (e.g. “Datafly Signal”).
3. Copy the key — you will paste it into Signal.

Step 3: Confirm Your Contact Type

New contacts are created with a contact type. If you don’t specify one, Engage defaults to Member. If your instance uses a custom contact type for web sign-ups, note its exact name.

Configure in Signal

Configuration Fields

Management UI Setup

API Endpoint

POST https://{tenant}.voyado.com/api/v3/contacts?contactType={contact_type}&source=datafly-signal

Authentication is the apikey request header. Each request also sends User-Agent: Datafly-Signal/1.0 and Content-Type: application/json, both required by Engage.

Voyado dedupes contacts on the unique identifier in the body (email or mobilePhone), so sending the same identified visitor again updates the existing contact rather than creating a duplicate.

Identity Signals

Voyado is a first-party CRM and stores raw contact details — it does not accept hashed match keys. Signal sends these fields in plaintext to your own Voyado instance:

How to Send Contact Data

Call datafly.identify() when a user signs up, logs in, or submits a form:

datafly.identify("user-123", {
  email: "jane.doe@example.com",
  phone: "+46 70 123 45 67",
  firstName: "Jane",
  lastName: "Doe",
  country: "SE"
});

Event Mapping

The Voyado Contacts API accepts profile data, not behavioural events. Signal therefore delivers only identity-bearing events to Voyado; all other events (page views, product views, purchases) are dropped because they carry no contact identifier.

Default preset

Example: Sign-up

Datafly.js call:

datafly.track("Signed Up", { method: "email" });
// ...with traits previously set via datafly.identify():
datafly.identify("user-123", {
  email: "jane.doe@example.com",
  phone: "+46 70 123 45 67",
  firstName: "Jane",
  lastName: "Doe",
  country: "SE"
});

Voyado payload sent by Signal (visitor granted marketing consent):

{
  "email": "jane.doe@example.com",
  "firstName": "Jane",
  "lastName": "Doe",
  "mobilePhone": "+46701234567",
  "countryCode": "SE",
  "lang": "sv",
  "externalId": "user-123",
  "preferences": {
    "acceptsEmail": true,
    "acceptsSms": true,
    "acceptsPostal": true
  }
}

A successful create returns HTTP 201 Created with the full contact record; an update of an existing contact returns the updated contact.

Testing

Troubleshooting