search

silverstripe / silverstripe-intercom

SilverStripe integration with Intercom.io
BSD 3-Clause "New" or "Revised" License
1 stars 5 forks source link

NEW: Add always_anonymous config option #20

Closed sminnee closed 5 years ago

sminnee commented 5 years ago

This means that integration code never uses the current member and can be more aggressively cached.

Fixes https://github.com/silverstripe/silverstripe-intercom/issues/19

chillu commented 5 years ago

You could set Intercom metadata via a cookie value instead, and then ignore that cookie value in CDN configuration (exclude from cache key)? Might require some JS to read the cookie value and provide it to some Intercom JS API

sminnee commented 5 years ago

That sounds more complicated and in the case of a public website the user tracking isn’t as important.

Typically either Intercom is being used in an app where the pages aren’t publicly cached anyway.

Or it’s being used on a website where Member::currentUser() isn’t as important to track.

chillu commented 5 years ago

Yeah, just an idea to retain that feature, but as you say, low priority and complicated.