You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Thu, 16 Sep 2021 at 12:27 am TaeWoo Kim ***@***.***> wrote:
Safari is blocking all 3rd party cookies.. and Google is following
something similar.
Only way i can think of is wrapping JS inside a subdomain via cname.
Ie... https://serving.com/pixel.js lives on customersite.com
So customer creates "serving.customersite.com" cname, and points it to
serving.com
Now "serving.customersite.com/pixel.js" is not considered 3rd party.
Am I correct on this assumption?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#222>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAE2X434SXRUJ3PWOJIAIT3UCCUOPANCNFSM5ECSWOEQ>
.
Safari is blocking all 3rd party cookies.. and Google is following something similar.
Only way i can think of is wrapping JS inside a subdomain via cname.
Ie... serving.com/pixel.js lives on customersite.com
So customer creates "serving.customersite.com" cname, and points it to serving.com
Now "serving.customersite.com/pixel.js" is not considered 3rd party.
Am I correct on this assumption?
The text was updated successfully, but these errors were encountered: