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.

Why route Actito through Datafly Signal

• Profiles are updated from the server, not the browser. Events reach Actito even when a tracker blocker or a failed page unload would have dropped a client-side call, so the profile reflects what actually happened.
• One consent decision governs every destination. Actito is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.

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

PUT https://api.actito.com/profiles/v5/entities/{entity}/profile-tables/{profile_table}/profiles
Authorization: Bearer {accessToken}

Profiles API V5 creates the profile, or updates the one whose unique key (normally emailAddress) matches. The V4 profile API was deprecated in January 2025 with end of service at the end of Q1 2026; Signal uses V5 from blueprint 0.2.0.

Identity Signals

Actito profiles are keyed on the email address. 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"
});

Event Mapping

The Default preset updates the profile on identity events only; page views and other behavioural events are not profile updates and are not sent.

Example: newsletter sign-up

{
  "attributes": {"emailAddress": "jane.doe@example.com", "firstName": "Jane", "lastName": "Doe", "motherLanguage": "EN"},
  "subscriptions": {"Newsletter": true},
  "dataCollection": {"date": "2026-09-23T10:00:00.000Z", "source": "Datafly Signal", "way": "website"}
}

Add more attributes by mapping them to attributes.<name>; the name must exist on the profile table, or Actito rejects the call with 400.

Testing Your Integration

Troubleshooting