Troubleshooting

Issues you may encounter and potential solutions.

Consent Modal Not Showing

Possible Causes:

• Incorrect guiOptions configuration.
• SDK not properly initialized.

Solution:

1. Double-check the guiOptions configuration to ensure the modal is correctly set.
2. Verify that the SDK is initialized with the correct parameters.
3. Check the browser's console for error messages.

---

CSS Issues or Not Applying Correctly

Possible Causes:

• CSS variables are not correctly overridden.
• CSS conflicts with other project styles.

Solution:

1. Ensure that the CSS variables are overridden correctly according to the documentation.
2. Use the browser's Developer Tools to inspect and fix CSS conflicts.

---

Unable to Save User Consent

Possible Causes:

• Incorrect storage configuration.
• Restricted access to cookies or localStorage.

Solution:

1. Ensure that you have set the correct storage configuration in the SDK.
2. Check the browser settings or security policies to ensure cookies/localStorage are enabled.

---

SDK Fails to Load

Possible Causes:

• Incorrect path to the SDK file.
• Network connection issues.

Solution:

1. Verify the path to the SDK in your configuration file.
2. Ensure there are no network or firewall issues preventing the file from loading.

---

Interface Incompatibility on Some Browsers

Possible Causes:

• Certain CSS/JavaScript features are unsupported on older browsers.

Solution:

1. Check the list of supported browsers in the documentation.
2. Update the browser to the latest version.
3. Add polyfills for unsupported features if necessary.

---

"Missing or Invalid Credentials" Error

Possible Causes:

• Missing or invalid login credentials (url, key, trackingId).
• The url is incorrect or the Kalapa CMP server is unreachable.

Solution:

1. Double-check the login credentials:
   • Ensure that all fields (url, key, trackingId) are filled in correctly.
2. Verify that the url is a valid Kalapa CMP server address.
3. Confirm that the key and trackingId match the information provided by Kalapa.
4. If the issue persists, contact Kalapa support to verify your login credentials.

---

"Unauthorized Access" or "Invalid API Key" Error

Possible Causes:

• Invalid or expired API key.
• Your account does not have permission to access the Kalapa CMP system.

Solution:

1. Ensure the key used is a valid API key provided by Kalapa.
2. Contact Kalapa to verify the status and permissions of your account.
3. Request a new or renewed API key if needed.

---

Unable to Connect to Kalapa CMP Server

Possible Causes:

• Incorrect url or network accessibility issues.
• Kalapa CMP server is down or blocked by a firewall.

Solution:

1. Verify the url and ensure it matches the one provided by Kalapa.
2. Check if your network allows access to this url (not blocked by a firewall or network policy).
3. Check the status of the Kalapa CMP system. If necessary, contact support for confirmation.

---

Tracking ID Issues

Possible Causes:

• Missing or incorrect trackingId field.

Solution:

1. Verify the value of trackingId and ensure it matches the ID provided by Kalapa.
2. If you're unsure about the trackingId, contact Kalapa for assistance.

---

If these issues persist, please contact Kalapa support for timely assistance.