With our Contentsquare integration you'll be able to successfully send data to your CS account using our Engagement Builder.
Overview - how it works
Our javascript fs.js picks up parameters from the Contensquare javascript tag. These parameters are send back to our backend as part of the request to get a number. The parameters are stored in our side and, if the visitor makes a phone call to a Kaisa number, we will use the data collected to send it to Contentsquare, using our Engagement Builder.
An Engagement Builder workflow can be set up to send data to the Contentsquare Enrichment API using the Call Ends event in combination with the Webhook delivery method.
Engagement Builder needs to authenticate the request via a proprietary Contentsquare Authentication method.
Parameters picked up by fs.js
We pick up “project ID”, “user ID” and “session number” as described here.
In order for us to correctly store this and other parameters to send to Contentsquare, we need to add some rules directly in our database linked to your account, so before you can start using this Integration make sure to discuss this with your CSM or to reach out to our support team.
Configuring an authentication client for Contentsquare API
Before configuring a workflow to integrate with Contentsquare, an authentication client must be configured in our Platform:
- Find your API token in Contentsquare [contact Contentsquare and they will provide the token, note: should not be taken from their platform, but directly contacting them and asking for it.]
- Go to Kaisa Dashboard Settings → Integrations and API/OAuth
- In the Integrations tab,
- click [Activate] on the Contentsquare integration card
- Add your token from step 1
- Save
Setting up a workflow to integrate with Contentsquare
Create a workflow in Engagement Builder. For more details on our Engagement Builder webhook we have an article here.
In the Delivery Method drawer, select “Send a webhook”
Endpoint: use the enrichment_url macro: {{ integration.enrichmentURL }}
Authentication: Integrations
Client: Contentsquare
POST request body: you custom request body following the schema for enrichments, see explanation further down in this document
After this is set up, we should be ready to start sending data to Contensquare.
If you have any questions, don't hesitate to contact us!
Comments
0 comments
Please sign in to leave a comment.