Setting custom anonymous ID about consent-manager

[bartschelfhout]

Hi @alexhansonsmith I did actually.
Just to give some context fist:
Our own anonymous identifier is being created by a piece of javascript that is loaded from the head of our website, hence the identifier is available in way before the entirety of the page loads.

What we discovered is that the consent manager does a series of lookups before generating a new identifier, to find if there was a previously generated one.
It looks at the local storage for a variable called ajs_anonymous_id.

So the solution was simple. In the piece of javascript that is loaded from the header section of our page, we write our own anonymous identifier to localStorage with that name.
localStorage && localStorage.setItem('ajs_anonymous_id', our_anonymous_identifier);

This would always get picked up by the consent manager.
Hope that helps!

[alexhansonsmith]

Hi @bartschelfhout - did you get anywhere with this? Without being able to control the identifier our MTU usage has spiked considerably

[alexhansonsmith]

Hey @bartschelfhout - this is really helpful. Thanks for such a comprehensive response!

[felipe-najson-ntf]

@alexhansonsmith @bartschelfhout Hi everyone, it seems that you already managed to fix the problem.
I join what @bartschelfhout says. The easiest way to override the anonymus ID is to overwrite it in the snippet as suggested in the segment documentation.
https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/identity/#override-the-anonymous-id-from-the-segment-snippet

You can find other ways to override the anonymous ID here
https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/identity/#override-the-anonymous-id-from-the-segment-snippet

On the other hand I will be adding a section to the documentation so that future users know how to do it.

Thanks for your contribution!