I’m afraid you can’t. Our plugin does not only use a regular JavaScript file (that you could, in theory, dynamically load from another URL if you so wished), but it also relies on a dynamic inline script that tells the regular JavaScript file information about your running tests (which pages are under test, what its conversion goals/actions are, etc).
Yes using the plugin is not a problem.
It’s just avoiding the Cloud Proxy scheme :
- the REST api
- External domain forwarding
- the insecurities of delegating a subdomain to you
- the performance issues of delegating a subdomain to you
- multiplication of dns resolution and domain calls.
By default, whenever there’s an event in the visitor’s browser that needs to be synched with our cloud (like “a visitor has seen this variant” or “a visitor has fulfilled that goal”), the event is sent to our cloud using an endpoint in: api.nelioabtesting.com.
Some browsers using ad-blockers might block that request, and so we’ll never know the events a visitor triggered. This is really unfortunate, because the information we collect is completely anonymous (again: there’s a visit here, there’s a conversion there), and that’s it… but ad-blockers decided to block our endpoints anyway.
To overcome this limitation, our plugin makes has a special setting to “proxy” those requests. This way, the events that are triggered in the visitors browser, would not ping our endpoint URL (api.nelioabtesting.com), but would instead ping your WordPress site (if you use the REST API method), which would then be responsible for synching the event back to our server, or a subdomain in your site that would forward the request to our servers (if you use domain forwarding).
So… what is your question precisely? I’m afraid I didn’t get it.
Why don’t you use GTM Server side to notify like all others “pings” tools ?
These proxy settings are pretty new in our plugin and I wasn’t (and still am not) familiar with GTM Servers or how we’d integrate our plugin with them and them with our cloud. What advantages would they offer?
In a simple way we put a server in the middle:
Our website call our server-side ( is a first party server for cookies too) and this server send to your api point all the report. Not the browser => no blocking at all.
That’s easy and all is based on GTM so there is plenty code source to do that in tag.manager.google.com
You keep the control by the API key.
And the js is from the same server.
So you can update it on the fly for all users.
The inline code remains in the plugin and all the setup.
I see. As I said, I’m afraid we’re not familiar enough with this setup to implement a compatibility layer on our own… but we’ll be happy to work with you and implement it together.
Please send us an email to support at nelio software dot com so that we can safely discuss what needs to be done.
I’ll be happy to work with you on that. Let’s move to your internal support support @ …
For me here it’s solved.
Thanks again for being so reactive.
Cool! We’ll be waiting for your new message/ticket, where we can discuss and work on the matter.
