What Atlas reads from HubSpot
| Data | Details |
|---|---|
| Contacts | Your contacts, with the emails and phone numbers Keyring joins on. |
| Calls and meetings | Every call and meeting your team logged, under the rep who made it. |
| Deals | Your deals and each change of status, in the order your team made it. |
How a HubSpot record finds its buyer
- 1Import the full historyOn the setup call Atlas brings in your whole HubSpot history.
- 2Join on strong IDsAn email is a strong ID, so each contact joins its buyer automatically. A match on a phone number alone waits for a person to approve it.
- 3Set the deal beside its paymentsEach Stripe payment, refund and failed charge sits on the same buyer as the deal, so a plan payment that didn't go through shows on it, with the reason Stripe gave.
- 4Run the trail from ad to paymentPaper Trail lays out the buyer's path from the first ad click, through each call and deal, to the payment, and credits the sale under six attribution models.
What it feeds
- Reps ranked by cash collected: A leaderboard of who brought the money in, counted from the cash Stripe collected.
- Every renewal traced to its ad: The ad click, the demo, the HubSpot deal and every Stripe payment joined into one customer.
- One customer, every call: Customer Detail shows every call and deal with a buyer, joined from HubSpot and your other tools.
Questions
What does Atlas read from HubSpot?
Your contacts, the calls and meetings your team logged, and your deals, from your full history.
What happens when a plan payment fails?
The failed charge shows on the same buyer as the deal, with the reason Stripe gave, and so does the retry that collected it.
Do my reps have to change how they work in HubSpot?
No. Atlas imports the full history of the calls and deals they already log in HubSpot, and your pipeline stays as it is.
How do I know the HubSpot import is complete?
Data Health shows each import and marks one incomplete if Atlas couldn't fetch everything.