This page will walkthrough the setup of Hightouch in K using the Direct Connect method
Step 1) Create an API Key
Log into your Hightouch account and go to Settings.
Go to the API Keys tab
Click Add API Key
Copy the API Key for the next step
Step 2) Add Hightouch as a New Source
Select Platform Settings in the side bar
In the pop-out side panel, under Integrations click on Sources
Click Add Source and select Hightouch
Select Direct Connect and add your Hightouch details and click Next
Fill in the Source Settings and click Save & Next
Name: Give the Hightouch source a name in K e.g. Hightouch
Host: Can be any unique value. For example add
app.hightouch.com/[hightouch account name]
Add your API Key copied from Step 1 and click Save
Test your connection and click Save
Click Finish Setup
Step 3) Schedule Hightouch source load
Select Platform Settings in the side bar
In the pop-out side panel, under Integrations click on Sources
Locate your new Fivetran source and click on the Schedule Settings (clock) icon to set the schedule
Note that scheduling a source can take up to 15 minutes to propagate the change.
Step 4) Manually run an ad hoc load to test Hightouch setup
Next to your new Source, click on the Run manual load icon
Confirm how your want the source to be loaded
After the source load is triggered, a pop up bar will appear taking you to the Monitor tab in the Batch Manager page. This is the usual page you visit to view the progress of source loads
A manual source load will also require a manual run of
DAILY
GATHER_METRICS_AND_STATS
To load all metrics and indexes with the manually loaded metadata. These can be found in the Batch Manager page
Step 5) Map Hightouch sources
After the manual load is completed go back to the Sources page
Next to the Hightouch source, click on the Merge Sources icon
Select the Hightouch sources and merge them with the sources you have already integrated in K
Troubleshooting failed loads
If the job failed at the extraction step
Check the error. Contact KADA Support if required.
Rerun the source job
If the job failed at the load step, the landing folder failed directory will contain the file with issues.
Find the bad record and fix the file
Rerun the source job