GTM Clarity Docs

Conversions and Billing

Understand what records conversion and resolution events, and how those events become billable usage.

GTM Clarity records conversion and resolution outcomes into an immutable ledger. Billing reads from that ledger later, so webhook events fire when outcomes are recorded, not when Stripe is updated.

What records a conversion event

There are two conversion paths.

The bot tool path records a conversion_event when the completed tool matches the customer's configured conversionType:

ToolMatching configured conversion types
capture_contactcaptured_contact
qualify_leadqualified_lead, resolved_ticket, custom
book_meetingbooked_meeting, sale, qualified_meeting

A tool only records when it matches the configured type. qualified_meeting additionally requires the model to confirm need, authority, and timing with qualified: true.

The workspace operator path records when an operator selects Convert. This path is idempotent, records one event per (conversation, customer), and uses the value agent_converted.

Use the outcome ladder

Pricing follows a five-rung outcome ladder. See the full ladder and pricing details on the pricing page.

RungOutcomePrice
ClarityIdentity resolution through resolution_event$0.50/visitor (banded $0.20–$0.50)
Contactcaptured_contact$21.50
Qualified Leadqualified_lead$95.00
Meetingbooked_meeting$125.00
Qualified Meetingqualified_meeting (verified)$225.00 + 2% ACV (minimum)

Clarity uses billResolutions, which is default-on. Each customer has one conversion rung through conversionType.

Understand billing mechanics

Events land in an immutable ledger. Identity resolution applies graduated pricing bands — resolution costs decrease as volume increases: $0.50 per visitor (0–1,000 visitors), $0.40 (1,001–5,000), $0.30 (5,001–15,000), $0.20 (15,001+).

Each visitor bills once per period at the highest outcome rung they reach. Reach a higher rung later and you pay the difference, never the whole rung again. The moment a resolved visitor becomes anything higher, the resolution is on us.

Trial allowance is controlled by includedConversions; included conversions bill at $0. Prepaid credits are drawn before metered spend. A soft budget cap stops billing but keeps serving. A hard spend cap suspends serving.

The conversion.recorded webhook fires at record time, not billing time.

Read and react to outcomes

Use the webhooks guide to react to conversion.recorded.

Use the API to read outcomes:

curl https://app.gtmclarity.ai/api/v1/conversions \
  -H 'Authorization: Bearer gtmc_your_key_here'
curl https://app.gtmclarity.ai/api/v1/resolutions \
  -H 'Authorization: Bearer gtmc_your_key_here'

On this page