Analytics integration
Trusted Only Logins (Clerk) + HalftimeOS
Track real agent and vendor login activity on the Trusted Only platform.
Why connect Trusted Only Logins (Clerk)?
How many agents and vendors actually signed in and used the platform this week? That login activity lives in Clerk, split by real business-profile type (agent vs. vendor) — not just a raw "active users" number that mixes the two together.
What you can track
-
Agent Logins Common pick
Distinct agent/broker-admin accounts that signed in during this period.
-
Vendor Logins Common pick
Distinct vendor accounts that signed in during this period.
-
Total Logins
All accounts that signed in during this period, agent + vendor + unclassified.
How to connect Trusted Only Logins (Clerk)
-
1
In HalftimeOS, go to Settings → Integrations and find Trusted Only Logins (Clerk).
-
2
Paste a JSON object with both a Clerk secret key and a read-only Trusted Only database connection string (the same one used for the Trusted Only metrics provider works here too): {"clerkSecretKey": "sk_...", "databaseUrl": "postgres://..."}. The database connection is needed to classify each login as an agent or a vendor.
-
3
Paste the key into HalftimeOS — it's encrypted at rest and never shown again in plain text.
-
4
Pick which metrics to track (we suggest the common ones) and map each to a new or existing KPI on your scorecard.
Connect with an API key from your own account.
Questions people ask about Trusted Only Logins (Clerk)
What does the Trusted Only Logins (Clerk) integration do?
How many agents and vendors actually signed in and used the platform this week? That login activity lives in Clerk, split by real business-profile type (agent vs. vendor) — not just a raw "active users" number that mixes the two together.
What metrics can I track from Trusted Only Logins (Clerk)?
You can pull Agent Logins, Vendor Logins, and Total Logins onto your scorecard as KPIs, updated automatically instead of entered by hand.
How do I connect Trusted Only Logins (Clerk) to HalftimeOS?
In HalftimeOS, go to Settings → Integrations and find Trusted Only Logins (Clerk). Paste a JSON object with both a Clerk secret key and a read-only Trusted Only database connection string (the same one used for the Trusted Only metrics provider works here too): {"clerkSecretKey": "sk_...", "databaseUrl": "postgres://..."}. The database connection is needed to classify each login as an agent or a vendor. Paste the key into HalftimeOS — it's encrypted at rest and never shown again in plain text. Pick which metrics to track (we suggest the common ones) and map each to a new or existing KPI on your scorecard.
How often does the Trusted Only Logins (Clerk) data update?
On whatever cadence matches the meeting the KPI feeds — you choose which meeting series and how many days ahead to pull, so the number's ready before that huddle starts, the same as any other integration in HalftimeOS.
Is my Trusted Only Logins (Clerk) data secure?
Yes. Your Trusted Only Logins (Clerk) credentials are encrypted at rest (AES-256-GCM) and scoped to your organization only. Connect with a restricted, read-only key where Trusted Only Logins (Clerk) supports one, so HalftimeOS can never write back to your account.
Related integrations
Put Trusted Only Logins (Clerk) on your scorecard.
Start free with one leader, then connect Trusted Only Logins (Clerk) whenever you're ready — no card required.