Skip to main content
A signal is one record of an architecture or design firm engaging with your brand or products on Acelab. Each signal says which firm, which brand, what happened and when, and for project activity, which project. This page describes each signal the Signals API returns.

Signal Types

There are 12 signal types. Firm-level types tell you about the firm. Project-level types also tell you the project. The signalType field holds the value in the first column. Treat the set as open: Acelab can add types later, so your mapping should accept a type it doesn’t know. The types that fire “once per” a window update the same record when the activity repeats inside it: the id stays the same and occurredAt moves forward. See Keeping Records Up to Date.

Fields

Each signal is one JSON object. Every field is always present, and a field that doesn’t apply is null.

Example Payloads

The values below are illustrative.
If the project were hidden from your brand, projectHidden would be true, and projectName, project.description and project.architectName would be null. projectId and the other project details stay the same.

What Stays Private

The Signals API returns the same data your brand sees on the Accounts and Projects pages in Acelab, and no more.
  • People. Signals from browsing, downloads, searches and saves name the firm, not the person. Names are sent only where Acelab shows them to your brand: whoever started a conversation (info-request, general-inquiry), event registrants, and the architect of a visible project.
  • Hidden projects. Until a project is visible to your brand, its name, description and architect are null. The API still sends its projectId and other details, with projectHidden: true.
  • Firms outside your accounts. You only get signals from firms that qualify for your brand’s Accounts page.
Not included: