Lean how Celero integrates with various CRMS
Celero seamlessly integrates with various CRM systems, enabling effortless updates on contact engagement, as well as the generation and direct placement of new leads and contacts into the CRM. This integration greatly enhances the impact of your Microsites with minimal effort.
Just a heads up: this blog post is going to dive into some technical stuff. If you're just using Celero casually, you might not need all these details. However, for your technical and integration teams, we've put together this post to make sure they have all the information they need. So, feel free to skip it if you're not into the technical nitty-gritty! đ
There are two types of integrations:
Celero doesn't store any PII information, and holds anonymized IDs for all visitors and contacts.
When accessing an integrations API, Celero doesn't store any of the contacts details other than their anonymized identifier from the CRM.
the only exception to this is if you are using the Celero CRM to manage your contacts, send emails and One-time passwords - In order to enable those interfaces, Celero holds the contact email for contact identification (for example when identifying for one-time-password purposes)
Celero simply requires 3 integration points with any system depending on the features used:
1)Â An API to query if the visitor id (grabbed from the CRMÂ cookie)Â is already associated with a contact in the CRM - this will be used to update engagement data once the session is complete.
2)Â Once the visitor session is complete, Celero will add the summary of their engagement into the contact's activity steam in the CRM.
1) Celero will automate tracking of the visitors
2)Â If a visitor was already identified on Celero or through a url parameter, Celero will add the summary of their engagement into the contact's activity steam in the CRM.
1) An APIÂ to query for a contact based on the email the visitor has entered. If the contact exists, we grab their anonymized ID.
2)Â An APIÂ to add a contact/lead if the contact doesn't exist.
We do not persist the form values but rather push them to the CRM.
â
â