Cookie Audience bucketing does not work with IP block?
I have a question about preview-testing an experiment with cookies and IP block. If we don't force the variation in the preview, we cannot see the experiment even if we have the cookie. Maybe that is because we have our internal IPs blocked: https://drive.google.com/a/veryshort.de/file/d/0B48vZt1PCqbXX1NDTl80WDJOS0k/view
Unfortunately we cannot disable IP blocking (not even for testing) as we have many employees working with the live site which has huge effects on the data.
I think the cookie setting works, so it must come from the blocking. what do you think about it?
Is there any way to ignore IP block while previewing the experiment?
We have one of the old "Gold" plans atm. I saw that the new Enterprise plan has a feature for IP based audiences... but is there another way to achieve this (or is it even possible with the enterprise feature?)...
Am I right in thinking that you've entered the IP addresses into 'Home > Project Settings > IP filtering'? If so, this doesn't block anyone from seeing an experiment, but removes these IP's results from the results page. If you do use other internal IP blocking in your site, and this is blocking you from seeing your experiment in preview, removing this and keeping the IP filtered IPs in the project settings will still remove your data from the results page.
I hope some of that information is useful!
What would happen, lets say if I removed the IPs from the "exclude traffic from these IP addresses" option, test a new experiment with it and get tracked myself; and than re-enter the IP block after testing? Will Optimizely retroactively filter out the unwanted IP traffic each time I change the IP settings?
Yes the IP Filtering feature will go through your result data events and exclude events that match the IP address. This is because Optimizely tracks the IP Address with every event. The same process is carried out for adding pageview goals retroactively. You can read about this process more, here.
I hope that helps!