All Collections
Apps & Integrations
CRM Integration Terminology
CRM Integration Terminology
Emma Dixon avatar
Written by Emma Dixon
Updated over a week ago

In order to make the integration with a CRM partner as simple as possible we have created this easy to use guide, designed to clarify the terminology used to enable the process to be as fast and efficient as possible.

CRM – This will refer to you chosen CRM partner

CRM Connector – The Force24 platform connects to CRM’s using a CRM connector. This connector allows a fast and simple connection. New connectors are being developed all the time to keep up with the constant innovation of CRM platforms.

API – Application Program Interface, this is a window provided by your CRM provider for us to use to gain access to your data.

API key – This is a token generated by your CRM to enable a programmatical authentication into your data. This is always issued by your CRM provider.

Secure Connection – We will establish a secure connection to your data to ensure you remain GDPR compliant at all times

1 Way Contact Sync CRM -F24 – This refers to a simple data exchange allowing us to keep your CRM contacts in Sync with contacts held in Force24. Actions performed to contact information in CRM will be replicated in the Force24 database

1 Way Contact Sync F24 -CRM – This refers to a simple data exchange allowing us to keep your Force24 account contacts in Sync with contacts held in your CRM. Actions performed to contact information in Force24 will be replicated in your CRM

2 Way Contact Sync – This refers to a 2-way synchronisation of your data, changes made in either platform will be mirrored in the other

List based Sync/Full Sync – A list-based sync is where only contacts meeting a specific criteria, such as a list membership will be synchronised with Force24 or your CRM. A full sync will mean all contacts in either system will be paired and synchronised.

Contact Information – Contact information relates to data held on the contact object. This includes data such as Name, Address, Age, Company and Lead Score. These are items held on a 1-2-1 relationship basis with the contact. This does not relate to activity information like emails opened or clicked

Other CRM objects – Other CRM objects outside of contacts may also need to be mapped, to give a better user experience. Such as call backs, opportunities, tasks.

Data processing – Data processing is sometimes needed during an integration to convert data into a useable format. For example, a contact Status of Customer may be referenced in the CRM database as the value “1”. This can be processed to be a meaningful value of “Customer” in the Force24 database.

Managed Integration – A managed integration is an integration that is managed by the Force24 team to ensure accuracy and consistency where a requirement involves data processing, other CRM objects or new CRM connectors. A managed connection is not directly editable via the Force24 platform interface – in an effort to keep things simple for all users.

Triggering – Is where the Force24 platform can be set to trigger a contact into a journey by the presence of a data value. Triggering can be done from any data value and does not need to be “human friendly” (i.e can be in code format)

Personalisation – This is where the data held will be used specifically to personalise an email, this data must be stored in a single field where it may be called in an SMS or Email

Did this answer your question?