Actito

Datafly Signal delivers events to Actito server-to-server using Actito’s profile API. Instead of running an Actito tracking script in the browser, Signal upserts the visitor’s Actito profile from your own first-party data, keeping contact records current for Actito email campaigns, journeys, and automation scenarios.

Prerequisites

Before configuring Actito in Signal, you need an Actito license, an API user, and a destination profile table.

Step 1: Create an API user

1. In the Actito portal, the license administrator goes to the API user management area.
2. Create a new API user dedicated to Signal (for example “Datafly Signal”).
3. Grant it write access on the entity and profile table you want Signal to feed.
4. Copy the generated API Key — an opaque string such as qhdfbvdh747R49FRHrthqhdfbvdh74. You will paste this into Signal.

Step 2: Note your entity and profile table

1. In the Actito Dashboard, note your entity name (the license/database identifier).
2. Open the profile table you want to keep in sync and note its exact name (it is case-sensitive).
3. Confirm the table’s unique key is the email attribute, and that it has attributes for the data Signal will write (for example firstName, lastName, phone, language, and a marketing-consent attribute).

Configure in Signal

Configuration Fields

Management UI Setup

API Endpoint

POST https://api.actito.com/v4/entity/{entity}/table/{profile_table}/profile?allowUpdate=true

The request body is a flat JSON object of profile attributes. allowUpdate=true makes the call create-or-update: Actito matches on the table’s unique key (email) and updates the existing profile if one is found, otherwise creates it.

Authentication

Actito uses a two-step token flow. Signal exchanges your API Key for a short-lived access token, then sends that token on every profile call.

GET https://api.actito.com/auth/token
Authorization: {api_key}

The response contains an accessToken (valid for 15 minutes), which Signal sends as:

Authorization: Bearer {accessToken}

Signal handles this exchange and token refresh for you.

Identity Signals

Actito profiles are keyed on the email address, so identifying users is what makes this integration work. Call datafly.identify() when a user logs in, registers, or submits a form:

datafly.identify("user-123", {
  email: "jane.doe@example.com",
  first_name: "Jane",
  last_name: "Doe",
  phone: "+44 7700 900123"
});

Signal normalises these before delivery:

Event Mapping

The Default preset upserts the profile on every tracked event so the contact record stays current. Two events are mapped explicitly; all others keep the profile fresh via global identity mappings and are otherwise dropped.

Example: identify on sign-up

Datafly.js call:

datafly.identify("user-123", {
  email: "Jane.Doe@Example.com ",
  first_name: "Jane",
  last_name: "Doe",
  phone: "+44 7700 900123"
});
 
datafly.track("Signed Up");

Actito profile payload sent by Signal:

{
  "email": "jane.doe@example.com",
  "firstName": "Jane",
  "lastName": "Doe",
  "phone": "+447700900123",
  "language": "en",
  "marketingConsent": true
}

This is sent as POST .../v4/entity/{entity}/table/{profile_table}/profile?allowUpdate=true, creating or updating the profile matched on email.

Testing Your Integration

Troubleshooting