Stape custom loader & incorrect sgtm server container URL

Custom Loader
1

Our site uses www.mydomain.com

The Stape custom loader generator thinks our sgtm server url is like this https://mydomain.com/metrics

but the server url uses www. ans is actually https://www.mydomain.com/metrics

When we use https://mydomain.com/metrics in the loader the tracking breaks with a 302 request error.

When we use https://www.mydomain.com/metrics in the loader the tracking works perfectly but Stape thinks all the requests received are from bots. My understanding is that this is the better server url to use as the pages on the site use www.

We’ve obviously done something wrong somewhere or misunderstood something, but really not sure what, any ideas anyone?

2

Hello,

The traffic is most likely being identified as bot traffic because Stape is receiving Cloudflare’s server IP address instead of the user’s actual IP address. Please make sure you have completed the following step in your Cloudflare configuration:

https://stape.io/helpdesk/documentation/how-to-use-same-origin-through-cloudflare#step-6-create-a-request-header-transform-rule

Regarding the Custom Loader, you can continue using https://www.mydomain.com/metrics.

3

Thank you very much, I will ask the devs to check that out.

4

Hi Alina, just to let you know your were right about the reason for the bots. It’s all fixed now.

Thanks again

5

Great, happy to help!