Google Wallet Passes: Are you making the most of your links?

Key Concepts

• Google Wallet links
• App link data
• Value added module data
• Links module data
• Text module data
• Passes (loyalty cards, event tickets, boarding passes, etc.)
• Google Wallet REST API
• JSON manipulation
• Client libraries
• Tokenization
• Google Pay
• Google Maps integration
• Accessibility
• Internationalization/Localization

Links Inside Google Wallet: Best Practices and Implementation

This live stream focuses on how to effectively use links within Google Wallet passes (specifically loyalty cards in this demo) to drive user engagement and direct customers to specific online resources. The presenter, a Google Wallet expert, demonstrates four primary methods for embedding links: app link data, value added module data, links module data, and text module data.

1. App Link Data: Call to Action at the Bottom of the Pass

• Description: App link data allows you to add a prominent call-to-action link at the bottom of the wallet pass.
• Implementation:
  • The presenter modifies the loyalty class definition in Java code.
  • He creates an AppLinkData object and sets its webAppLinkInfos property.
  • Within webAppLinkInfos, he defines the target URI (e.g., developers.google.com/walletevents) and a description ("Check out the past and upcoming wallet live streams").
  • The code is updated, and the pass is refreshed in the Google Wallet.
• Example: The demo shows a link labeled "Open More Coffee" that directs users to the Google Wallet events page.
• Key Takeaway: This is ideal for primary calls to action, such as driving users to your website or a specific landing page.

2. Value Added Module Data: Recommendations in the Front of the Pass

• Description: Value added module data allows you to display recommendations or special offers with an image and a link in the front of the pass.
• Implementation:
  • The presenter adds ValueAddedModuleData to the loyalty class definition.
  • He creates a list of ValueAddedModuleData objects.
  • Each object includes a header (localized string, e.g., "This is your value added opportunity"), a body (localized string, e.g., "You got more free coffee"), a URI (e.g., developers.google.com/wallet), and an image (using ImageDefinition and ImageURI).
  • The code is updated, and the pass is refreshed.
• Example: The demo shows a recommendation with an image of "Sparky" (a Google mascot) and the text "This is your value added opportunity. You got more free coffee," linking to the Google Wallet developer website.
• Key Takeaway: This is useful for promoting specific offers, recommendations, or personalized content.

3. Links Module Data: Additional Information in the Back of the Pass

• Description: Links module data allows you to add a list of links that are displayed on the back of the pass (accessible via the three-dot menu).
• Implementation:
  • The presenter modifies the loyalty object definition.
  • He adds LinksModuleData and sets its uris property to a list of Uri objects.
  • Each Uri object includes an ID, a description, and a URI (e.g., maps.google.com or developers.google.com/wallet).
  • The code is updated, and the pass is refreshed.
• Example: The demo adds two links: "Google Maps Location" (linking to maps.google.com) and "Best source of wallet information on the internet" (linking to developers.google.com/wallet).
• Key Takeaway: This is suitable for providing supplementary information, such as store locations, support resources, or legal disclaimers.

4. Text Module Data: HTML Links in the Back of the Pass

• Description: Text module data allows you to add formatted text to the back of the pass, and it supports basic HTML tags, including hyperlinks.
• Implementation:
  • The presenter adds TextModuleData to the loyalty object definition.
  • He creates a list of TextModuleData objects.
  • Each object includes an ID, a header ("My first text"), and a body containing text with HTML tags (e.g., <a href="developers.google.com/walletevents">here</a>).
  • The code is updated, and the pass is refreshed.
• Example: The demo adds the text "The latest information about wallet events is <a href="developers.google.com/walletevents">here</a>." The word "here" is a clickable link to the Google Wallet events page.
• Key Takeaway: This is useful for embedding links within descriptive text, providing context and encouraging users to click.

Code and Technical Details

• The presenter uses Java and the Google Wallet REST API client libraries.
• He emphasizes that the core of the process involves manipulating JSON properties.
• The pass builder tool is used to generate initial JSON definitions for the class and object.
• The code demonstrates how to set various properties, including localized strings, URIs, and image definitions.

Q&A Highlights

• Google Maps Integration: While direct integration with Google Maps place pins isn't explicitly confirmed, the presenter suggests that using the correct Google Maps URL within a links module data entry should work.
• HTML Support: Basic HTML tags like <b>, <strong>, <i>, and <a href> are supported in text module data. The presenter is unsure about support for lists or advanced tags. Script tags are likely not supported.
• Accessibility: The Google Wallet team prioritizes accessibility, but the presenter is unsure about the support for accessibility-related HTML attributes like alt or title within text module data.
• Google Wallet vs. Google Pay: Google Wallet is for storing passes and digital IDs, while Google Pay handles online payments.
• Tokenization: Credit and debit cards added to Google Wallet must be tokenized.
• Availability in India: The presenter explains that adding credit/debit card support to Google Wallet requires individual agreements with card issuers, which is a time-consuming process. Google Wallet is available in India with passes.

Conclusion

The presenter effectively demonstrates four distinct methods for incorporating links into Google Wallet passes. By strategically using app link data, value added module data, links module data, and text module data, developers can create engaging and informative passes that drive user interaction and achieve specific business goals. The live stream provides actionable insights and practical code examples for implementing these techniques. The Q&A session addresses common questions and clarifies the capabilities and limitations of the Google Wallet platform.