Social Sharing is an extremely powerful tool to expand your user base and product recognition, customizing and implementing this to be efficient on your site can be quiet difficult. Most of the most relevant Social Providers have setup testing and troubleshooting tools that can help to identify where you have gone astray. Below is a brief overview of some useful tools that have been setup to assist with implementing custom Social Sharing options.
\nFacebook Open Graph Object Debugger
\nSetting up custom sharing with Facebook uses Facebook Open Graph meta tags, which are cached on Facebooks end and can lead to some confusion when making updates to your customizations. In order to identify the cached details that are being used for your implementation Facebook provides the Open Graph Debugger tool. All you need to do is input your sites URL and click on Debug.
\nThis will then crawl your page and display some useful information on the currently scraped details and warnings and error messages. It also give you the option at this point to refresh this scrapped data with any changes that you have made to our existing cached details.
\nGoogle Structured Data Testing Tool
\nGoogle uses a combination of a few different methods in order to define the customized sharing options:
\nThe structured data testing tool allows you to view what Google has interpreted from your webpage. Start by entering the URL of the page that you are sharing and click on preview.
\nInsert the URL in the \"URL to be shared field\" and click on Get Code. This will generate a sample share icon in the preview section.
\nTo test the share functionality click on the generated icon to display the share interface as determined by the provided URL.
\nTwitter Button Generator Tool
\nTwitter also uses multiple systems to determine the content that will be tweeted by the tweet buttons. The most commonly used meta tags, which allow you to set any of the available customizable fields in your tweet.
\nTo test the tweet you can use Twitters button generator. Select the \"Share a link\" option under \"Choose a button\".
\nInput your site URL in the \"share URL\" field, This will cause the Tweet button under \"Preview and code\" to be updated.
\nClick on the generated button to see a sample of the Tweet that has be defined by your URL.
\n","frontmatter":{"date":"February 09, 2015","updated_date":null,"description":null,"title":"Social Provider Social Sharing Troubleshooting Resources","tags":["Engineering","SocialSharing","Facebook","Google","LinkedIn"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.5037593984962405,"src":"/static/ca57c9bd893c5ad9ae9e68ee6a62ddd8/ee604/social.png","srcSet":"/static/ca57c9bd893c5ad9ae9e68ee6a62ddd8/69585/social.png 200w,\n/static/ca57c9bd893c5ad9ae9e68ee6a62ddd8/497c6/social.png 400w,\n/static/ca57c9bd893c5ad9ae9e68ee6a62ddd8/ee604/social.png 800w,\n/static/ca57c9bd893c5ad9ae9e68ee6a62ddd8/f3583/social.png 1200w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Karl Wittig","github":null,"avatar":null}}}},{"node":{"excerpt":"Are you tired of eye dropping (or worse… guessing) the colors of every social network you like? Fear not my friend, I have searched the webs…","fields":{"slug":"/engineering/social-media-colors-hex/"},"html":"Are you tired of eye dropping (or worse… guessing) the colors of every social network you like? Fear not my friend, I have searched the webs to find our beloved social media colors and listed it out in hex form.
\nFacebook #3b5998
\nGoogle Plus #F90101
\nLinkedin #007bb6
\nTwitter #55acee
\nYahoo #400090
\nAmazon #FF9900
\nAol #066cb1
\nDelicious #67b6e3
\nDigg #486ca3
\nDisqus #35a8ff
\nFoursquare #1cafec
\nGithub #181616
\nGoogle #0266C8
\nHyves #f9a539
\nInstagram #406e94
\nKaixin #bb0e0f
\nLive #004C9A
\nLivejournal #3770a3
\nMixi #d1ad5a
\nMyspace #313131
\nOdnoklassnikki #f69324
\nOrange #ff6600
\nPaypal #13487b
\nPersona #e0742f
\nPinterest #cb2128
\nQQ #009BD9
\nReddit #ff5700
\nRenren #005baa
\nSalesforce #219CDF
\nStackexchange #4ba1d8
\nSteam Community #666666
\nTumblr #32506d
\nVerisign #0261a2
\nVirgilio #eb6b21
\nVkontakte #45668e
\nSinaweibo #bb3e3e
\nWordPress #21759c
\nMailru #1897e6
\nXing #007072
\nOpenid #f7921c
\nDid I miss anything? Add it in the comments and help build this awesome list.
\n","frontmatter":{"date":"February 06, 2015","updated_date":null,"description":null,"title":"Social Media Colors in Hex","tags":["SocialMedia","Facebook","Google","Color"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1,"src":"/static/d2cb1d5026eb68986f33462424c006a3/6d161/darrylblog1-150x150.png","srcSet":"/static/d2cb1d5026eb68986f33462424c006a3/6d161/darrylblog1-150x150.png 150w","sizes":"(max-width: 150px) 100vw, 150px"}}},"author":{"id":"Team LoginRadius","github":"LoginRadius","avatar":null}}}},{"node":{"excerpt":"W3C stands for the World Wide Web Consortium, a recognized global web standards body. Tim Berners-Lee founded this organization and is run…","fields":{"slug":"/engineering/w3c-validation/"},"html":"W3C stands for the World Wide Web Consortium, a recognized global web standards body. Tim Berners-Lee founded this organization and is run by a full-time staff to continue creating and preserving web standards.
\nThese specifications are then used to direct the creation of code that lives up to those standards by web developers and browsers. They write the rule-book in a nutshell, which helps determine whether our code is well-written or poorly written.
\nLet's understand some essential points of W3C validation.
\nWorld Wide Web Consortium (W3C) allows internet users to check HTML and XHTML documents for well-formatted markup. Markup validation is an important step towards ensuring the technical quality of web pages.
\nW3C validation is the process of checking a website's code to determine if it follows the formatting standards. If you fail to validate your website's pages based on W3C standards, your website will most likely suffer from errors or poor traffic owing to poor formatting and readability.
\nW3C validation helps you to get better rankings in search engines (SEO). Errors in your code can affect your site's performance and make a big impact on your site's SEO. Search engines check the HTML or XHTML code of your website when searching.
\nIf they find invalid HTML or XHTML code – meaning code that does not follow the official rules, you might be removed from their indexes. If there is an error on your web page code, robots will stop searching your whole website's content.
\nHaving a standards-compliant code is the best practice for web design. It also teaches and encourages best practices for web design. While many veterans have learned to create error-free code and make relatively few validation errors, most beginners make more errors.
\nComputer validation checks can help beginners learn from their mistakes.
\n\"These technologies, which we call \"web standards,\" are carefully designed to deliver the greatest benefits to the greatest number of web users while ensuring the long-term viability of any document published on the web.\" — Web Standards Group
W3C validated websites will be easily accessed by people with modern browsers. Validation improves usability and functionality because your users are less likely to run into errors when displayed on browsers compared to non-validated websites.
\nValidation is fully compatible with a wide range of dynamic pages, scripting, active content, and multimedia presentations.
\nThe website validation process allows website designers to correct formatting errors that impact website performance, and following international standards, the code used in websites is reduced in size while improving efficiency.
\nBecause of this, web pages are displayed much faster and flow much better compared to websites that have not been validated.
\nMaking website browsers friendly is one of the biggest reasons why W3C code validation was introduced. Websites that are not validated may display correctly in one browser but not in other browsers. Many websites face cross-browser problems.
\nWebsites that are not validated may display formatting problems when used in certain browsers. On the other hand, W3C validated websites are displayed without errors regardless of what browser is used.
\nThere are five major web browsers: Google Chrome, Firefox, Microsoft Edge, and Safari, and usage among them translates to millions of internet users.
\nWith the recent boom in smartphones and tablets, more people will be accessing the Internet from mobile devices than desktop computers.
\nBy 2020, mobile commerce will reach $2.91 trillion worldwide, and some sectors are seeing an even higher proportion of mobile traffic, so there is a growing need for website owners to maximize the usability of their websites on new devices.
\nUnfortunately, many website owners do not take advantage of this growth and forego W3C validation that makes sure their websites and web pages are mobile-friendly too. If you want your website to be visited by as many users as possible, accessibility should be a big factor.
\nWebsites or web pages that validate using W3C website validation have code formatted efficiently and are easy to edit, and it helps website owners to create a new page or another new website with similar formatting.
\nThe validated code used in W3C HTML validation, W3C XHTML validation, or W3C CSS validation can be used in future sites.
\nValidators tell you where you have errors in your code. If your page isn't displaying as expected, a validator might very well point you to the cause of the display problems.
\nAlso, an invalid code that may display fine in one document may show stopping errors in another because of the encompassing code.
\nValidation is comparing your code to W3C standards. The best way to validate your code is by using the W3C validation tools.
\n\nHTML Validator:
\nThis validator checks the markup validity of web documents in HTML, XHTML, SMIL, MathML, etc
\nCSS Validator:
\nThis validator checks the CSS validity of web documents in HTML, XHTML etc.
\nThere are plenty of browser extensions that will test the page you're viewing against the W3C validators.
\nHTML Tidy is another option for validating pages, though it may not offer the exact same results as the W3C validator. One advantage of HTML Tidy is using an extension; you can check your pages directly in the browser without visiting one of the validators sites.
\nIf at all possible, any website should follow W3C validation requirements. It is the right way to do it, but it has many enduring advantages, such as extending the lifespan of the pages, maintaining browser stability, and much more. This will help you understand why W3C is necessary to test all our websites for W3C validation before calling a project complete.
\n","frontmatter":{"date":"January 26, 2015","updated_date":null,"description":"Learn what w3c is and why to use it, and also how to validate your web page for W3C standards, a simple guide on W3C validation.","title":"W3C Validation: What is it and why to use it?","tags":["W3C","Validation"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.5037593984962405,"src":"/static/198baa1960dbcb001c3f7c4c7a369913/ee604/w3c.png","srcSet":"/static/198baa1960dbcb001c3f7c4c7a369913/69585/w3c.png 200w,\n/static/198baa1960dbcb001c3f7c4c7a369913/497c6/w3c.png 400w,\n/static/198baa1960dbcb001c3f7c4c7a369913/ee604/w3c.png 800w,\n/static/198baa1960dbcb001c3f7c4c7a369913/f3583/w3c.png 1200w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Team LoginRadius","github":"LoginRadius","avatar":null}}}},{"node":{"excerpt":"Creating a popup is a very simple addition to any webpage. In this tutorial, I will show you how to create a popup using basic Html…","fields":{"slug":"/engineering/simple-popup-tutorial/"},"html":"Creating a popup is a very simple addition to any webpage. In this tutorial, I will show you how to create a popup using basic Html, javascript and CSS. The first thing we want to think about is what we want to do to trigger a popup. You can trigger an event on almost anything such as a button, link or keypress. In this tutorial, we will be clicking on a button to trigger a popup.
\nWhat you will need:
\nLet’s start building the popup
\n<html>\n<head>\n <title>A Simple Popup</title>\n</head>\n<body>\n<div id="maincontent">\n <h1>Page Content<h2>\n</div>\n<div id="overlay"></div>\n<div id="popup">\n <div class="popupcontent">\n <h1>Some Popup Content</h1>\n </div>\n</div>\n</body>\n</html>We’ve created a div with id overlay to cover all the page content when the popup is displayed. This forces the user to close the popup before returning to the page content and also creates a nice user experience. The div with id popup will be our popup containing controls at the top to close the popup and our content area. Currently, this popup has no content and no styling so nothing will show. Let's add some styling next.
\n<html>\n<head>\n <title>A Simple Popup</title>\n <style>\n #overlay {\n position: absolute;\n top: 0;\n bottom: 0;\n background: #999;\n width: 100%;\n height: 100%;\n opacity: 0.8;\n z-index: 100;\n }\n\n #popup {\n position: absolute;\n top: 50%;\n left: 50%;\n background: #fff;\n width: 500px;\n height: 500px;\n margin-left: -250px; /*Half the value of width to center div*/\n margin-top: -250px; /*Half the value of height to center div*/\n z-index: 200;\n }\n </style>\n</head>\n<body>\n<div id="maincontent">\n <h1>Page Content<h2>\n</div>\n<div id="overlay"></div>\n<div id="popup">\n <div class="popupcontent">\n <h1>Some Popup Content</h1>\n </div>\n</div>\n</body>\n</html>We’ve now added some CSS for the overlay and the popup. At this point, we can see a white box above our grey overlay. We’ve added an h1 tag inside our popup a page title and some main page content. We should now see something like this:
\nNext let's add a control to close this popup. We’ll add a span containing an X that we can click on to close this popup and JavaScript to handle this event.
\n<html>\n<head>\n <title>A Simple Popup</title>\n <style>\n #overlay {\n position: absolute;\n top: 0;\n bottom: 0;\n background: #999;\n width: 100%;\n height: 100%;\n opacity: 0.8;\n z-index: 100;\n }\n\n #popup {\n position: absolute;\n top: 50%;\n left: 50%;\n background: #fff;\n width: 500px;\n height: 500px;\n margin-left: -250px; /*Half the value of width to center div*/\n margin-top: -250px; /*Half the value of height to center div*/\n z-index: 200;\n }\n\n #popupclose {\n float: right;\n padding: 10px;\n cursor: pointer;\n }\n </style>\n</head>\n<body>\n<div id="maincontent">\n <h1>Page Content<h2>\n</div>\n<div id="overlay"></div>\n<div id="popup">\n <div class="popupcontrols">\n <span id="popupclose">X</span>\n </div>\n <div class="popupcontent">\n <h1>Some Popup Content</h1>\n </div>\n</div>\n<script type="text/javascript">\n // Initialize Variables\n var closePopup = document.getElementById("popupclose");\n var overlay = document.getElementById("overlay");\n var popup = document.getElementById("popup");\n \n // Close Popup Event\n closePopup.onclick = function() {\n overlay.style.display = 'none';\n popup.style.display = 'none';\n };\n</script>\n</body>\n</html>Now we can close this popup…. Ah, that’s nice. Here we’ve added our X to click on, some CSS to style this close area. Also, we’ve added the javascript to handle the click event to hide the popup. Save your file as index.html and open it in your browser to test closing the popup. You’ll notice that the popup is displayed when we first open the page. Let's hide this with CSS on load so that we have to do something to open it.
\n#overlay {\n display: none;\n ...\n}\n \n#popup {\n display: none;\n ...\n}After adding display: none; to our overlay and popup, you’ll notice that when you load the page in your browser we cannot see them. To show this popup we’ll have to do something, so let’s make a button to click on and some JavaScript to handle this event.
\n<html>\n<head>\n <title>A Simple Popup</title>\n <style>\n\t#overlay {\n\t\tdisplay: none;\n\t\tposition: absolute;\n\t\ttop: 0;\n\t\tbottom: 0;\n\t\tbackground: #999;\n\t\twidth: 100%;\n\t\theight: 100%;\n\t\topacity: 0.8;\n\t\tz-index: 100;\n\t}\n\n\t#popup {\n\t\tdisplay: none;\n\t\tposition: absolute;\n\t\ttop: 50%;\n\t\tleft: 50%;\n\t\tbackground: #fff;\n\t\twidth: 500px;\n\t\theight: 500px;\n\t\tmargin-left: -250px; /*Half the value of width to center div*/\n\t\tmargin-top: -250px; /*Half the value of height to center div*/\n\t\tz-index: 200;\n\t}\n\n\t#popupclose {\n\t\tfloat: right;\n\t\tpadding: 10px;\n\t\tcursor: pointer;\n\t}\n\n\t.popupcontent {\n\t\tpadding: 10px;\n\t}\n\n\t#button {\n\t\tcursor: pointer;\n\t}\n </style>\n</head>\n<body>\n<div id="maincontent">\n <h1>Page Content<h2>\n <button id="button">Show Popup</button>\n</div>\n<div id="overlay"></div>\n<div id="popup">\n <div class="popupcontrols">\n <span id="popupclose">X</span>\n </div>\n <div class="popupcontent">\n <h1>Some Popup Content</h1>\n </div>\n</div>\n<script type="text/javascript">\n\t// Initialize Variables\n\tvar closePopup = document.getElementById("popupclose");\n\tvar overlay = document.getElementById("overlay");\n\tvar popup = document.getElementById("popup");\n\tvar button = document.getElementById("button");\n\t// Close Popup Event\n\tclosePopup.onclick = function() {\n\t overlay.style.display = 'none';\n\t popup.style.display = 'none';\n\t};\n\t// Show Overlay and Popup\n\tbutton.onclick = function() {\n\t overlay.style.display = 'block';\n\t popup.style.display = 'block';\n\t}\n</script>\n</body>\n</html>We’ve added a button in our main content area. To show the popup we’ve added a JavaScript function to change the overlay and our popup to display:block; on event onclick. After making these changes click on your button to open your popup.
Demo:
\nSee the Pen OPmQMP by Zoie Carnegie (@zoie-loginradius) on CodePen.
\nPlease post your questions or feedback in the comment area.
\n","frontmatter":{"date":"January 05, 2015","updated_date":null,"description":null,"title":"A Simple Popup Tutorial","tags":["HTML","CSS","UI"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.5037593984962405,"src":"/static/53876e64ac99e057d364277e1ccec1ea/ee604/simplepop.png","srcSet":"/static/53876e64ac99e057d364277e1ccec1ea/69585/simplepop.png 200w,\n/static/53876e64ac99e057d364277e1ccec1ea/497c6/simplepop.png 400w,\n/static/53876e64ac99e057d364277e1ccec1ea/ee604/simplepop.png 800w,\n/static/53876e64ac99e057d364277e1ccec1ea/db955/simplepop.png 900w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Zoie Carnegie","github":null,"avatar":null}}}},{"node":{"excerpt":"Welcome to our new initiative to contribute and spread the learnings/findings we had working with LoginRadius API! We always try to come up…","fields":{"slug":"/engineering/hello-developers-and-designers/"},"html":"Welcome to our new initiative to contribute and spread the learnings/findings we had working with LoginRadius API!
\nWe always try to come up with new ideas/process during our development and research sessions..sometimes they are funny but awesome. :). We'll share those ideas and experiences.look forward for your comments/feedback!
\n--
\nLoginRadius Engineering team
\n","frontmatter":{"date":"May 02, 2014","updated_date":null,"description":null,"title":"Hello developers and designers!","tags":["Engineering"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1,"src":"/static/61bc9402fec623803bf04d21e948e84a/2a4de/desdev.png","srcSet":"/static/61bc9402fec623803bf04d21e948e84a/69585/desdev.png 200w,\n/static/61bc9402fec623803bf04d21e948e84a/497c6/desdev.png 400w,\n/static/61bc9402fec623803bf04d21e948e84a/2a4de/desdev.png 600w","sizes":"(max-width: 600px) 100vw, 600px"}}},"author":{"id":"Team LoginRadius","github":"LoginRadius","avatar":null}}}}]},"markdownRemark":{"excerpt":"Google has prepared a roadmap to restrict third-party cookies in Chrome. Since 04 January 2024, Chrome has rolled out third-party cookie…","fields":{"slug":"/engineering/identity-impact-of-google-chrome-thirdparty-cookie-restrictions/"},"html":"Google has prepared a roadmap to restrict third-party cookies in Chrome. Since 04 January 2024, Chrome has rolled out third-party cookie restrictions for 1% of stable clients and 20% of Canary, Dev, and Beta clients.
\nWhat does it mean for user authentication?
\nOn one hand, Google believes third-party cookies are widely used for cross-site tracking, greatly affecting user privacy. Hence, Google wants to phase out (or restrict) supporting third-party cookies in Chrome by early Q2 2025 (subject to regulatory processes).
\nOn the other hand, Google introduced Privacy Sandbox to support the use cases (other than cross-site tracking and advertising) previously implemented using third-party cookies.
\nIn this article, we’ll discuss:
\nThird-party cookie restrictions affect user authentication in three ways, as follows.
\nIf your website or app uses an external Identity Provider (IdP) — like LoginRadius, the IdP sets a third-party cookie when the user authenticates on your app.
\nIf you have multiple apps across domains within your organization and authentication is handled using an IdP (internal or external) with web SSO, you already use third-party cookies to facilitate seamless access for each user using a single set of credentials.
\nIf you have implemented web SSO with one primary domain and multiple sub-domains of the primary domain, third-party cookie restrictions may not apply. For now, Google doesn’t consider the cookies set by sub-domains as third-party cookies, although this stance may change in the future.
\nFor example, you have apps at example.com, travel.example.com, stay.example.com, and web SSO is handled by auth.example.com. In this case, third-party cookie restrictions don’t apply.
Federated SSO is similar to, albeit different from, web SSO. It can handle multiple IdPs and applications—aka., Service Providers (SPs)—spanning multiple organizations. It can also implement authentication scenarios that are usually implemented through web SSO.
\nUsually, authentication is handled on a separate pop-up or page when the user wants to authenticate rather than on the application or website a user visits.
\nFor example, you already use federated SSO if you facilitate authentication for a set of apps through multiple social identity providers as well as traditional usernames and passwords.
\n\n\nNote: It is also possible to store tokens locally, not within cookies. In this case, third-party cookie restrictions won’t affect token-based authentication. However, the restrictions still affect authentication where tokens are stored within third-party cookies (a common and secure method).
\n
Google has been developing alternative features and capabilities for Chrome to replace third-party cookies as part of its Privacy Sandbox for Web initiative.
\nSpecific to authentication, Google recommends the following:
\nCHIPS are a restricted way of setting third-party cookies on a top-level site without making them accessible on other top-level sites. Thus, they limit cross-site tracking and enable specific cross-site functionalities, such as maps, chat, and payment embeds.
\nFor example, a user visits a.com with a map embed from map-example.com, which can set a partitioned cookie that is only accessible on a.com.
If the user visits b.com with a map embed from map-example.com, it cannot access the partitioned cookie set on a.com. It has to create a separate partitioned cookie specific to b.com, thus blocking cross-site tracking yet allowing limited cross-site functionality.
You should specifically opt for partitioned cookies (CHIPS), which are set with partitioned and secure cookie attributes.
\nIf you’re using an external identity provider for your application, CHIPS is a good option to supplant third-party cookie restrictions.
\nHowever, CHIPS may not be ideal if you have a web SSO or federated SSO implementation. It creates separate partitioned cookies for each application with a separate domain, which can increase complexity and create compatibility issues.
\nWith Storage Access API, you can access the local storage in a third-party context through iframes, similar to when users visit it as a top-level site in a first-party context. That is, it gives access to unpartitioned cookies and storage.
\nStorage Access API requires explicit user approval to grant access, similar to locations, camera, and microphone permissions. If the user denies access, unpartitioned cookies and storage won’t be accessible in a third-party context.
\nIt is most suitable when loading cross-site resources and interactions, such as:
\nVerifying user sessions when allowing interactions on an embedded social post or providing personalization for an embedded video.\nEmbedded documents requiring user verification status to be accessible.
\nAs it requires explicit user approval, it is advisable to use Storage Access API when you can’t implement an identity use case with the other options.
\nWith Related Website Sets, you can declare a primary website and associatedSites for limited purposes to grant third-party cookie access and local storage for a limited number of sites.
Chrome automatically recognizes related website sets declared, accepted, and maintained in this open-source GitHub repository: Related Website Sets
\nIt provides access through Storage Access API directly without prompting for user approval, but only after the user interacts with the relevant iframe.
\nIt is important to declare a limited number of domains in related website sets that are meaningful and used for specific purposes. Google may block or suspend any exploitative use of this feature.
\nThe top-level site can also request approval for specific cross-site resources and scripts to Storage Access API using resuestStorageAccessFor() API.
If you’re using an external identity provider for your web application, you can declare the domain of the identity provider in the related set to ensure limited third-party cookies and storage access to the identity provider, thus ensuring seamless user authentication.
\nRelated Website Sets can also work to supplement third-party cookie restrictions in web SSO and federated SSO if the number of web applications (or domains) is limited.
\nFedCM API enables federated SSO without third-party cookies.
\nWith FedCM API, a user follows these steps for authentication:
\nYou can access a user demo of FedCM here: FedCM.
\nFor more information about implementing federated SSO with FedCM API, go through the FedCM developer guide.
\nFirstly, we’re committed to solving our customers' user identity pain points — and preparing for the third-party cookies phase-out is no different.
\nWe’ll implement the most relevant and widely useful solutions to facilitate a smooth transition for our customers.
\nPlease subscribe to our blog for more information. We’ll update you on how we help with the third-party cookie phase-out.
\nThe proposed changes to phase out third-party cookies and suggested alternatives are evolving as Google has been actively collaborating and discussing changes with the border community.
\nMoreover, browsers like Firefox, Safari, and Edge may approach restricting third-party cookies differently than Google does.
\nFrom LoginRadius, we’ll keep you updated on what we’re doing as a leading Customer Identity and Access Management (CIAM) vendor to prepare for the third-party cookie phase-out.
\nTop-level site: It is the primary site a user has visited.
\nFirst-party cookie: A cookie set by the top-level site.
\nThird-party cookie: A cookie set by a domain other than the top-level site. For example, let’s assume that a user has visited a.com, which might use an embed from loginradius.com to facilitate authentication. If loginradius.com sets a cookie when the user visits a.com, it is called a third-party cookie as the user hasn’t directly visited loginradius.com.