Liongard Integration FAQs

Answers to the most Frequently Asked Questions about the Liongard Integration

What are the requirements for a Metric?

For a Metric to work in Synthesize billing module, you need to make sure the following requirements are met:

  • Parent/Child Inspector Type (for a list of verified inspectors that work with Synthesize billing module, click here).
  • Query results be in the form of a number (aggregated whole number).
  • Metric Display enabled
  • Mapping of all Accounts in Synthesize billing module.
  • Mapping of all Discovered Systems to Environments in Liongard

Tip For more information on requirements, please refer to the following documentation on Liongard Requirements.

How to Write a Metric?

If you're new to this space, we encourage you to review Liongard documentation. If you wish to have further assistance, please don't hesitate to reach out to support. 

How to Write a Metric (

Can you map multiple services to a single custom metric in Synthesize billing module?

Yes, you can map multiple services to a single customer metric in Synthesize billing module.

Simply drag and drop multiple services to a single custom metric when configuring or updating service mappings in the Liongard integration. 

Note When you map multiple services to a single metric, you may come across false-positive New Found Revenue service cards. To declutter these false positives, simply hit the filter button on the Service Reconciliation page and toggle the Show New Revenue Cards and hit apply.

Why do we have to map accounts in Synthesize billing module when we already map environments to Discovered Systems in Liongard?

It is recommended to map all accounts in Synthesize billing module, as we map accounts from your PSA., through the unique Metric ID pulled from Liongard's API to environments (discovered systems) from Liongard. 

If you cannot map all accounts when configuring the Liongard Integration (for example, your legal entity), simply continue on to the next step.

Do I have to map all Discovered Systems in Liongard?

Yes, this is a best practice and among Liongard's Weekly Recommended Practices.

Since each inspector has a dependent relationship to an Environment, those Discovered Systems that are not activated will not return values upon evaluation.

Note that it's best practice to review Discovered Systems in Liongard on a weekly basis to ensure data is retrieved. Refer to Best Practices for Using Liongard Integration ( for more information.

Is it required to use Child Inspector types when creating a Metric?

Synthesize billing module leverages Parent/Child Inspector types by mapping Accounts synced from your PSA to that of Environments in Liongard. Discovered systems are mapped to Environments in Liongard and Accounts to Environments in Synthesize billing module.

Although you may technically use a Parent Inspector type, there is no way to break down the aggregate quantities (unit count) per customer unless you were to do some JMESpath wizardry! This is where the use of Parent/Child Inspector types is recommended.

Tip For a full list of verified Parent/Child Inspector types, please refer to Verified Inspectors.

There are two inspector types within Liongard, a parent and a child inspector. Think of a parent inspector type as an MSP multi-tenant account and the child inspector type as their customers. Parent inspectors and child inspectors may return different Data Prints (raw data).

When creating a Metric, the Metric itself is tied to the inspector type. When using the Query Builder in Liongard (Admin > Metrics) one of the first drop-downs you will select is the Inspector, in which you would like to build the query against. Although the Metric itself is tied to both the parent and child inspectors, this ties the Metric you are building to that inspector type. If you were to create a Metric query that would only apply to a child inspector, then the parent inspector would evaluate null.

Bottom line, when you create a Metric, it will apply to all inspector types (parent/child), so once more Discovered Systems are activated and associated with an Environment, we will return data from that System, and the Metric will be active, without any further action.

Do inspector sync schedules align with Synthesize billing module?

Currently, inspector sync schedules align with the Synthesize billing module sync, which is scheduled every week on Saturday.

What is required from a Metric to validate with Synthesize billing module? 

Synthesize billing module only validates a single number (integer) to evaluate Quantity, like the following query:

Does Metric Display need to be enabled for third-party applications like Synthesize billing module?

Yes, Metric Display is required to be enabled for Synthesize billing module to evaluate Metrics.

Does Synthesize billing module support Change Detections?

No, Change Detections are currently not supported through the Liongard API.