Settings
To configure Zaraz's general settings, select Zaraz ↗ > Settings. Make sure you save your changes, by selecting the Save button after making them.
Allows you to choose between working in Real-time or Preview & Publish modes. By default, Zaraz instantly publishes all changes you make in your account. Choosing Preview & Publish lets you test your settings before committing to them. Refer to Preview mode for more information.
The debug key is used to enable Debug Mode. Refer to Debug mode for more information.
Toggle this option on to enable the Zaraz E-commerce API. Refer to E-commerce for more information.
Cloudflare Zaraz offers backwards compatibility with the dataLayer function found in tag management software, used to track events and other parameters. You can toggle this option off if you do not need it. Refer to Data layer compatibility mode for more information.
When you toggle Single Page Application support off, the pageview trigger will only work when loading a new web page. When enabled, Zaraz's pageview trigger will work every time the URL changes on a single page application. This is also known as virtual page views.
Zaraz offers privacy settings you can configure, such as:
-
Remove URL query parameters: Removes all query parameters from URLs. For example,
https://example.com/?q=hellobecomeshttps://example.com/. -
Trim IP addresses: Trims part of the IP address before passing it to server-side loaded tools, to hide it from third-parties.
-
Clean User Agent strings: Clear sensitive information from the User Agent string by removing information such as operating system version, extensions installed, among others.
-
Remove external referrers: Hides the page referrers URL if the hostname is different from the website's.
-
Cookie domain: Choose the domain on which Zaraz will set your tools' cookies. By default, Zaraz will attempt to save the cookies on the highest-level domain possible, meaning that if your website is on
foo.example.com, the cookies will be saved onexample.com. You can change this behavior and configure the cookies to be saved onfoo.example.comby entering a custom domain here.
This option automatically injects the script needed for Zaraz to work on your website. It is turned on by default.
If you turn this option off, Zaraz will stop automatically injecting its script on your domain. If you still want Zaraz functionality, you will need to add the Zaraz script manually. Refer to Load Zaraz manually for more information.
When toggled on, the Zaraz script will also be injected into iframe elements.
Specify custom URLs for Zaraz's scripts. You need to use a valid pathname:
/<PATHNAME>/<FILE.JS>This is an example of a custom pathname to host Zaraz's initialization script:
/my-server/my-scripts/start.jsRefer to HTTP Events API for more information on this endpoint.
Choose whether to prevent Zaraz from loading on suspected bot-initiated requests. This is based on the request's bot score which is an estimate, and therefore cannot be guaranteed to be always accurate.
The options are:
- Block none: Load Zaraz for all requests, even if those come from bots.
- Block automated only: Prevent Zaraz from loading on requests from requests in the Automated category.
- Block automated and likely automated: Prevent Zaraz from loading on requests from requests in the Automated and Likely Automated category.
Refer to the Context Enricher for more information on this setting.