Expand my Community achievements bar.

SOLVED

How overrideMboxEdgeServer works

Avatar

Level 3

Hello.

The documentation tells, that if overrideMboxEdgeServer=true, then <clientCode>.tt.omtrdc.net will be used for calls to Target, and if it's false, then mboxedge<clusterNumber>.tt.omtrdc.net.

 

Documentation also states that for CNAME usage overrideMboxEdgeServer should be false

 

Documentation links:
https://experienceleague.adobe.com/docs/target/using/implement-target/client-side/at-js-implementati...

https://experienceleague.adobe.com/docs/target/using/implement-target/before-implement/implement-cna...

 

QUESTION: Having all this information I still dont understand the reason of what overrideMboxEdgeServer was made for ?

And why for CNAME usage it should have false value ?

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

@Kirill812 As per my understanding “overrideMboxEdgeServer” configuration is used to avoid "edge cases" (where a visitor would move from 1 edge to another). If the visitor switches from one edge node to another, then that would mess up with their targeting qualifications because their profiles are not synched across different servers(They would get different experiences just by refreshing the page ). Hence to avoid this "overrideMboxEdgeServer" the default value is set to "True" so a visitor would remain associated with only 1 edge node.

If you will not set "overrideMboxEdgeServer" to false, then the first hit would go to the CNAME ( for example target.domain.com)and then the rest (subsequent hits) would go to the edge node associated with the first hit ( for example https://mboxedge34.tt.omtrdc.net). Now If a visitor has ad blockers and other privacy features on their browser, then request to the edge node (*.tt.omtrdc.net) may get blocked. Hence for CNAME we recommend setting the value of "overrideMboxEdgeServer" to false.

 

Hope this helps

View solution in original post

3 Replies

Avatar

Community Advisor

Hi @Kirill812 

we configure this CNAME since 3rd party domains are more likely to be blocked by security settings applied in browser client-side. Applying this update will reduce the likelihood of Adobe Target being blocked by increasingly aggressive security settings in releases of Chrome, FireFox, Edge, Safari etc. and affecting the Adobe Target functionality on your site.

Avatar

Level 3

Yes, this is clear. But still it does not clarify why for hybrid Target implementation this settings should be used:
<script>
window.targetGlobalSettings = {
overrideMboxEdgeServer: true,
serverState: ${JSON.stringify(serverState, null, " ")}
};
</script>


Avatar

Correct answer by
Employee Advisor

@Kirill812 As per my understanding “overrideMboxEdgeServer” configuration is used to avoid "edge cases" (where a visitor would move from 1 edge to another). If the visitor switches from one edge node to another, then that would mess up with their targeting qualifications because their profiles are not synched across different servers(They would get different experiences just by refreshing the page ). Hence to avoid this "overrideMboxEdgeServer" the default value is set to "True" so a visitor would remain associated with only 1 edge node.

If you will not set "overrideMboxEdgeServer" to false, then the first hit would go to the CNAME ( for example target.domain.com)and then the rest (subsequent hits) would go to the edge node associated with the first hit ( for example https://mboxedge34.tt.omtrdc.net). Now If a visitor has ad blockers and other privacy features on their browser, then request to the edge node (*.tt.omtrdc.net) may get blocked. Hence for CNAME we recommend setting the value of "overrideMboxEdgeServer" to false.

 

Hope this helps