BetterContact

The Corma and BetterContact integration keeps your contact enrichment tool and its subscription in line with the sales and growth teams who use it. BetterContact describes itself as running 20+ data providers in one waterfall to find and verify emails and mobile numbers, charging only for valid data. It bills in credits, and its pricing page lists no seat or per-user charge, so the governance questions are who can spend the balance and where the contact data goes.

Key takeaways

• BetterContact pricing is credit-based: an email costs 1 credit and a mobile number 10 credits, charged per valid data point returned.
• The BetterContact credit balance is shared across the whole organization, not held per user or per API key.
• Each BetterContact API key identifies one user, grants full access to the credits and can be regenerated or deactivated.
• BetterContact's privacy policy says all its data infrastructure is in Europe, while its DPA allows sub-processors outside the EEA, including the United States.

Why do BetterContact API keys matter?

The API key is the main credential. BetterContact's authentication docs explain that a key identifies one user, while every key in the organization draws on the same credit balance, with rate limits applied per key. The API key also connects the Google Sheets Add-on, HubSpot and Clay; in Clay, the user enters their BetterContact email as the username and the API key as the password. When a key leaks, regenerating it stops the old value immediately. BetterContact documents no expiry for keys and no scope narrower than full access to the credits.

Team management is thinly documented. BetterContact describes no invite or removal flow and no named roles; its terms only say the customer may designate administrators who assign users differentiated access rights. For your GDPR records, contacts a user enriches stay in the customer's account while that user's account is active, and the BetterContact data processing agreement says all personal data is deleted at the end of the contract.

How Corma governs BetterContact

• Credits in the budget: the BetterContact plan and its monthly charge sit in SaaS subscription management, next to your other sales tools.
• Keys with an owner: every API key can spend the shared balance, so each one is a non-human identity that needs a named owner and a record of the tools it connects, such as Clay or HubSpot.
• Leavers with a key check: a leaver workflow in the IT Workflow Builder asks the person to deactivate their API key before they leave, and the team to reconnect any Clay, HubSpot or Google Sheets integration that used it.
• Users mapped to owners: the people who hold BetterContact access are mapped to owners and confirmed in automated access reviews.

Frequently asked questions

Does BetterContact support SSO and SCIM?

No BetterContact page mentions SAML single sign-on, SCIM or two-factor authentication, and the only alternative sign-in documented is Google Sign-In. Read how to offboard apps without SCIM, SAML or SSO.

How does Corma connect to BetterContact?

BetterContact's API docs cover lead finding, enrichment and the credit balance and list no user-management endpoint, so Corma's browser-based agents can work in the BetterContact web app, in an isolated browser session with credentials taken from your password vault. See also how Corma covers sales data tools such as Apollo.

Where is Corma data hosted?

Corma runs on AWS, with web servers and databases in data centers inside the European Union. Data is encrypted in transit and at rest, and Corma is ISO/IEC 27001:2022 certified.

Want a named owner for every BetterContact key that can spend your credits? Book a Corma demo.