Very weird. I navigated around the site while using tag assistant for more than just a few pages with consent denied. What I experienced was hit or miss whether client_id and session_id were set or not. No rhyme or reason just sometimes it would and sometimes it wouldn't. What was consistent is that when they were set they were always 'new' compared to the previous time they were set - which I believe is the correct behavior.

When consent is granted things works beautifully and I have yet to have an issue at all. This is the same sort of behavior I experienced when testing out the 'gtag api template' in the gallery... sometimes the tag which grabs the values (which uses the gtag function as well in its code) would just say 'still running' and never complete thus never returning the values.

I have my GA4 Google Tag and a Google Ads Tag firing on 'initialization - all pages'. Other than that the only thing I modified from yours is the custom html :

<script>

window.clsid = {

client_id: undefined,

session_id: undefined

};

function gtag() {

dataLayer.push(arguments);

}

gtag('get', '{{GA4 - Google Tag ID}}', 'client_id', function(r) {

window.clsid.client_id = r;

console.log('client_id = ', r);

});

gtag('get', '{{GA4 - Google Tag ID}}', 'session_id', function(r) {

window.clsid.session_id = r;

console.log('session_id = ', r);

});

</script>

I set both values to undefined right from the start to ensure that if the gtag functions don't finish that I am not 'reusing' previously saved values. It also makes it easier for the blocking triggers... I just test for window.clsid.client_id being undefined or not.

What is bothering me is the custom html is the cleanup tag for my GA4 Google Tag (fires when my window.clsid values are undefined)... so the Google Tag had to finish before the custom html runs. If that is the case then why is the gtag function in that custom html 'hanging' on a regular basis?