The ajs_user_id cookie
ajs_user_id is a cookie set by Segment, from Twilio Inc. Stores the identified user ID after a call to identify().
Set by
SegmentDuration
1 year
Category
Analytics
Needs consent
Yes
Does the ajs_user_id cookie require consent?
ajs_user_id is used for analytics, so under the GDPR and the ePrivacy rules it may only be set after the visitor has agreed. Showing a banner is not enough on its own: the cookie must not be set before the visitor clicks accept.
Does your site set ajs_user_id before consent?
A free scan loads your site the way a new visitor sees it and lists every cookie that is set before anyone has said yes, ajs_user_id included.
How to put ajs_user_id behind consent
Remove the Segment snippet from your site and add your Segment ID under Integrations in Consentify instead. Consentify then loads Segment only after the visitor has accepted analytics, so ajs_user_id is never set before consent.
View all integrationsNot sure what's running on your Segment site?
Scan it first and you'll know exactly which scripts need consent before you set up the banner. Takes about ten seconds.
- Results in about 10 seconds
- No account needed
- Shareable report link
Other cookies set by Segment
| Cookie | Purpose | Duration |
|---|---|---|
| ajs_anonymous_id | Anonymous visitor ID used to tie events together before the visitor is identified. | 1 year |