Discover what performs best and deliver it at scale

No. Optimize uses anonymous identifiers. As a simplified example, Optimize will identify a visitor with an anonymous visitor ID (e.g., user12345), but cannot tie that anonymous visitor ID back to an identifiable person by default. For example, if John Smith from the United States visits your site and is assigned the visitor ID of user12345, Optimize would only identify that visitor as user12345 but would not know that user12345 is John Smith.

No, Optimize does not use cookies.

Optimize uses local storage within the browser to assign an anonymous ID number to your visitors. These anonymous IDs cannot be tied back to an identifiable person when using Optimize out of the box.

Optimize stores data in a browser’s local storage in order to ensure the accuracy and integrity of the attribute data being collected.

Optimize needs to assign an anonymous ID to your visitors in order to determine the proper page variation to display based on that visitor's attributes.

When someone visits your site, a snippet of Javascript runs in the browser, which assigns an anonymous ID to a visitor and stores attributes that can be used for segmentation purposes.

If you have a consent management platform (CMP) integrated with your site, you can offer your visitors the choice to opt out of Optimize.

Potentially. At your sole discretion, if you decide to connect certain third-party integrations to Optimize, it is possible that that integration could enable you to individually identify visitors. To be clear, Optimize cannot do this on its own. Any individual identification that could occur would be the result of your use of that third party integration. The choice to use third-party integrations is exclusively yours. You might consider discussing any such integrations with your compliance team or a privacy attorney to help you determine the implications of using third-party integrations with Optimize.