You can calculate ratios in query formulas by dividing two aggregate values or by averaging a binary Existence output. Both approaches can return the same result. The better choice depends on the shape of the data, the ratio being calculated, and the complexity of the query.
For example, an event attendance rate can be calculated as:
Number of attendees / Number of registrations = 6 / 10 = 0.60⭐ Get Inspired
This article was adapted from a post by Technolutions staff in the Slate Community Forums' Get Inspired space. Have a great idea for a Get Inspired post? Let us know!
Comparing the two approaches
Approach | How it works | Pros | Cons |
|---|---|---|---|
Divide two aggregate exports | Create a Formula subquery export that divides a numerator export by a denominator export. | Works for a broad range of ratios and is easy to read when the numerator and denominator are conceptually separate. | Can require multiple joins, filters, and aggregate exports, which can add query complexity. |
Average a binary Existence export | Return | Can reduce repeated joins and may be easier to optimize for subpopulation ratios. | Only works when each denominator row can be evaluated as a binary member or non-member of the numerator group. |
Building a ratio by dividing two aggregate exports
Use this approach when you want to calculate a ratio from two explicit counts, sums, or other aggregate values.
In the query, add a Subquery Export.
Set Output to Formula.
Add a subquery export or aggregate export that returns the numerator. For an attendance rate, this is the number of attended registrations.
Add a subquery export or aggregate export that returns the denominator. For an attendance rate, this is the total number of registrations.
Rename each export so it can be referenced cleanly in the formula, such as
attendedandregistered.In the Formula section, divide the numerator by the denominator.
Select Save.

Building a ratio by averaging a binary Existence export
Use this approach when each row in the denominator group can be assigned a 1 or 0 based on whether it belongs to the numerator group. For an attendance rate, each registration can be evaluated as attended or not attended.
In an event with 10 registrations where six registrations are attended and four are not attended, the binary values look like this:
1 + 1 + 1 + 1 + 1 + 1 + 0 + 0 + 0 + 0 = 6The average of those values returns the same ratio:
(1 + 1 + 1 + 1 + 1 + 1 + 0 + 0 + 0 + 0) / 10 = 0.60In the query, add a Subquery Export for the row set that represents the denominator. For an attendance rate, this is the registration row set.
Add an inner Subquery Export.
Set Output to Existence.
Configure the Existence export so rows that meet the numerator condition return
1and rows that do not meet the condition return0.Return to the top-level subquery export.
Set the top-level output to average the binary Existence export.
Select Save.


📝 Note
The binary-average approach is appropriate for subpopulation ratios. It works when the denominator is a set of rows and each row can be classified as either included in the numerator or not included in the numerator.
Checking the results
When both approaches are configured for the same attendance rate, they should return the same value.
.webp?sv=2026-02-06&spr=https&st=2026-06-19T23%3A10%3A07Z&se=2026-06-19T23%3A25%3A07Z&sr=c&sp=r&sig=EOqrIdyC2n8CDhp4n%2BD4QAUJ%2B67oqtYgQzCUDZV1fgQ%3D?sv=2026-02-06&spr=https&st=2026-06-20T09%3A21%3A49Z&se=2026-06-20T09%3A34%3A49Z&sr=c&sp=r&sig=bX%2FQVmlpKtrTLMxkA%2BlJkW6NPiZ7ryXbWcHjJB56I2Q%3D)
Preview the query and compare the two outputs before using the ratio in reports, dashboards, exports, or automation. If the values differ, review the filters, row set, and aggregate settings for each subquery export.