Uniform Pulse FAQ

All users who have access to a project in Uniform can open Pulse in that project. Pulse uses your Uniform sign-in, so you do not need a different account or password.

Pulse shows only in the projects where Uniform activated it. To add Pulse to more projects, request activation or speak to your Uniform account representative.

No. Pulse starts to record events when Uniform activates it for a project.

Pulse keeps events for 90 days. In Pulse, you can look back a maximum of 14 days at a time.

Uniform usually sends each event to Pulse a few seconds after it happens. An open Pulse tab checks for new events every 10 seconds. For more information, see live updates.

No. Pulse shows who changed which item, when, and through which source. To see all the data that Uniform sent for an event, open the event and select Raw webhook payload.

An API key, a personal access token, or an automation made the change. Examples of automations are import scripts and AI agents. To find the API key, look at the Actor column. It shows the name of the key, or its ID if Uniform did not send a name.

Give each script or integration its own API key. Then you can see which one made each change.

Uniform made the change itself, not a person or an API key. An example is a scheduled release launch.

Pulse uses the time zone of your browser.

No. Pulse keeps the data of each customer in a separate database.

Uniform did not activate Pulse for this project. To activate it, request activation or speak to your Uniform account representative.

Your Uniform user does not have access to this project. Ask a team admin to give you access to the project.

Last modified
Previous
Insights
Next
Asset Studio