Use EncodeUri() if part of the URL path or EncodeUriComponent() if used as a URL parameter

[semisight]

When reviewing your template we've noticed that it is using parameters to build a url. It's a best practice to use [EncodeUri()](https://developers.google.com/tag-manager/templates/api#encodeuri) if part of the URL path or [EncodeUriComponent()](https://developers.google.com/tag-manager/templates/api#encodeuricomponent) if used as a URL parameter.

[harmasz]

Hey @semisight, we are currently using encodeUri() on the whole request path before running sendHttpGet(), like this:

server-side-template-for-gtm/template.tpl

Lines 230 to 242 in 2a9bde9

	// Build the full URL for sending the request
	const url = data.accountURL + encodeUri(requestPath);
	// The sendHttpGet API takes a URL and a result callback. You must call
	// data.gtmOnSuccess() or data.gtmOnFailure() so that the container knows when
	// the tag has finished executing.
	sendHttpGet(url, (statusCode) => {
	if (statusCode >= 200 && statusCode < 300) {
	data.gtmOnSuccess();
	} else {
	data.gtmOnFailure();
	}
	});

Do you mean that we should switch to encoding each param with encodeUriComponent()?

[endgameapp]

You should indeed change that behavior. For example, if a string will contain &-character it will break the query (since encodeUri will not encode & characters and thus will break up the parameter.

[endgameapp]

For example, when event.page_title = 'Cookies & Drinks' it will not encode & and thus break the URL parameters.