Connecting Vecta to Atlas

Atlas is your CRM. Connect the two and Vecta does three things: it writes each email onto the person's timeline in Atlas, it lets Atlas offer to turn a reply into a lead, and it lets you build a Vecta list from Atlas people instead of exporting a CSV.

Connect

1. 1

   Make the keys in Atlas

   A Vecta key (starts atl_vk_) in Settings → Connected apps, and, if you want to pick people from Atlas, an API key (starts atl_ak_) in Settings → API.

2. 2

   Paste them in Vecta

   Settings → Atlas. Only the workspace owner can do this. The keys are stored encrypted and never shown again.

3. 3

   Test each key

   The test buttons ask Atlas whether the key works, changing nothing.

What reaches Atlas

• Each email sent, opened, clicked and replied to, with the campaign name. For a reply, the first lines of what the person wrote (quoted text removed, at most about 300 characters).
• Bounces, unsubscribes and people you added to the do-not-email list. Atlas marks those people Do not email.
• Privacy: reply text, email addresses and names go from Vecta (Frankfurt) to Atlas (Helsinki), both in the EU, only while Atlas is connected.
• Only things that happen after you connect. Nothing old is sent.

Replies and leads

A reply is sent with its first lines and a note that a real person wrote it. Atlas can then offer to make them a lead. Out-of-office answers are marked so Atlas doesn't offer. Vecta never creates a lead by itself.

Do not email works both ways

Someone who unsubscribes or bounces in Vecta is marked Do not email in Atlas. The other way round, someone marked Do not email in Atlas is blocked in Vecta too, so no campaign will email them. Vecta reads Atlas's list every hour and whenever you pick people from Atlas, and you can press Check Do not email now in Settings → Atlas (it needs the Atlas API key).

Which company is this?

Vecta tells Atlas which company the workspace belongs to. If the Vecta key you pasted was made in a different company's Atlas, Atlas refuses it and Settings → Atlas says so in plain words. Make the key in the right company's Atlas and paste it again.

Pick people from Atlas

Lists → From Atlas lets you choose Contacts or Candidates, add search words and filters (one per line, like status:is:replied), see how many match, and import them into a new list. It uses the same import as a CSV, so duplicates are merged and anyone on your do-not-email list is still skipped.

If something looks wrong

• "Atlas doesn't have the Vecta receiving address yet": Atlas needs a small update first. Nothing is wrong in Vecta, and nothing is lost: events wait.
• "Paused: Atlas didn't accept the key": the key was revoked or mistyped. Make a new one in Atlas and paste it. Saving clears the pause and sending carries on.
• "The Vecta key starts with atl_vk_": you pasted the other kind of key.
• "This key belongs to a different company" or "different workspace": a key works for one company and for the first Vecta workspace that used it. Make a new key for this workspace.
• The address is refused: it must be Atlas's public https address, not a private one.
• Nobody matches in From Atlas: check the filters. A filter that names a field Atlas doesn't have matches nothing.
• People are missing after import: people without an email address in Atlas are skipped and counted, and so is anyone marked Do not email in Atlas.
• Disconnect: stops events and forgets the keys. Nothing already in Atlas is removed, and blocks Vecta already made from Atlas's list stay until you lift them.