In this lesson we will take a look at everyday account management, from reporting to error management.
Account Reporting
Cyclr provides a selection of reporting tools that help you keep an eye on your customer’s accounts, providing you insight into their usage and allowing you to analyze and respond to each customer’s individual needs.
You can find most reports on your Partner Console, under Reports. We will be taking a look at the ones regarding your Accounts specifically, but you can familiarize yourself further with the other available reports in this article here on the Community Site.
Account Report
The Account Report provides you a list of all your Accounts, in order of the number of Active Cycles in the Account. A Cycle is considered active if they are currently running or were paused only within the last 24 hours.
This report gives you a quick look of your customers’ usage, as you can immediately see how many active cycles, connectors or custom connectors each Account has. It can provide you insight into customer engagement levels, which in turn may help you identify potential growth or expansion opportunities and even gauge possible future support needs.
Account Connector Method Report
The Account Connector Method report shows you all of the Connectors and Methods used in Accounts. It helps you get a quick overview and understanding of which Accounts use which Connectors and Methods.
The report displays a list of all your Accounts in alphabetical order. Next to the Account Name you have two columns: one showing a list of all Connectors installed in that Account, and the other showing you a list of all the Methods from those Connectors that are used by Cycles.
This can help you keep track of which of your customers are utilizing your integration offerings the best, helping you assess integration depth and complexity across your Accounts.
Account Task Report
The Account Task Report shows you daily task and incident metrics per Account. One “task” is a single API call or data step in your integration flows. If an action is successful, a “Successful Task” is recorded, and similarly if an action is unsuccessful or results in an error, an “Incident Task” is recorded.
This allows you to monitor several activities on your accounts, such as transaction volumes, error rates, and resource usage per customer. You can view only one day at a time, but
Task & Incident History Report
The Task & Incident History Report shows the task and incident metric history of an individual Account, helping you get a closer look at their task history. You’ll find the Task & Incident History Report through the Account Task Report, by clicking on the “clock” icon button next to the Account or Cycle data.
By analyzing Successful Tasks, you can assess each Account’s activity level, revealing high-usage customers who may need additional support. Tracking Incident Tasks helps monitor error rates which can help you stay informed on any issues that may require troubleshooting, training, or product improvements. High incident rates can indicate Accounts that are at risk of dissatisfaction, allowing proactive outreach to address potential issues before they escalate.
Monthly Task Report
Unlike the other Account reports, the Monthly Task Report is not available under the Reports sections of your Console. Instead, you will find it thorough the Account Management section of your Partner Console. Next to each account, there is an individual “reports” button that will take you to that account’s Monthly Task Report.
This report simply shows you the number of tasks that account has had in each billing period. This can help you spot usage trends in specific accounts, allowing you to identify growth trends, seasonal patterns, and potential churn risks by showing how consistently each Account uses their integrations.
Error management
If a transaction error occurs in a running cycle, you can configure Cyclr to make an HTTP Request to get immediately notified of it. This way you or your support team can respond to and troubleshoot issues as soon as they arise.
By sending a HTTP POST request to a URL you specify, whether that would be an external system or a webhook step inside a cycle, you can process the data using Cyclr’s logic tools. If you use a template or a cycle for this, we recommend installing the Error Webhook Utility Connector to make the setup simpler as it already knows the required Request Body structure.
We have a full example of how to handle errors using the Error Webhook available in the Handle Transaction Errors section in our documentation. The documentation provides a step-by-step guide on how to set up the webhook to get the webhook URL, with a complete example payload.
Account-level Override
If you wish, you can choose to handle errors in particular Cyclr Accounts differently by using the Account-level override.
To enable account-level overrides, in your Cyclr Console, go to the Accounts menu then Account Management. Click Settings for the Account you wish to set this for, and enable the Transaction Error Webhook option. You can then specify the URL for the Error Webhook you want to use for that Account in particular.
Key Takeaways
- By utilizing Cyclr’s Reporting tools, you can stay on top of your customers usage as well as spot potential upselling opportunities or churn risks.
- Configure Error Webhooks to get immediately notified on transaction errors on live cycles.
- You can manage errors on individual accounts differently with Account-level overrides from the Account Settings.