This article describes the browser cookies, local storage, and session storage used by Emplifi Ratings & Reviews SpeedFlex widgets. The widgets are installed as non-blocking JavaScript on your site (first party). They load from, and communicate with, Emplifi servers (third party).
All cookies and storage entries listed below are first party: they're written by JavaScript on your site's domain. Emplifi servers don't set cookies.
The one exception is the UGC device identifier. When it's enabled for your site, the widgets load a hidden iframe from the UGC photos.pixlee.co domain, which stores an anonymous ID in that domain's own (third-party) storage.
Summary
|
Name |
Type |
Category |
Lifetime |
Disabled by |
|---|---|---|---|---|
|
|
Cookie |
Targeting / analytics |
30 minutes, renewed on each widget interaction |
|
|
|
Local storage |
Targeting / analytics |
Until removed |
|
|
|
Cookie |
Functional |
24 hours |
|
|
|
Cookie |
Functional |
1 year |
|
|
|
Session storage |
Strictly necessary |
Until the browser tab is closed |
Not affected (see Session storage) |
|
|
Third-party local storage (cookie fallback) |
Targeting / analytics |
Local storage: until removed. Cookie fallback: 30 days |
The iframe isn't loaded when you set |
Tracking (targeting) data
The SpeedFlex widgets collect data on how users view and interact with them. Two anonymous identifiers tie those interactions together. Neither contains any information about the user or their device. Emplifi uses the data for product improvement and to report on how your users interact with the widgets.
-
TTSVID (cookie): a random identifier for a single visit. It expires 30 minutes after the user's last interaction with a widget.
-
TT_UID (local storage): a random identifier for the browser, used to connect visits over time. It has no expiry. It stays until the widgets remove it (see below) or the user clears site data.
If you already have your own anonymous visitor ID, you can supply it with eventUid on turnToConfig. The widgets then use your ID and don't write TT_UID.
<script>
var turnToConfig = {
locale: "en_US",
pageId: "pdp-page",
sku: "YOUR_SKU",
eventUid: "YOUR_VISITOR_ID"
}
</script>
Disabling tracking
To stop tracking data from being collected, set disableTargetingCookies to true on turnToConfig on every page where the SpeedFlex widgets are installed. Typically, you do this when a user has opted out of tracking.
<script>
var turnToConfig = {
locale: "en_US",
pageId: "pdp-page",
sku: "YOUR_SKU",
disableTargetingCookies: true
}
</script>
When this setting is on, the widgets send no tracking events and write neither TTSVID nor TT_UID.
If the user opts out after the page has loaded, call the disableTargetingCookies command instead. It stops tracking immediately and removes both the TTSVID cookie and the TT_UID local storage entry.
TurnToCmd('disableTargetingCookies')
To turn tracking back on later in the same page view, call TurnToCmd('enableTargetingCookies').
Functional cookies
The SpeedFlex widgets set two more cookies for normal operation.
-
TT_USER_TOKEN: keeps a user logged in for 24 hours after they submit content through the widgets and authenticate with Emplifi Ratings & Reviews. It's only present for users who arrived from a solicitation or confirmation email. The cookie holds an authentication token and the user's display details (first name, last name, and nickname), so the widgets can show the user as logged in.
-
TT_SRLSD: stores the date the user last saw the seller rating form, so the form isn't shown too often. It only exists for users who have seen the form, and it expires after one year.
Disabling all cookies and storage
To disable these cookies together with the tracking data above, set disableAllCookies to true on turnToConfig on every page where the SpeedFlex widgets are installed.
<script>
var turnToConfig = {
locale: "en_US",
pageId: "pdp-page",
sku: "YOUR_SKU",
disableAllCookies: true
}
</script>
To apply this after the page has loaded, call TurnToCmd('disableAllCookies'). It removes TTSVID, TT_USER_TOKEN, TT_SRLSD, and the TT_UID local storage entry. Call TurnToCmd('enableAllCookies') to turn them back on.
Disabling all cookies changes how the widgets behave:
-
Logged-in state: users must enter their name and email address for every submission, unless you use SSO to manage logged-in state.
-
Seller ratings: if your site collects seller ratings, users may see the seller rating form more often, because the widgets can't tell when they last saw it.
Session storage
The widgets use session storage to remember which reviews, questions, answers, and photos a user has voted helpful or not helpful. This stops the same user from voting twice on one item and keeps their vote highlighted while they browse. Keys take the form <type>_<contentId>, for example rWasUpVoted_12345, and hold only the vote value.
|
Key |
Records |
|---|---|
|
|
Review marked helpful |
|
|
Review marked not helpful |
|
|
Vote on a question |
|
|
Vote on an answer |
|
|
Vote on a photo or video |
These entries contain no identifiers, are never sent to Emplifi, and are deleted by the browser when the tab is closed. They're strictly necessary for voting to work, so disableAllCookies and disableTargetingCookies don't affect them.
UGC device identifier
If UGC identifier sharing is enabled for your site, and tracking isn't disabled, the widgets load a hidden iframe from https://photos.pixlee.co/getDUH. The iframe returns an anonymous UGC identifier to the widgets, which attach it to tracking events. This lets Emplifi match widget activity with activity in Emplifi UGC for the same browser.
The identifier is a random ID with no information about the user or their device. Because it's created inside the iframe, it's stored on the UGC photos.pixlee.co domain, not on your site's domain:
|
Name |
Type |
Lifetime |
Notes |
|---|---|---|---|
|
|
Local storage |
Until removed |
Used when the browser allows local storage in the iframe |
|
|
Cookie (fallback) |
30 days |
Only used if local storage is unavailable. Set with |
|
|
Cookie (fallback) |
30 days |
Copy of the cookie above without |
Many browsers partition or block third-party storage, so the identifier may differ between sites or may not persist.
When you set disableTargetingCookies or disableAllCookies, the widgets don't load the iframe, so no identifier is created or read. Calling these commands doesn't remove an identifier that's already stored on the UGC domain.
Only Emplifi can change UGC identifier sharing. To check whether it's enabled for your site, or to have it disabled, contact Emplifi support.
Cookie attributes
All widget cookies are set on your site's domain with these attributes:
|
Attribute |
Value |
Notes |
|---|---|---|
|
|
|
Available on every page of your site |
|
|
|
Not sent on cross-site subrequests |
|
|
Set on HTTPS pages |
The cookie is only sent over HTTPS. It's omitted on HTTP pages, because browsers reject |
|
|
Not set |
Host-only: the cookie belongs to the exact host the widgets run on, not its subdomains |
The cookies are created by JavaScript, so scripts on your page can read them, and they can't be HttpOnly.