Set up webhooks in Zoho PageSense

Set up webhooks in Zoho PageSense

Webhooks let you send data from Zoho PageSense to an external application or server whenever a supported event occurs. This helps you connect PageSense with your existing systems and automate workflows using conversion and form submission data.
For example, you can send conversion data to your backend when a visitor completes a goal, or send pop-up form submission data to another system for further processing.
NotesNote: Webhooks currently support goal completions and pop-up form submissions in Zoho PageSense. Support for other features will be introduced in future updates.

Create a webhook  

To create a webhook in PageSense:
Log in to your Zoho PageSense account and navigate to Settings > Connect Services > Webhooks.

Click New Webhook and enter a name and a description explaining its purpose, if required.

Enter the Webhook URL of the application or server that should receive the data.

Configure the authentication method required by your endpoint.

Click send test request to check whether the endpoint can receive the request and save Webhook.

Configure webhook authentication  

PageSense supports the following authentication methods for webhooks. Choose the method that matches the authentication requirements of your receiving endpoint.
HMAC


HMAC (Hash-based Message Authentication Code) is the recommended authentication method. It allows your server to verify that requests came from PageSense and that the signed content has not been tampered with.
To configure HMAC:
  1. Select HMAC as the authentication type.
  2. Copy the generated secret key and store it securely.
  3. Configure your receiving server to verify the signature sent in the
     X-PageSense-Signature header using the secret key.
  4. Use the verification result to determine whether to accept the request.
PageSense signs each request using the secret key and includes the signature in the X-PageSense-Signature header. Your server must implement the corresponding signature verification logic.
Important: Keep the secret key confidential. Do not share it publicly or expose it in client-side code.

No Auth
Choose No Auth if your receiving endpoint does not require authentication. Select No Auth from the Authentication Type dropdown. No additional authentication credentials are required.
Use this option only if your endpoint is designed to accept unauthenticated requests and you have considered the associated security risks.




Bearer Token
Choose Bearer Token if your receiving endpoint uses a bearer token for authentication.
To configure it:
  1. Select Bearer Token as the authentication type.
  2. Enter the token in the Token field.
  3. Save the webhook.
PageSense sends the token in the Authorization header using the following format:
Authorization: Bearer <token>



API Key
Choose API Key if your receiving endpoint requires an API key in a request header.
To configure it:
  1. Select API Key as the authentication type.
  2. Enter the required header name in Key Name.
  3. Enter the corresponding API key in Key Value.
  4. Save the webhook.
PageSense sends the API key as a header using the name and value you provide.


Basic Auth
Choose Basic Auth if your receiving endpoint uses username-and-password authentication.
To configure it:
  1. Select Basic Auth as the authentication type.
  2. Enter the username in User Name.
  3. Enter the password in Password.
  4. Save the webhook.
PageSense sends the credentials in the authentication header required by Basic Auth.


 Test a webhook  

You can use the Send Test Request option to check whether your configured endpoint can receive a request from PageSense.

Before sending a test request, make sure you have:

  • Entered a valid webhook URL.

  • Selected the appropriate authentication method.

  • Provided the required authentication credentials, if applicable.

  • Configured your endpoint to accept incoming requests.

If the test request fails, verify the URL, authentication details, and endpoint configuration before trying again.

When are webhooks triggered?  

Currently, PageSense supports webhooks for the following events:
  • Goal completion: Send data when a visitor achieves a configured goal.
  • Pop-up form submission: Send data when a visitor submits a supported pop-up form.
These webhooks help you pass relevant event data to your own systems for further processing and workflow automation. Support for additional PageSense features will be introduced in future updates.

Frequently asked questions  

Can I use webhooks with all PageSense features?
Not yet. Webhooks currently support goal completions and pop-up form submissions. Support for other features will be added in future updates.

Which authentication method should I choose?
Choose the authentication method supported by your receiving endpoint. HMAC is recommended because it allows your server to verify request signatures. If your endpoint requires a bearer token, API key, or Basic Auth, select the corresponding option in PageSense.

Can I send webhook data to my own server?
Yes. Enter the URL of your server's webhook endpoint and configure the authentication method it requires.

What should I do if a test request fails?
Check that the webhook URL is valid and accessible, the selected authentication method matches your endpoint's requirements, and the credentials are correct. Also, ensure that your server is configured to receive requests.

Will webhooks support other PageSense features in the future?
Yes. Support for additional features is planned for future updates. The currently supported events are goal completions, polls and pop-up form submissions.

 



We’ve designed this documentation to guide you every step of the way. If you need further assistance or have any questions, don’t hesitate to contact us at support@zohopagesense.com - we’re always here to help!