All ideas

Our site is multi-currency: USD, EUR, GBP, CAD and PTS (which indicates loyalty points). Currently, it's using PTS orders (which start at 1,000) as $ so it's showing a user redeeming for 2k points as having an order value of $2,000. If there was a...

Deletion of identifiers from the customer should be possible via API. I have the following use cases in mind. Anonymize old customer who have requested their account to be deleted. We cannot make the customer anonymous if we cannot clean up their ...

It would be necessary to be able to delete event from ODP via API. I have two uses in mind for this. Currently there is no way to delete incorrectly created events. Mistake in data load or integration can cause unwanted event data and we would nee...

We would like to capture AVS response from PayFlowPro payment gateway to prevent fraud orders. Here is an example of the API response RESULT=0&PNREF=EFHP0D426A53&RESPMSG=APPROVED&AUTHCODE=25TEST& AVSADDR=Y &A VSZIP=N & CVV2...

Heeey, I'd like to submit a feature request in integrating Qualtrics with Optimizely. As we’re a user of both platforms, I believe that integrating these technologies can bring benefits to RSA. Qualtrics is a an experience management platfor...

We would like the ability to delete or hide custom created Objects. Currently these tasks must be handled by Support/Engineering and it can take a long time for these requests to be processed.

Usually, when presenting ODP to clients, the Customers section gets a wow, especially when they see the History logs. However, what the clients didn't see during quick presentations is usually, the history log does not tell the detail of the event...

If we had the ability to see a map of where people clicked on an email as a visual, it would enable faster decision-making about campaign efficiency and strategy: Number of clicks % of clicks

Currently we can only access Real-time Segments. We have requirements that go beyond 28 days and would like to personalise on normal segments.

The Optimizely Assistant chrome extension is running an ancient version of jQuery, as reported by this security analysis tool: https://crxcavator.io/report/hkmpnondmidmfdlaphahbalnmphelnfo?platform=Chrome You are currently using a version of jQuer...