Below are the details for testing the Utiq integration.
The following steps should be completed before taking the service into production use.
Note the utiqLoader.js only makes the Utiq service calls if consent (as configured via CMP) has been accepted for the
Utiq appropriate purpose.
- In your browser set a Developer Tools -> Network tab requests filter to:
- Set a stub customer identifier using for example this Chrome browser
extension ModHeader and
setting the request header x-cryptip with a sha256 (64 bytes) string, which will be provided by
the Customer Success team for the integration testing.
Using a stub customer identifier:
- Clear all browser cache / application storage, then open the page with the Utiq service enabled. You should see the
correct consent notification.
- Accept the consent. Then check you can see a bunch of requests applying above filter:
- Go to https://consenthub.utiq.com and click on “ACCESS YOUR CONSENTHUB” button to enter the area to see all consented
sites/apps. You should now see your site listed.
- Go back to your site and open consent settings and reject the Utiq service consent.
- Refresh page or navigate to another page. You should no longer see above calls.
- Go back to https://consenthub.utiq.com and refresh the page. Then click on “ACCESS YOUR CONSENTHUB” button to enter
the area to see all consented sites/apps. You should no longer see your site listed.
For access to demo sites that you can use to experience the Utiq service please contact our Customer Success team at firstname.lastname@example.org
Note: If you are testing with an internet connection that is from a telco participating in the Utiq service, the telco connection will take precedence over the stub. If the telco is not yet enabled during the testing, you will need to use a different telco connection to work with the stub.