App-to-app verification
Issuers can offer app-to-app verification as an option for completing a yellow path ID&V challenge when provisioning a token. App-to-app verification is configured through your TSP and does not require any configuration by the Google Pay team. This page explains how your app interacts with the Google Wallet app based on the provisioning instructions we receive from your TSP.
When users choose to activate app-to-app verification, Google Wallet will invoke the issuer app by calling the Android Activity specified by the issuer through their TSP configuration. Once the user has verified their identity, the issuer app passes control back to Google Wallet to finish the provisioning flow.
If the app is not installed on the user's device, Google Wallet will open the Play Store page for your app. After installing the issuer app, the user needs to restart the flow.
To support app-to-app verification, you will need to:
- Configure TSP settings to enable the app-to-app flow. to support the app-to-app flow.
The flow below shows an abstract user experience for the app-to-app verification process:
TSP settings
Issuers must provide the parameters below to their TSP. Google Pay receives these parameters from the TSP during the tokenization process and uses them to call your app.
| Parameter | Example | Description |
|---|---|---|
| Package Name | com.example.myapp | The package name (applicationId) identifies the issuer mobile app that Google Pay should call during when invoking the Intent to start the app to app flow. If the app is not installed on the cardholder’s mobile device, the user will be prompted to install it from the Google Play Store. |
| Action | com.example.bank.action.ACTIVATE_TOKEN | When calling your app, we create an explicit Intent. The action must be provided in it's fully qualified form, including the package name. Also, the action must be specific for use in token activation. |
| Extra text | This parameter is used to pass extra data that will be included in the Intent. It is typically a JSON structure, Base64-encoded. The value of this string is opaque to Google and will be provided as-is in the standard field EXTRA_TEXT. |
Warning: You must not pass security, PCI, or authentication information in the EXTRA_TEXT field.
App development
When a user selects the app-to-app method to verify their identity, the issuer app must:
-
.
- Authenticate the cardholder. .
- Return the user to Google Wallet by calling activity.setResult(RESULT_OK, . )
Receiving the intent
When a user chooses to verify their identity using the issuer's app, Google Wallet calls your app using the package name, action, and EXTRA_TEXT provided to us through the TSP. To receive the Intent from our call, you will need to update your app manifest and create an activity to activate the token.
App manifest
Issuers must update the Android manifest of their mobile app to handle the Action so Google Wallet can call it during the app-to-app flow.
Once your app's manifest has been updated, Google Wallet will be able to call your app to start the token activation activity in your app.
Token activation activity
To complete activation, your app must start an activity to complete token activation using the activation parameters passed in the Intent . The following code sample demonstrates how you can access the data from the EXTRA_TEXT in the Intent .
Activating the token
There are two ways to activate tokens:
- By calling the TSP API to activate the token directly.
- By obtaining an activation code from the TSP and passing it to Google Wallet in the Activity result.
Activation using TSP APIs
When the card issuing bank mobile app uses the TSP API to activate the token, the card issuing bank app receives the Intent , authenticates the cardholder, and activates the token by calling the TSP’s API. At the end of this flow, you simply indicate to Google Wallet whether or not the activation was successful when returning the user to Google Wallet. Review your TSP technical documentation for details on how you can activate tokens using their APIs.
When activating through the TSP API, your app does not return a code to Google Pay and the token activation happens “out of band” from the Google Pay perspective.
Below is a code sample for how to return the user to Google Wallet after the activation process is complete using the TSP API technique.
Activation code
When the card issuing bank mobile app obtains an activation code from the TSP and returns it to Google Wallet, the issuer app returns an activation code to Google Wallet using an intent result. Consult with your TSP on how to generate an activation code, sometimes called an authentication code or Tokenization Authentication Value (TAV).
Below is a code sample for how to return the user to Google Wallet with an activation code.
Mobile app security
The card issuing bank mobile app must have the ability to adhere to the Android security model, especially concerning the use of intents. Upon receiving the intent, use Activity.getCallingPackage to validate that the calling activity is actually Google Wallet as indicated below.
Make sure that your mobile app does the following:
- Authenticates the cardholder's identity.
- Obtains cardholder consent to every digitization request.
- Verifies that the digitization relates to the correct cardholder account.
Review your TSP’s technical documentation on token activation and the Android developer site for sending, allowing, and receiving Intents .
All rights reserved. Java is a registered trademark of Oracle and/or its affiliates.
Website To App — Web to app we
Website To App — это приложение, которое конвертирует веб-сайт в приложение Android и публикует его в игровом магазине.
С помощью Website To App вы можете за минуту создать приложение andriod без исходного кода и распространять свое новое приложение. Кроме того, мы предоставляем бесплатную функцию «Push-уведомления и сервис Admobs», которая может отправлять уведомления.
Это приложение включает функцию, которая позволяет перейти на выбранный веб-сайт из определенной кнопки меню, и ее также можно использовать на смартфоне и планшете.
Конвертируйте и распространяйте свой сайт на собственное приложение для смартфона!
Преобразуйте свой блог в приложение для смартфона!
Создайте свое собственное приложение без домашней страницы!
Теперь это возможно с веб-сайта для приложения приложения в очень минимальном количестве
Я хочу, чтобы вы сегодня использовали Website To App, чтобы создать собственное приложение без лишних затрат времени.
[Основная функция]
— Функция настройки — настройка приложения, имя приложения, значок приложения, имя пакета и т. Д.
— Установка первого экрана загрузки
— Добавление / редактирование / удаление кнопки меню и настройка цвета фона меню, цвета шрифта и значка кнопки.
— Добавление / редактирование / удаление пользовательских страниц.
— Отображение названия, адрес электронной почты, контактный номер и т. Д.
— Отправка push-уведомления.
Мы надеемся, что вы используете это приложение с пользой.
Пожалуйста, свяжитесь с нами, если у вас есть какие-либо проблемы или для улучшения функций, настройки и т. Д.
Two Apps Are Better Than One
An App-to-App Experience That Drove 500% More Installs
SpotHero launched in 2011 to help get drivers everywhere, easier. Letting drivers search, compare, and book a parking spot in advance, the mobile app has parked over 8 million cars across the country and saved drivers hours of searching for a parking spot.
As an app-first company, we are tasked with answering the same million dollar question facing all app-based services — how do we convince someone that your app should be the next to take up precious space on a person’s device? Our answer: prove they can’t live without it. Remember when you actually had to step out onto the street to hail a cab? Thanks, Uber.
But when is the optimal time to market a “can’t live without us” message to our core on-the-go consumer? In the morning as they multi-task brushing their teeth while watching the news? During their mid day “I need to pay attention to this conference call, but also want to know what’s happening on Facebook” moment? At night while they’re multi-tasking cooking & watching primetime?
Instead of trying to avoid the day-to-day clutter, we decided we should join it.
Our core consumers are on-the-go. They’re busy and want to get where they’re going as efficiently and price consciously as possible. Insert Waze, an app that helps navigate these drivers to get from point A to point B with ease. It’s the perfect marriage of sending the right message, at the right place, at the right time. Your’e in the car wondering where you’re going to park at point B when you see a SpotHero ad letting you know we can help.
So we launched our first campaign with Waze in September of 2016. The hope was that if we position ourselves as a must have app, users would choose to install. After just two months of live media, brand recall was 156% higher for users exposed to our ads. Big win! We knew that our message wasn’t going unheard, but what we weren’t seeing was a correlated lift in lower funnel metrics like app installs or in app purchases. Not such a win. So we began to brainstorm how we can optimize the mobile experience on Waze to provide a benefit to our commuting drivers beyond generating awareness of our service. What would they care about most?
In April of 2017, we changed the user experience. Instead of prompting users to install our app after seeing one of our ads, we shifted the call to action to actually book a parking spot. After all, that’s what our app is there for, right?
In order to make this possible we enlisted the help of Branch deep links, which allow us to get Waze users successfully from one point in the Waze app to another specific point in the SpotHero app. Today, users can choose to book parking at a specific location within Waze and are magically transported to the same location within SpotHero, creating a seamless experience from drive to park.
By providing this direct app-to-app experience, we effectively increased app installs by 532% in the first two months.
And we didn’t stop there.
Even though we had successfully optimized the user flow, our creative messaging still featured general brand awareness copy. We saw this as an opportunity for further growth, so we enlisted the help of our design team and updated our ads to let users know they can book a SpotHero space by searching for parking within the Waze app. And people noticed.
Ad engagement increased by 3X with a corresponding 75% increase in in-app purchases.
Winner winner chicken dinner. But we didn’t stop there either.
With the success of this initial app-to-app partnership, live in our top 3 markets, we expanded to cover SpotHero’s core 9 markets, leveraging thousands of Branch deep links in the process. Early results show a 2X increase in installs in just the first two weeks of the 9 market test.
The success of this campaign is two-fold. We found a context where our app made sense, and we found a way to positively effect a person’s day. By inserting ourselves into a part of someone’s daily commute with a way of making that commute easier, we not only built positive brand awareness but transitioned Waze drivers into SpotHero customers.
*This post was written as an entry to the Mobile Growth Stories competition sponsored by Branch Metrics.
The Difference Between App to App and Web to App Advertising
Mobile devices – and the apps contained within them – are increasingly «always on.» This presents a perfect opportunity for advertisers to drive meaningful engagement where messages are an integrated and seamless part of the user experience.
Mobile devices – and the apps contained within them – are increasingly “always on.” This always on phenomenon presents a perfect opportunity for advertisers to drive meaningful engagement where messages are an integrated and seamless part of the user experience.
App to App vs. Web to App
Mobile app and mobile web are the two mediums that advertisers can use as a forum for their marketing and advertising offers.
Mobile App: According to Flurry 86 percent of the time people spend on their mobile devices is within apps. In fact, they recently released a report describing how “Mobile Addicts” launch apps more than 60 times a day. This is why mobile app inventory is among the most attractive inventory for advertisers: it’s where most of the market attention is focused.
Many app publishers also have valuable first-party behavioral and demographic data that advertisers can use for enhanced targeting. As a result, mobile app inventory is the highest priced segment of the mobile inventory spectrum.
Mobile Web: Mobile web means your creatives will be shown in their proper mobile sizes, resulting in a higher rate of visibility and engagement. Mobile web inventory is similar to mobile app inventory in terms of creative sizes, but the ad shows in a web environment rather than an app environment.
A user can navigate between an ad and the offer destination in two ways:
App-to-app is the most common user experience where:
- User is in one app (in-app) such as the “Shazam” app and sees an ad in the app for another app (such as the “Spotify” app).
- User clicks on the ad, which opens the respective App Store (or opens the “Spotify” app if it’s an existing user who already installed it).
- User installs or opens the “Spotify” app (assuming it’s not an existing user).
Web-to-app is the scenario where:
- User is in a web browser on their mobile device (such as Safari or Chrome on an iOS device).
- User sees an ad on a web page for the “Supercell Clash of Clans” app.
- User clicks on the ad, which opens the respective App Store (or opens the “Clash of Clans” app if it’s an existing user who already installed it).
- User installs the “Clash of Clans” app (assuming it’s not an existing user).
Measuring App to App vs. Web to App Campaigns
As you start developing your mobile campaigns, you’ll want to make sure you have the right technology in place to measure the overall success of your campaign and gain insight into how to optimize specific channels to drive better results.
Resources
Analytics The 2023 B2B Superpowers Index
Analytics Data Analytics in Marketing
Digital Marketing The Third-Party Data Deprecation Playbook
Digital Marketing Utilizing Email To Stop Fraud-eCommerce Client Fraud Case Study
The attribution methods may vary, depending on where users are coming from – mobile app vs. mobile web.
While you can use a few methods to attribute app installs and in-app events, the method you implement depends on a combination of three factors:
- Platform/App Store: iOS/Apple iTunes App Store, Android/Google Play Store, Amazon Appstore for Android, etc.
- Engagement Type: Click-through vs. View-through measurement
- Conversion Type: Install or In-App Event
The main difference between app-to-app and web-to-app install attribution is that you can only do Fingerprint Matching with iOS. With Google Play, you can use the Google Install Referrer string for both app-to-app and web-to-app install attribution.
This chart below shows four attribution methodologies along with the engagement and conversion type. You can see that the attribution method for installs varies based on what platform you are running campaigns on.
While methods vary between platforms and stores when performing install attribution, the methods are very similar between Android and iOS apps (in both app-to-app and web-to-app scenarios). This similarity leads to a very big advantage when it’s time to attribute events via the Open URL with a Click ID method (to attribute app-to-app and web-to-app install events).
The chart below has the same matrix set up but shows the results if you want to measure event attribution (versus install attribution as above).
Summary
Allocating marketing resources to mobile can help you tap into a significant market potential and make meaningful audience connections. The combination of beautiful creative, smart targeting, and accurate measurement will set you up for a successful mobile campaign.
I’d love to hear your experience and results when running app to app and web to app mobile campaigns in the comments below!