Setting up your Chat Platform
Step 1: Configure your Unibuddy Chat Platform correctly in order for the lead data to flow through.
Ensure the below has been done:
Your Chat Platform URL has been created and sent to your Onboarding Manager (this is the URL where you will have your chat platform embedded).
This URL should be live and not a test site.
You have at least one (1) prospect or test prospect account created.
Source Mapping and Creating the Source Format
In order for the integration to work, the Unibuddy fields need to be mapped out by creating the source format on Slate. These fields are mapped with the lead and interaction data.
1. Create a new source format with the following settings by going to Database and then Source Format. From here Select New Source Format.
Name
Status = Active
Format = JSON
Remap As of Date= Current Date
PLEASE NOTE REGARDING "Remap As Of Date" PROMPT: This field tells Slate how far back to look into the imported data to make them available for remapping. Since you're creating a brand new Source Format, it's recommended that you use the current date.
PLEASE NOTE: SFTP access must be turned OFF for the Unibuddy/Slate sync to function properly.
2. Add a source format under force definition using the XML option
<layout type="json" node="/">
<f id="email" s="email" />
<f id="first_name" s="first_name" />
<f id="last_name" s="last_name" />
<f id="accept_marketing" s="accept_marketing" />
<f id="active" s="active" />
<f id="applicant_id" s="id" />
<f id="sign_up_location" s="sign_up_location" />
<f id="date_of_entry" s="date_of_entry" />
<f id="degree_level" s="degree_level" />
<f id="live_events_1" s="live_events[1]" />
<f id="live_events_2" s="live_events[2]" />
<f id="live_events_3" s="live_events[3]" />
<f id="live_events_4" s="live_events[4]" />
<f id="live_events_5" s="live_events[5]" />
<f id="live_events_6" s="live_events[6]" />
<f id="live_events_7" s="live_events[7]" />
<f id="live_events_8" s="live_events[8]" />
<f id="live_events_9" s="live_events[9]" />
<f id="live_events_10" s="live_events[10]" />
<f id="community_1_date" s="community[0]/interaction_date" />
<f id="community_1" s="community[0]/interaction_subject" />
<f id="community_2_date" s="community[1]/interaction_date" />
<f id="community_2" s="community[1]/interaction_subject" />
<f id="community_3_date" s="community[2]/interaction_date" />
<f id="community_3" s="community[2]/interactions_subject" />
<f id="community_4_date" s="community[3]/interaction_date" />
<f id="community_4" s="community[3]/interaction_subject" />
<f id="community_5_date" s="community[4]/interaction_date" />
<f id="community_5" s="community[4]/interaction_subject" />
<f id="conversation_summary" s="conversation_summary" />
<f id="blocked_by_university" s="blocked_by_university" />
<f id="degrees_interested_1_name" s="degrees_interested[1]/name" />
<f id="degrees_interested_2_name" s="degrees_interested[2]/name" />
<f id="degrees_interested_3_name" s="degrees_interested[3]/name" />
<f id="degrees_interested_4_name" s="degrees_interested[4]/name" />
<f id="degrees_interested_5_name" s="degrees_interested[5]/name" />
<f id="country_code" s="country/code"/>
<f id="country_name" s="country/name"/>
<f id="domestic_region_name" s="domestic_region/name"/>
<f id="domestic_region_country_code" s="domestic_region/country/code"/>
<f id="domestic_region_country_name" s="domestic_region/country/name"/>
<f id="decision_stage_name" s="decision_stage/decison_stage_name"/>
<f id="decision_stage_date" s="decision_stage/decison_stage_date"/>
<f id="decision_stage_date" s="decision_stage/decison_stage_reason"/>
<f id="confidence_in_choosing" s="confidence_in_choosing"/>
<f id="confidence_in_choosing_driver" s="confidence_in_choosing_driver"/>
<f id="signup_source_type" s="signup_source/type"/>
<f id="signup_source_created" s="signup_source/created"/>
<f id="source_tracking_params_medium" s="source_tracking_params/ub_medium"/>
<f id="source_tracking_params_source" s="source_tracking_params/ub_source"/>
<f id="source_tracking_params_campaign" s="source_tracking_params/ub_campaign"/>
<f id="source_tracking_params_content" s="source_tracking_params/ub_content"/>
<f id="YOUR_CUSTOM_FIELD" s="YOUR_CUSTOM_FIELD"/>
</layout>
3. If you want to use custom fields, you'll need to add them towards the bottom with the name of the custom field
PLEASE NOTE: The name of your custom fields needs to match what you input into your Format Definition area, and there should be no special characters (For example, ? or !). So please remove these from your custom field in your Admin Dashboard when possible. For example, if your new custom field was named Sample Custom Field, you would then add this name into your Format Definition area with '_' replacing the spaces:
<f id="sample_custom_field" s="sample_custom_field" />
Your are now ready to reach out to Unibuddy and finalise the sync between both Unibuddy and your new Slate Instance.