2.6K members online now
2.6K members online now
Everything you need to know about setting up Optimize including creating your account and container, linking to Google Analytics and how to tag your site.
Guide Me

Optimize Mismatched Origin Error Message

[ Edited ]
Visitor ✭ ✭ ✭
# 1
Visitor ✭ ✭ ✭

I was running an experiment over the weekend when I started getting the following error message.

Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('https://optimize.google.com') does not match the recipient window's origin ('https://website.com').
(anonymous) @ js_compiled.js?v=141197588:1045

It was working on Thursday when I tested it, but stopped working sometime after that.


How do I resolve this issue? Nothing is loading on the varient because of it.




P.S. When I googled for similar issues they mentioned it being an http vs https issue, but both of these are https. And my website needs to be an https request.


UPDATE: After much review and help from customer service, we discovered this error had nothing to do with the issues I was experiencing. The test was to hide an element of a page, but when forwarding to the next page everything would be hidden again. The mistake I made was that I didn't make the test page specific and I had all the elements in our next page wrapped in an element with the same id.

1 Expert replyverified_user
Marked as Best Answer.
Accepted by topic author Aryeh S
January 2017

Optimize Mismatched Origin Error Message

Google Employee
# 2
Google Employee



Messages similar to the one that you mention (Failed to execute 'postMessage' on 'DOMWindow') are sometime shown during editing of a page (during initialization), but they don't have any effects in the behavior of the editor.


Also these messages do not appear to end users of the page and shouldn't appear when you are previewing a variation (using the preview functionality in the experiment page).


Can you give any details on the specific experiment and what do you mean by "stopped working"?


From what I can understand it stopped working for visitors of the page (since it was already running) and is not related with WYSIWYG "editing" of a variation.