Client-side JavaScript

Note: If your publication uses other features of Subscribe with Google, usage of swg.js client-side assumes that a publication has already configured and initialized the library as illustrated in the Subscribe with Google devsite. Using Subscribe with Google with Subscription Linking is optional.

With Subscription Linking, client-side javascript is the only way to create a new association between a PPID and a reader's Google Account. On a configured page, the reader is presented with a dialog asking them to link their subscription. After the reader clicks on the "Continue with Google" button, they can choose an account to link with, and be sent back to the configured page upon completion.

Associating the PPID with the reader's account is done using the linkSubscription method in swg.js. The use is similar to the previous Account Linking feature (example), but instead of passing a promise, the method accepts an object containing the PPID.

Code Examples

These client-side code examples illustrate how to initiate a link, what a valid response looks like, and (optionally) how to use the swg.js eventManager to listen to analytics events and route them accordingly.

Initiate the Subscription Linking dialog

const result = await subscriptions.linkSubscription({publisherProvidedId:6789})

Note: Don't unconditionally prompt users! You shouldn't prompt users who have already linked their subscription, and you should delay re-prompting users who recently declined linking their subscription.

Sample response

Valid responses from a successfully linked account contain both the PPID used in the link, and a boolean success status.

console.log(result) //{publisherProvidedId: 6789, success: true}

Subscription Linking does not require the use of third-party cookies or an active Google session for the reader. This flexibly allows for launching into the linking experience at any time in a reader's experience, and not just after a purchase. If a reader is not logged in to a Google Account, they are given the opportunity to do so as part of the flow.

Complete Client-Side example

<script
  async
  type="application/javascript"
  subscriptions-control="manual"
  src="https://news.google.com/swg/js/v1/swg.js">
</script>

<script>

  function linkSubscription(ppid) {
    self.SWG.push(async (subscriptions) => {
      try {
        const result = await subscriptions.linkSubscription({
          publisherProvidedId: ppid,
        })
        console.log(result)
      } catch(e) {
        console.log(e)
      }
    })
  }

  document.addEventListener('DOMContentLoaded', function () {
    (self.SWG = self.SWG || []).push(subscriptions => {
      subscriptions.init("PUBLICATION_ID");

      //Configure the event manager for analytics integration
      subscriptions.getEventManager().then(manager => {
        manager.registerEventListener((event) => {
            // Add code here to send the event to your analytics
            // sendToAnalytics(event);
          console.log(event);
        });
      });
    });

    document
      .querySelector("SELECTOR")
      .addEventListener('click', function(){
        linkSubscription(PPID)
      })
  });
</script>

Create an OAuth Client ID

While an OAuth client is not required for Subscription Linking, an OAuth client can be used to author the allowlist of authorized domains for your project. Authorized domains are a list of domains from which your client-side javascript is allowed to make calls from. Your publication likely already has an OAuth Client ID configured in Publisher Center, for use with swg.js.

• If your Subscription Linking client-side javascript calls originate from a previously validated domain name, no action is required.
• If your javascript runs from a new domain name, follow the SwG OAuth Client ID configuration instructions.

Note: Creating and using an OAuth Client is only available for publications who are launching Subscription after launching Subscribe with Google.

Testing

In order to test Subscription Linking's client-side implementation, the code must be run from a server with an authorized javascript origin.

1. For production use, authorized origins can come from either the configured OAuth Client, or from the list of verified domains in the publication settings within Publisher Center.
2. For development or staging use, with an unverifiable domain (e.g. localhost or a non-public server), the domain must be listed in the configured OAuth Client.

Note: Adding domains to the OAuth client's allowed origins list can take more than 30 minutes before they are available for use.

Key Point: To continually test with the same subscription account, the account may be manually unlinked using Google's my accounts page.

Troubleshoot Errors

The most common problem when testing client-side javascript is receiving a 403 - Not Authorized error when attempting to run the javascript. To resolve this, make sure that you are running the javascript from a validated domain in Publisher Center, or that you're running the code on a host that is in the authorized js origins of the linked OAuth client.