IABTechLab
diff --git a/‎examples/google-secure-signals-integration/server_side/package-lock.json‎
Lines changed: 2 additions & 2 deletions b/‎examples/google-secure-signals-integration/server_side/package-lock.json‎
Lines changed: 2 additions & 2 deletions
diff --git a/‎examples/google-secure-signals-integration/server_side/views/header.html‎
Lines changed: 8 additions & 3 deletions b/‎examples/google-secure-signals-integration/server_side/views/header.html‎
Lines changed: 8 additions & 3 deletions
@@ -2,7 +2,7 @@
 <html>
   <head>
     <meta charset="UTF-8" />
-    <title>UID2 Publisher Server-Side Integration Example</title>
+    <title>Server-Side UID2 Integration Example Using Google Secure Signals</title>
     <link rel="stylesheet" type="text/css" href="/stylesheets/app.css" />
     <link rel="shortcut icon" href="/images/favicon.png" />
     <script src="https://code.jquery.com/jquery-3.6.0.min.js"></script>
@@ -26,15 +26,20 @@
     </script>
   </head>
   <body>
-    <h1>Server-Side UID2 Integration Example</h1>
+    <h1>Server-Side UID2 Integration Example With Google Secure Signals</h1>
     <p class="intro">
       This example demonstrates how a content publisher can use the UID2 services to implement the
       <a href="https://unifiedid.com/docs/guides/integration-google-ss#server-side-integration"
-        >Server-Side Integration</a
+        >Server-Side Integration.</a
       >. [<a
         href="https://github.com/IABTechLab/uid2-web-integrations/tree/main/examples/google-secure-signals-integration/server_side"
         >Source Code</a
       >]
+      <br />
+      <br />
+      This assumes that the publisher has implemented
+      <a href="https://unifiedid.com/docs/guides/integration-google-ss">Server-Side integration</a>
+      on the backend and able to pass the resulting UID2 identity response to the front end.
     </p>
   </body>
 </html>