Proxying requests

One of SDK objectives is to proxy requests to Finteza via your website. For details, please visit the "Proxying the script and requests" section.

To enable proxying, set its parameters in addition to the main parameters in the Finteza.RegisterAnalytics initialization method:

Finteza.RegisterAnalytics(websiteId: "{WEBSITE_ID}", token: "{TOKEN}", path: "{PATH}");

Parameter	Type	Description
token *	string	Token for signing the X-Forwarded-For header. You can get this value in the website settings of the Finteza panel: open the Counter section, enable the "Proxying the script and requests" option and copy the value from the "Proxy token" field. When proxying, all requests to Finteza are physically sent from your website's server rather than directly from clients. In order to pass real IP addresses of clients (and not just the site address) to Finteza, SDK uses the X-Forwarded-For header. In order to prevent traffic inflation by spoofing requests and provide only real data on website visits, Finteza checks a header signature in requests. If a header is signed by the unique website token, the system trusts its values. Otherwise, the traffic is considered "inflated" (traffic reports are available in the Quality website section of the Finteza panel).
path	string	Beginning of the path for requests to be proxied. If the parameter is not specified, the default /fz value will be used. Below are the necessary changes to the tracking code, so that all requests to Finteza are executed along the paths with the specified beginning.

Parameter

Type

Description

token *

string

Token for signing the X-Forwarded-For header. You can get this value in the website settings of the Finteza panel: open the Counter section, enable the "Proxying the script and requests" option and copy the value from the "Proxy token" field.

When proxying, all requests to Finteza are physically sent from your website's server rather than directly from clients. In order to pass real IP addresses of clients (and not just the site address) to Finteza, SDK uses the X-Forwarded-For header.

In order to prevent traffic inflation by spoofing requests and provide only real data on website visits, Finteza checks a header signature in requests. If a header is signed by the unique website token, the system trusts its values. Otherwise, the traffic is considered "inflated" (traffic reports are available in the Quality website section of the Finteza panel).

path

string

Beginning of the path for requests to be proxied. If the parameter is not specified, the default /fz value will be used.

Below are the necessary changes to the tracking code, so that all requests to Finteza are executed along the paths with the specified beginning.

* – required parameters.

Example:

Finteza.RegisterAnalytics(websiteId: "opemapikpuymgukzpihgweylppotinamyf", token: "joanmxozikjgeqlgguazmzoplankaqlg", path: "/fz");

Then, add the following line in the Web.config file, under the system.webServer/modules section:

This enables the proxy module, which independently routes incoming requests and only proxies analytical requests to Finteza.

Note: Change the tracking code after configuring proxying.