Signal Types
There are 12 signal types. Firm-level types tell you about the firm. Project-level types also tell you the project. ThesignalType 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 isnull.
Example Payloads
The values below are illustrative.Firm level: viewed-product-page
Firm level: viewed-product-page
Project level: added-to-spec, project visible to your brand
Project level: added-to-spec, project visible to 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.Event: registered-for-event
Event: registered-for-event
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 itsprojectIdand other details, withprojectHidden: true. - Firms outside your accounts. You only get signals from firms that qualify for your brand’s Accounts page.

