Skip to main content
Act-On Software

Connecting a Single Salesforce Account with Multiple Act-On Accounts

You can connect one Salesforce account to multiple Act-On accounts. It's important to pay close attention to the records that are imported to and marketed to in each Act-On account. When your Act-On and Salesforce accounts are connected, the Salesforce administrator's login is used to make the connection.
Note: Connecting one Salesforce account to multiple Act-On accounts is not a default feature of the Act-On package for Salesforce. This can be done by Act-On Support, but there are several implications (described below).

For best results, use the Record Types feature in Salesforce for each of your Act-On accounts. For example, in Act-On account #1, connect with a Salesforce administrator who has access to Record Type A; in Act-On account #2, connect with a Salesforce administrator who has access to Record Type B. This workflow will allow the leads and contacts to be filtered before being pulled in to Act-On.

Here are some other things to be aware of when using multiple Act-On accounts to one Salesforce instance:

  • The Activity History displayed will be associated to the Act-On account in which your Sales User license is connected.
    • In the event you would like to combine your Act-On accounts into one, it is important to note that the Act-On activity history cannot be merged or transferred or cross referenced.
    • If you cancel an Act-On account, that history cannot be ported over to a new or existing account. 
  • It is a best practice to create multiple lead scores for each connected Act-On account to ensure that this field is not overwritten in Salesforce from two or more Act-On accounts. 
  • Having multiple Act-On accounts means having multiple CNAMEs and multiple website tracking beacons. Please ensure that all associated beacons are added to the web pages in which you wish to track.
  • Cookies for web visitors cannot be merged – each record gets a cookie for the one account. A contact can be cookied in one account but anonymous in another.
  • Lists will need to be imported to both accounts. You can control which records are imported into each Act-On account based on the connected user. 
  • Form pushes could update/override existing data if pushing from two different Act-On instances.
  • If you sync your opt outs back to Salesforce, you could potentially be opting out that record in both Act-On accounts. 
  • API calls are used from both Act-On accounts.
  • Was this article helpful?

Have a question about this topic?

Ask the community!