Connect by Anthology (née CampusManagement, née-née Hobsons) is a higher-ed focused CRM system used by institutions across the globe.
Engage
Creating a functional two-way API integration between Gecko and Connect is quickly achievable.
Integrating Engage with Connect
It takes about 2 minutes to create a functional integration between Connect and Gecko:
⚙️ Connect
Log in to Connect and click your username in the top-right corner. Select Update Profile.
Create a new webservice
Make a note of the webservices username and webservice access token
🦎 Gecko
Navigate to Settings > Integrations > + New Integration
Pick Connect as the type
Put your webservices username in the Gecko Username field and your webservices access token in the Gecko Password field
Pick your region and click Save
Once your integration has been created, you'll be able to map fields between Gecko and Connect. In the video below, we showcase how this mapping works and how the integration look/functions:
Integrating forms/scripts
By syncing form/script responses, Gecko can create new contacts in Connect (or merge them into existing ones).
Gecko can push over:
Any details captured on the form
response meta information;
When the response was captured
UTM parameters
Student Geo-IP information
Capture app compatibility
who was logged in when the response was captured
which device was used
A record of any email/texts sent via form workflows (inc., the body of the message, sender name, subject lines, etc.)
You have complete autonomy over when a form response is synced and where the data in each field is pushed to.
Integrating events
Gecko can map to any existing Connect event or automatically build new events in Gecko whenever a new event gets created in Connect.
Once mapped, Gecko’s events integration with Connect is two-way (we can push attendee information from Gecko → Connect and pull from Connect → Gecko).
Gecko can:
Gecko can only sync top-level events to Connect Events and not sessions (Connect’s API prevents this, sadly!)
Gecko pushes attendee information directly into the event on Connect as Registration data
Integrating emails/texts
Texts or emails sent from Gecko automatically create a record on the student’s Connect Communication Log. This occurs anytime a new message is sent in Gecko, and the contact is synced.
Gecko can push over:
Any desired Student details
The sender of the text/email (e.g., “Admissions - admissions@gecko-university.edu”)
The subject line of the email
The body of the text/email
The time/date the email was sent
The status of the email/text (i.e., clicked, opened, delivered)
Integrating calls
In addition to creating new contacts (or merging into existing ones), calls made in Gecko can automatically create an interaction in the contact’s Communication Log back in Connect.
Gecko can push over:
Call data (start time, end time, outcome, caller ID, caller number)
An .mp4 recording of the call
The campaign of the call
Any student details required
Any notes made by the caller
Associated script responses
Importing from Connect into Engage
Contacts can be imported into Gecko via the Settings > Import Data page and will use Connect's ‘Contact Filter’ functionality. Gecko will only import student data from fields/attributes mapped in the Settings > Integration > {Connect} page on Gecko.
Chat
Integrating Chat with Connect
It takes about 2 minutes to create a working integration between Connect and Chat:
⚙️ Connect
Log in to Connect and click your username in the top-right corner. Select Update Profile
Create a new webservice
Make a note of the webservices username and webservice access token
🦎 Gecko
Navigate to Settings > Integrations. Find the Connect card and click Setup.
Put your webservices username in the Gecko Webservice Client Name field and your webservices access token in the Gecko PassKey field
Pick your region and click Done
Once your integration has been created, you'll immediately be able to map fields between Gecko and Connect. In the video below, we showcase how this mapping works and how the integration looks on both platforms:
Integrating conversations
In addition to creating new contacts (or merging into existing ones), Gecko Chat conversations can automatically create a new interaction in the student’s Communication Log. These updates to Connect are triggered when the conversation is started and again when the conversation is closed.
Gecko automatically pushes over:
Any student/contact data
The transcript of the chat conversation into the student timeline
Conversation metadata;
When the conversation took place
The channel the conversation took place on
Which agents/bots (if any) were involved
Any internal notes/workflows that were triggered during the conversation
Any questions? Start a live chat with a support team member, or feel free to explore the rest of our academy. Spotted an error or want to suggest a future article for the academy? Let us know here.