Every entry you collect in Cognito Forms contains an activity log, which includes the complete history of the entry in chronological order. The activity log enables you to see who performed an action on the entry and when it occurred, track payment history, view email delivery status, troubleshoot any errors associated with the entry, and more.
Viewing the entry activity log
Starting from 12/01/2022, you can access entry activity data as far back as: 1 week (Individual plan), 1 month (Pro plan), 6 months (Team plan), or 2 years (Enterprise plan).
To view the activity log for an entry:
- Open the Entries page for your form.
- Select an individual entry to expand the entry details.
- Find the Activity section.
- Select an individual event (Submit, Update, etc.) to view the full details, such as changes to entry status, payment activity, emails and integrations.
Actions can be performed by:
- A user logged into Cognito Forms. Their name, email address, and workflow role will appear in the log.
- People involved in your form’s workflow. Their email address and workflow role will appear in the log.
- An anonymous user. Their workflow role will appear in the log.
- An integration like Make, Microsoft Power Automate, Zapier, JSON webhooks, or Google Analytics.
- A payment provider like Stripe, Square, or PayPal.
If a user deletes their Cognito Forms account, their name and email address will be removed from the log. When a user updates their profile information (name, email, avatar, etc.), the audit log will display the most recent changes.
The activity log does not include the action of deleting an entry or viewing/editing an entry without performing an action.
The activity log displays all actions associated with the entry, as well as who performed the actions and when they occurred (based on your own time zone).
|Workflow Action (Cognito Forms User)||View when a Cognito Forms user performed a workflow action on the entry.|
|Workflow Action (Shared Link)||View when a user who received a workflow link via email performed a workflow action on the entry.|
|Workflow Action (Anonymous Link)||View when an anonymous user performed a workflow action on the entry.|
|Workflow Action (Integrations)||View when an integration was triggered, the delivery status of the integration, and if the integration failed and why.*|
|Save (Cognito Forms User)||View when an entry was saved and which Cognito Forms user saved it. The activity log records one save per one hour time window.|
|Save (Anonymous Link)||View when an entry was saved by an anonymous user.|
|Change Status||View changes to an entry’s status.|
|Import||View when the entry was imported from an Excel spreadsheet.|
|Submit Payment||View when payment was submitted to the entry.|
|Refund Payment (in Cognito Forms)||View when an order was refunded and which user initiated the refund.|
|Refund Payment (in payment provider)||View when an order was refunded within the connected payment provider.|
|Copy||View when the entry was copied from an existing entry.|
|Update Quantity||View when a quantity limit on the entry was updated.|
*Users with Owner or Administrator permissions can view the full integration status details.
Email delivery status
The activity log records details for all emails sent by the entry, including which workflow action triggered the email, the full text of the email, and the files or generated documents attached to the email.
|Sending||Our email provider is in the process of sending the email.|
|Delivered||The email was accepted by the recipient’s email server.|
|Soft Bounced||The email wasn’t delivered due to a temporary problem. Soft bounces can happen because the recipient’s inbox is full or due to an issue with the receiving server.|
|Hard Bounced||The email can’t be delivered for permanent reasons. A hard bounce typically occurs because the recipient’s address is invalid or no longer in use. In this case, our email provider will stop attempting to deliver the message and subsequent email to that address will be temporarily rejected.|
|Rejected||Our email provider rejected the API request to send the email. Typically, emails are marked as rejected to help maintain a good email sender reputation.|
|Spam/Complained||The recipient marked the email as spam. In this case, any subsequent emails will be rejected.|
Integration delivery status
Review all actions related to data integrations, including when an integration was triggered, the delivery status of the integration, and if the integration failed and why.
|Delivered||The integration was sent successfully.|
|Pending||The integration has been queued but not yet sent. Or, the integration is being retried. If our system receives a 4XX or 5XX response, we will initiate a retry mechanism, resending the webhook event up to 30 times over a 72 hour period. We do not retry 404 (Not Found) and 410 (Gone) responses for our integrations with Make, Power Automate, and Zapier.|
|Failed||The integration delivery failed and will not be retried.|
Users with Owner or Administrator permissions can select the integration status to view additional details such as the integration platform and trigger, response code, response message, etc.