Skip to main content
Add CTA buttons to your web landing pages with Airbridge and measure their performance.

​
Understand CTA buttons

To increase conversions from users who arrive at your web landing page, add a call-to-action (CTA) button to the page. With Airbridge, you can send users who click the CTA button to the destination you want and measure the button’s performance. Use CTA buttons to send users who reach your web landing page from an ad or content to a specific in-app page or to the app store, depending on whether they have installed the app. Creating CTA buttons for web landing pages involves the following steps.

​
Before you begin

To add CTA buttons to your web landing page, ask your developer to build them. Prepare all of the following before you make the request.

​
User redirect paths

Decide where to send users who click the CTA button on your web landing page, depending on conditions. Your developer needs these paths to build CTA buttons that send users to the right destinations. Prepare the following for each redirect path.

​
Information to view in reports

When users click a CTA button on your web landing page, you can view information on the click in reports. Define the CTA button information and campaign information to view in reports.

​
CTA button information

NoteTo analyze the performance of campaigns that use CTA buttons accurately, we recommend defining all of the information below. Without it, it’s hard to tell in reports which campaigns used CTA buttons.
Define the CTA button information to view when you select each GroupBy in reports. All items below are optional, and the fields are for your developer. You can define up to three pieces of information per button and view them in reports. You can define any information related to the button in CTA Param 1, CTA Param 2, and CTA Param 3, including items not listed in the examples below.

​
Campaign information

NoteTouchpoint information is not collected when users reach your web landing page in the following ways. In these cases, the campaign information entered in defaultChannel and defaultParams appears when you select touchpoint GroupBys in reports.
  • Users click an ad without a tracking link or UTM parameters
  • Users enter the web landing page URL directly
Define the campaign information to use when touchpoint information is not collected, such as when users click an ad without a tracking link or UTM parameters or enter the web landing page URL directly. For example, use this campaign information to identify users who reach your web landing page organically. All items below are optional, and the fields are for your developer.

​
Create CTA buttons

There are two ways to create CTA buttons with Airbridge: using the openDeeplink function and using tracking links. We recommend the openDeeplink function, and this article focuses on it. For the attribution scenario of each method, see Attribution scenarios for CTA buttons on web landing pages.
This setup requires code changes. Ask your developer for help.Share this Create CTA buttons section with your developer, along with the user redirect paths and the information to view in reports that you prepared above.

​
Install the Airbridge SDK

Install the Airbridge App SDK and Web SDK for the platforms you use.

​
Set up CTA buttons

Follow the documentation below to apply the openDeeplink function to your CTA buttons. Set up the redirect paths based on whether users have installed the app, and set up the information to view in reports.

​
View performance

View the performance of your CTA buttons in Airbridge in the following ways. If you defined CTA button information, use CTA Param 1, CTA Param 2, and CTA Param 3.
If you defined CTA button information, select CTA Param 1, CTA Param 2, and CTA Param 3 as GroupBys. If you didn’t define this information, it’s hard to tell which campaigns used CTA buttons when you view reports.
CTA Param 1, CTA Param 2, and CTA Param 3 in the GroupBy search results
For example, say your web landing page has two buttons. You set CTA Param 1 to CTA for both buttons to mark that a CTA button was used, and set CTA Param 2 to Top Banner and Bottom Banner by button position. Reports then show this information as follows. First, select CTA Param 1 as a GroupBy. The value CTA shows which performance came from CTA buttons.
Actuals report with CTA Param 1 selected as a GroupBy
Then select CTA Param 2 as a GroupBy to view the performance of each CTA button by button position.
Actuals report with CTA Param 2 selected as a GroupBy
When you export app raw data, select CTA Param 1, CTA Param 2, and CTA Param 3 in the [Select Event Properties] step.
CTA Param 1, CTA Param 2, and CTA Param 3 selected in the Select Event Properties step
You can check web and app events in real time. For example, check the Open (Web) event on the [Web Real-time Log] page, and then check the Deeplink Open (App) event and the events that follow it on the [App Real-time Log] page. To view CTA button information, click the event row and check attributedCtaParam1, attributedCtaParam2, and attributedCtaParam3.
NoteThe Airbridge Web SDK automatically collects the Move to App (Web) event when a CTA button is clicked. Therefore, the Channel of this event is always airbridge.websdk.