Enabling Firebase Analytics on your mobile app is very easy with Andromo. No coding or complex steps required.

Please note that for this to work, you will need a Google Firebase account. If you don’t have one, create your account here.

First, you’ll need to add your app to Firebase.

1. After creating your Firebase account, log in and go to your console.

On your console’s left panel navigation, click on Analytics to expand the menu and then select ‘Dashboard’.

2. On the Dashboard select Android, to add your app. 

3. Enter the package name of your app on the succeeding screen and then click “Register app”.

4. Download the Firebase configuration file.

1. Now log in to your Andromo account.

2. Open your project editor.

3. In your Project editor, click on Services and check the box that says “Enable Firebase Analytics”

4. Upload Firebase configuration file (google-services.json)

Open your Project in Andromo

Go to your settings.

Scroll down till you find ‘Rate Us Options’

Create your pop-up messaging and select the timing and hit ‘Save Changes’. You’re all set.

Onesignal describes themselves as the “market leader in customer engagement, powering mobile push, web push, email, and in-app messages.” They have lived up to their name and certainly are among the top providers of push messaging services. Today, we’re going to show you how to create your free OneSignal account and begin sending push notifications to your Andromo app users.

To complete this tutorial, you will need the following:

1. An Andromo account
2. An Andromo app published in Google Play Store (if you don’t have one, follow this guide to build and then launch your app and then come back to complete the rest of this tutorial)
3. OneSignal Account
4. Google Firebase account

Creating your OneSignal & Firebase Accounts

To create your free OneSignal account, head over to https://onesignal.com and click “Start for Free”. OneSignal’s services are free. Enter your details and follow the on-screen instructions to confirm your account creation.

Next up, you’ll need to create your Firebase account.

Firebase is owned by Google. It’s an extremely powerful platform that allows you to manage a large number of Google products from one place. You will need to get a Server Key and Sender ID in order for OneSignal to be able to generate notifications for your Andromo ap.

If you don’t have a Firebase account, follow these steps to create your free account:

Head over to https://firebase.com and click the “Get Started” button. Follow the on-screen instructions to create your account.

1. After creating your account, go to the firebase console.

On the console, create a new project and name it whatever you want. Next, open your Firebase project.


On the project dashboard, click on the little cogwheel to open “Project Settings”.

One the Project Settings page, we are only interested in two things: the Server Key and Sender ID. These will allow OneSignal to communicate with Firebase in order to send push notifications.

Now head back to OneSignal and follow the steps below to complete your setup.

Click “Add App” and enter the name of your app.

Next, select Android as your platform.

You’re almost there. Now you need to choose your file type. Select Native Android.

Okay, now enter the Server Key and Sender ID you got from your Firebase account.

Hit save and you’ve completed setup in OneSignal.

Now log into your Andromo account. Activating OneSignal in Andromo is an easy one-click action.

On your ‘My Projects’ page, click on the drop-down menu on your app project and select ‘Edit Project’.

Click ‘Service’ and scroll down to the OneSignal section and tick the check box. That’s it, you’re done!

To learn how to create and send your push messages, read OneSignal’s documentation here: https://documentation.onesignal.com/docs/notifications

Google has provided the www.cookiechoices.org site that contains more information and suggests text that may be appropriate for the consent message that you present to your users. See the section titled "What do I put in my consent message?" which currently suggests the following text might be appropriate for an app:

We use device identifiers to personalise content and ads, to provide social media features and to analyse our traffic. We also share such identifiers and other information from your device with our social media, advertising and analytics partners. See details

Note that this is just a broad example, and may not reflect what is needed for your app, or an app that uses the minimum Google services. You will need to determine the appropriate notice text for your app based on the services it uses and any additional information you might collect.

Note also that Google's example includes a link in order to provide the user with more information. You will need to determine an appropriate web page to link to if you choose to include a link in your notice.

Please see www.cookiechoices.org for more information.

Implied Consent vs Explicit Consent

If your app does not retrieve or store any identifying information, and only collects anonymous data (all apps generated by Andromo may collect anonymous analytics data), you may be able to assume implied consent. Implied consent means that you only need to inform the user, and don't require the user's acceptance in order to proceed. This is the kind of consent that is required for the use of Google Services in Andromo such as Google Analytics and AdMob. With implied consent, you can use the Launch Notice feature on the App Info tab to inform the user.

However, if you've configured your app to collect additional user information, for example through a Website or HTML Archive activity, then your app may require explicit consent from the users. Explicit consent means the user must agree to the data collection in order to use the app. If your app requires explicit consent, you should notify the user in your license agreement, and use the License Agreement feature on the App Info tab to ask the user for consent the first time they launch the app.

User ID

This is the YouTube username. If you are going to show videos from your YouTube account you can find this value in the upper right-hand corner if you are logged in or in the URL to your channel. E.g. the following is the URL for my channel:

http://www.youtube.com/user/markIndigoRose?feature=mhee

My username can be seen after the '/user/' value in the URL and is markIndigoRose

Channel ID

This is the YouTube Channel ID. Some YouTube accounts contain a Channel ID instead of a User ID. You can find this value in the URL. For example, the following is the URL for the Google Developers channel:

https://www.youtube.com/channel/UC_x5XG1OV2P6uZZ5FSM9Ttw

The channel ID can be seen after the '/channel/' value in the URL and is UC_x5XG1OV2P6uZZ5FSM9Ttw

Video ID

This represents the ID of a specific video that has been uploaded to YouTube. You can get the video ID from the URL of a video. E.g. for the following YouTube video URL:

http://www.youtube.com/watch?v=qAShPzHEu1Q1

The video id is represented by the v parameter. So in this case the video ID is: qAShPzHEu1Q1

Playlist ID

This is the ID of a playlist on YouTube. This value can be found in the URL for the playlist that you want to use. E.g. the URL for my Andromo playlist is as follows:

http://www.youtube.com/user/markIndigoRose#p/c/C9834EB1F487C712

That playlist id is after the /c/ value in the URL. So my Andromo Playlist's ID is: C9834EB1F487C712

Updated YouTube accounts may have playlist URLs like so:

http://www.youtube.com/playlist?list=PLC9834EB1F487C712

In that case the playlist id is after the ?list=PL. So the playlist ID would be: C9834EB1F487C712

Google Analytics lets you measure user interactions with your app, anonymously tracking actions that the user performs, without sending any identifying information.

You can find detailed information about Google Analytics here: Android Native Application Tracking Overview

However, much of the information at that site deals with integrating Analytics into your app, which you do not need to do -- the integration is already done for you in Andromo.

This article will focus on how to start using Google Analytics in your Andromo project.

SDK Policy

Important By using analytics you agree to follow the Google Analytics SDK Policy. This means that:

You will give your end users proper notice about the implementations and features of Google Analytics

and:

You will either get consent from your end users, or provide them with the opportunity to opt-out from the implementations and features you use.

All Andromo apps allow the user to opt out of analytics in the application Settings. A notice will appear in the app's About dialog when analytics is enabled.

You may also want to add something like the following text to your Google Play descriptions:

(This application uses Google Analytics to anonymously track usage data within the application.)

Note: Andromo may also use Google Analytics to collect anonymous usage data in order to help guide improvements to the platform.

Get a Google Analytics Account

If you do not already have a Google Analytics account you can visit Google Analytics and sign up.

Note: it may take up to 24 hours for results to start showing up in a new account.

Get a Google Analytics App Property ID

Follow these instructions to set up a new Google Analytics property for your app. If the Analytics interface has changed, you can find the latest version of these instructions here. (Note that you do not need to download the SDK. All of the SDK programming and integration has already been done for you in Andromo.)

1. Sign in to your Analytics account. Click the Admin tab.

2. Find the account you want to add the new app property to. If you have a lot of accounts, click the All Accounts link just below the menu bar. Use the search box to help find the right account.

3. From the table, click the account name you want to add the property to.
If you want create a new account, click +New Account and skip Step 4. A new property is automatically added to all new accounts.

4. Click +New Property (web or app).

5. Select App as the type of property you want to track.
Andromo only supports App properties as of version 3.0.6. If you were previously using Web analytics in your app, you will need to create a new App property and update the ID in your Andromo project settings.

6. Type in an App Name.
Use a very specific and descriptive name.

7. Select an Industry Category.

8. Select your Reporting Time Zone.
This only affects the time that appears in your reports.

9. Click Get Tracking ID.
This is the property ID you will need to paste into your Andromo project settings.

Your app property ID will be in the following format: UA-XXXXX-YY

Enable Analytics in your Andromo Project

Now that you have your Google Analytics property ID, you need to add it to your Andromo project.

1. Edit your project, and select the Services tab.

2. Locate the Google App Analytics section, and check the box labelled Enable Analytics.

3. Enter your property ID into the App Analytics Code field.

4. Click the Save Changes button so that your changes are applied to the project.

Build

Now that you have the Analytics settings enabled, the final step is to build this version of your application and distribute it to your users (e.g. by publishing it on Google Play).

Note that it can take some time for results to begin showing up in Google Analytics, especially for a new Analytics account.

What will be Tracked

As your app is used, Google Analytics will track a wide variety of anonymous usage statistics, such as the number of visits to each activity within your application, and the average amount of time your users spent there. Your Google Analytics reports will show each activity using the title you selected for it in your project.

Note: in Google Analytics the activities are referred to as "Screens."

Update your Date Range

Note that the default date range for Google Analytics reports does not include the current day. You may want to adjust the date range near the top of the Google Analytics report page if you want to see results from the current day included.

Alternatively, you can use the Real-Time reports in Google Analytics which show a snapshot of the current data being tracked. Note that it may take up to 24 hours for Real-Time data to begin showing up in a new Google Analytics account.

Create a New Project in the Google Developers Console

Step 1 - Go to the Google Developer Console and sign in with your Google account, or create a new one.

Step 2 - Press the "Create Project" button.

Step 3 - On the New Project dialog, enter a project name in the "Project name" field and click the "Create" button (leave the Project ID as it's default).

Step 4 - In the sidebar on the left, select "APIs & auth" to expand the category, and then "APIs".

Step 5 - In the list of APIs, select "YouTube Data API".

Step 6 - Click the "Enable API" button to enable it in your project.

Step 7 - In the sidebar on the left, select "Credentials".

Step 8 - Under "Public API access", click the "Create new Key" button.

Step 9 - On the "Create a new key" dialog, select "Android key".

Step 10 - On the "Create an Android key and configure allowed Android applications" dialog, just click the "Create" button (LEAVE THE FIELD BLANK).

Step 11 - You should now see your application's "API key" value under the section "Key for Android applications". Copy that key into your Andromo project's "YouTube API Key" field.

Note: It can take some time for your API access to become fully enabled, so we recommend waiting about 15 minutes before testing your app.

Setting up your AdMob Publisher ID is a quick and simple process. Follow these steps and you'll have your AdMob Publisher ID in no time!

1. Go to admob.com and sign up.
http://www.admob.com

2. Choose Add Site/App from the menu

3. Pick 'Android App'

4. Fill in the App Name, Category and App description. You don't need to enter the Android Package URL as you won't know it until you've put your app up in Google Play anyways. Leave that completely blank.

(Make sure you remove all text from the URL field if you don't use it, e.g. remove the default market:// text.)

5. Click OK.

6. You'll then see a screen that talks about the AdMob Android SDK. This is the confusing part. Just ignore it and click the 'Go to Sites/Apps' button at the bottom. You don't need to download the SDK or anything. Andromo takes care of that part for you already.

7. Now you'll see a list of your Apps. Find the app you just added and hover over the name with your mouse. You'll see a Manage Settings button appear. Click it.

8. You'll see your Publisher ID up at the top. It is below the App Name and below the Site URL. It is labelled 'Publisher ID' and is a 15 character code (alphanumeric).

9. After enabling AdMob ads in your project, enter your AdMob Publisher ID into the "AdMob Ad Unit ID" field of your Andromo project.

However if you have published your application to Google Play it is strongly advised that you do not delete your project. The reason for this is that once you delete your project the package name associated with it will be lost forever. There will be no way for you to reclaim your package name on Andromo, and therefore no way for you to ever update your project again on Google Play.

If you are removing your application from Google Play or have not published your application to Google Play then you can feel free to delete it. Otherwise the best decision is to leave it just in case.

Sign into dev.twitter.com

To get your authentication keys you will need to sign into Twitter’s developer site. You can sign into the developer site using your Twitter account settings. If you do not have a Twitter account, you will need to sign up for an account at www.twitter.com.

Create a new Twitter Application

Next you will need to go to the apps section of the developer site, and create a new application using the "Create a new application" button.

You will be asked to provide a Name, Description, and Website for your app. You do not need to provide a Callback URL (you can leave that field blank).

The Name and Description fields are self-explanatory, but you might not be sure what to put for the Website of your app. If you have not created a website for your app, use the URL of the store listing for your app, or wherever people can download it.

Finally agree to their Terms of Service, pass a CAPTCHA, and your app will be registered with Twitter.

Get your Consumer Key and Consumer Secret

You will find your Consumer key and Consumer secret on the details tab when viewing your app on Twitter's developer site:

Copy and paste those values into each Twitter activity in your Andromo app. The Twitter activities will only work correctly if you provide these values.

Note: You will need to do this for each of your Andromo apps.

The starting position:
     

In the process of moving:

And the final result:
        

The Website Activity is designed to display a website that has been published to a web server. You can think of it as any url (such as http://www.andromo.com) that you browse to on a computer or device using a web browser such as Internet Explorer, Firefox, Chrome, Safari etc. Just like a web browser, when you visit the website, the pages are downloaded to the device so you can view them locally. This type can be useful if you want to reference content that is either not your own, or that you've already published online that you keep up-to-date.

The HTML Archive Activity is also designed to display web content, however it differs in where the content physically resides. Instead of the html pages existing on a web server and downloaded to the device, the HTML Archive Activity provides the ability to store the HTML content within the application so it can be read directly from the device. To implement this type, you would create the same html stucture that you would use if you were publishing it to a web server (making sure relative pathing is used), but instead create a zip archive of the html content files. This type can be useful when you want to include custom content that you don't want to make available online, or for performance reasons, since loading the content directly from the application will be more responsive than having to download it.

Assuming you have uploaded your App to Google Play and you see at least 100 installations, you should be making some money. However, if you're looking at your AdMob dashboard/reports and not seeing any movement (be patient - it can take 3-4 days for AdMob to approve your account and app - you won't see anything during this time), then you've likely missed one of the following steps.

Go through this list step-by-step and everything will work fine. Miss one of these steps, and it won't work. So, slow down and take this one step at a time.

First login to your Andromo account and click on the Project you want to edit. Then...

1. Go to the Monetization tab.

2. In the 'Banner Ads' section, check the box labelled 'AdMob Banners'.

3. Enter your AdMob Ad Unit ID (or legacy Publisher ID). Do the same in the 'Interstitial Ads' section if you want them enabled too. Make sure you enter it correctly, and choose the correct ad format ID (banners or interstitials) or you won't get any credit! We have a Knowledge Base article to walk you through this. Follow these instructions exactly: http://support.andromo.com/kb/monetization-options/setting-up-admob-ads

4. Click 'Save Changes'

5. Go to the 'Build' tab

6. Click 'Build My App'

7. We'll email your Android App (.APK) file to you.

8. Upload your app to Google Play

9. Wait a couple of days (it can take 3-4 for AdMob to activate your account and possibly a few days for your app to be found in Google Play searches etc). It can also take a few minutes for ads to start being served the first time you use it.

10. If people install your app and actually use it, you'll start seeing revenue in your AdMob account. Just because you have 20 people who have downloaded your app, doesn't mean you're going to make any money. You need hundreds, more likely thousands of installs in order to see things really moving.

Good luck!

The following steps are required to add Google Analytics to your Andromo app. If you're encountering problems, you can double check that you've followed these steps, or start over from scratch with a new Analytics app:

• Log into your Analytics account.
• Click the "Admin" button.
• Click the "New Account" button.
• Select the "Web Site" button under "What would you like to track?".
• Fill in the required info fields.
• Click the "Get Tracking ID" button.
• Accept the license.

That will show your "Property ID" in the format UA-XXXXXXXX-X at the top of the page on the "Tracking Info" tab.

• Enter that ID into your Andromo project's "App Analytics Code" field on it's Services tab, and make sure analytics is enabled ("Enable Analytics" checkbox is checked).
• Uninstall the current copy of your app from your phone (just to ensure you're using the new version of the app).
• Re-build your app, download, and install it on your phone.
• Run your app and navigate around a little bit.

At the top of the current page in your Analytics account, there is a "Reporting" tab in orange with items on the left side such as "Real-Time". Click the "Overview" tab to view the reporting feature. There can be an initial delay of 10 minutes or more before your app starts tracking its usage, so don't panic if you don't see immediate results. Once it does start tracking, the delay is maybe 10 to 20 seconds to see the changes of your usage in your app. The delay amounts may differ for everyone, as this was just a sampling of an experience using it.

Additional Checks

Some other things to check:

• Make sure your device has connectivity since it does need internet access in order to transmit the data.
• Make sure you don't have any other settings enabled, or apps installed on your phone used for blocking this type of transmission.
• If you're on a local network, it may be possible that you're behind a very aggressive firewall, so it may not hurt to test from another location if all else fails.

Currently supported by the Audio Player Activity:

• RTSP (RTP, SDP) over UDP
• HTTP progressive streaming
• HTTPS progressive streaming (Android 3.1 and newer)
• HTTP/HTTPS live streaming draft protocol:
• MPEG-2 TS media files only
• Protocol version 3 (Android 4.0 and above)
• Protocol version 2 (Android 3.x)
• Not supported before Android 3.0

Note that live streaming and HTTPS are only supported on devices running Android 3.x or newer.

Currently not supported by the Audio Player Activity:

• AAC+SBR (see below)
• RTSP/RTP over TCP (the RTP portion must flow over UDP)
• MP3 streams over RTSP/RTP

See Network Protocols for more information about the network protocols supported on Android devices.

Playlist Files

Andromo supports several kinds of playlist files, including M3U, PLS, and ASX.

They are all essentially text files that contain one or more stream URLs. When an audio player activity downloads a playlist, it interprets the contents and displays each URL as a separate track. Within the playlist, you can supply a title for each track along with the URL.

Using playlists also allows you to change the list of streams remotely, without needing to rebuild your app, simply by editing the playlist files.

AAC+

Andromo uses the standard Android audio framework, which supports AAC+ audio if it's supported on the device. (Stock Android officially supports AAC-LC, HE-AAC and HE-AAC v2 in MP4 or M4A containers.)

However, the audio framework and codecs are not always consistent across all device models due to changes or omissions made by the device manufacturers. Some devices will play AAC, some will only play specific variations, and some won't play it at all. It depends how audio was implemented in the device firmware.

Audio streams using AAC+SBR and PS (Progressive Stereo) in particular are not supported on most Android devices.

Note: It's possible that a stream which does not play in the standard audio framework used by Andromo can be played in a different music app on your device. Some apps provide their own support for AAC streams by using third party libraries. However, any app that includes the ability to decode AAC audio is expected to pay licensing fees, which can be very expensive. Note that these fees are legally required even if a free open source library was used.

Because Andromo uses the existing AAC playback ability within Android, you do not need to pay these licensing fees when using Andromo.

For this reason, you will most likely want to avoid higher bit rates, as they will quickly use up your available space. For most apps a bit rate of 128 kbps or less will be required in order to fit more than a few tracks into a single app.

Note: Andromo currently limits the size of each uploaded audio track to 10 MB. If your audio files are too big, you will need to make them smaller (e.g. re-encode them at a lower bit rate), or host them on a web site and let the users stream them instead.

Open the Google Cloud Console page.

If you have not created a project you will be prompted to do so. However if you have you will see a list of your projects. To create a new project press the Create Project button in the upper left corner of the page:

You will then be prompted to name your project and provide it with a unique ID:

If you have not already verified your account you will need to verify you account with Google using either the SMS or voice call method.

After verifying and creating a project, you will need to select APIs & auth from the menu on the left. Once the list of APIs load, you will need to find Google Cloud Messaging for Android in the list and enable it.

The next step is to generate your API Key. You can do this by first selecting Credentials in the APIs & auth section of the menu, followed by pressing the Create New Key button under Public API access.

On the Create a new key dialog, press the Browser key button.

On the Create a browser key and configure allowed referers dialog, leave the settings blank, and just press the Create button.

At this stage you should now see your Google API Key labeled API key listed under Key for browser applications as shown below. You'll need this key in order to create your app on AirBop.

The last bit of information you need is the Google Project Number which can be found in the Overview section:

This feature can be enabled on the "Services" tab of your Andromo project's settings.

Note: AirBop is not supported on Amazon devices as they do not have the necessary Google Services installed. AirBop will be disabled in the app when the Target Market is set to Amazon Appstore.

Features

This feature allows you to do the following:

• Send a notification message to your app with a title and a message.
• Allows you to pass a URL to open when the user clicks on the notification message.
• Allows you to specify an activity in your app to open when the user clicks on the notification message.
• Allows you to do nothing when the user clicks on the notification message.
• Allows the end user to enable or disable the app's notifications using a preference.
• Allows the end user to enable or disable the app's notification sound using a preference.
• Allows the end user to enable or disable the app's notification light using a preference.

Examples
Below are examples of what the user will see when a notification is sent to your app.

Notification Icon:

Notification Message (on Android version 4.1 or later):

Notification Message (on Android version 2.2):

App's Notification Preferences (available from the options menu):

Sign up for an AirBop Account

Visit https://www.airbop.com/users/sign_up to sign up for an AirBop account. If you already have an AirBop account, proceed to creating a Firebase project.

Once you sign up, you'll be emailed a 'Confirmation' notice. Before you can login, you must go to your email box, find the email and then click on the link found in the message.

You can then login to your AirBop account at https://www.airbop.com/users/sign_in.

Create a Firebase Project

Google has recently transitioned from the Google Cloud Console to the Firebase Console for creating new projects with cloud messaging. This means that the steps required to create your Google project have changed. Previous instructions can be found Here. The instructions below are for creating a cloud messaging project in the Firebase console to use in AirBop and Andromo.

1. Open the Firebase Console page. You'll be required to sign in with a Google account.

2. If you have not created a project you will be prompted to do so. However if you have you will see a list of your projects. To create a new project press the "Create New Project" button.

3. On the "Create a project" dialog, enter a project name, select your country/region, and then press the "Create Project" button.

4. Click the Settings button in the upper left corner next to your project name and select "Project Settings".

5. On the "Settings" page, select the "Cloud Messaging" tab. This page contains the keys you'll need to enter in your AirBop and Andromo projects as discussed in the steps below.

Create an AirBop Project

Once you've created a project in Firebase, the next step is to create a project in AirBop:

1. Log in to your AirBop account at www.airbop.com.

2. After logging in, you'll see the Dashboard, where any apps you have already set up with AirBop will be listed. Select the "+ Add New App" link to begin adding a new app.

3. Enter the name of your app in the "App Name" field. This is a label that you can use to identify the app in your AirBop account. This value is only used for organizational purposes.

4. Enter your app's Java Package Name. This value can be found on the "App Info" tab of your Andromo project beside the label "Package Name". It will be a value such as com.andromo.dev12345.app12345. If you're using a custom package name, you would copy the value from the "Custom Package Name" field instead.

5. Copy the "Legacy Server key" value from your Firebase project's "Cloud Messaging" tab to the "Google API Key" field.

6. Click the Save changes button to save the information you entered. After you've saved your changes, AirBop will generate an AirBop App Key and App Secret for your app and display it next to the labels "AIRBOP_APP_KEY" and "APP_SECRET" on your app's Info tab. These values are needed in your Andromo project discussed in the next step.

Enable AirBop in your Andromo Project

Once you've created your Firebase project and AirBop project, the next step is to enable and configure it's settings in your Andromo project.

1. Select the "Services" tab of your Andromo project.

2. Select "Enable AirBop Messaging" under "AirBop Push Message Notifications".

3. Copy your "AIRBOP_APP_KEY" value from your AirBop project into the "AirBop App Key" field. You can find this value on the "Edit" tab of your AirBop project's settings.

4. Copy your "APP_SECRET" value from your AirBop project into the "AirBop App Secret" field. You can find this value on the "Edit" tab of your AirBop project's settings.

5. Copy the "Sender ID" value from your Firebase project into the "Google Project Number" field. You can find this value on the "Cloud Messaging" tab of your Firebase project's settings.

6. Press the "Save Changes" button to save the your settings.

Testing Registration

After you've saved the Push Message settings in Andromo, the next step is to build, download, and install your app on your device. In order for your device to register with GCM and AirBop, your app needs to be run to perform the registration. After running your app you should see your device listed under "Recent device registrations" on the "Info" tab of your app's settings on the AirBop website. Once your device is successfully registered, you're ready to send a notification message to it.

 Sending Notification Messages

General information about sending messages to your app can be found in the AirBop knowledge base article, 'Sending a New Message' found here: http://support.airbop.com/kb/dashboard/sending-a-new-message

The following AirBop features are NOT supported in Andromo apps:

• JSON Mode of Message Details with custom values. Values other than "title", "message" and "url" will be ignored.
• Label setting of Device Targeting.

Target URL Handling in Andromo
The Target URL setting of the Message Details in AirBop controls what you want to display when the user clicks on the notification. Andromo provides three different options for the handling notification clicks:

• Do Nothing - If you leave the Target URL blank, nothing will happen when the user clicks on the notification message. It will just be dismissed.
• Open a Website - If you specify a website URL such as http://www.andromo.com, it will be opened in the user's default web browser application when the user clicks on the notification.
• Open an Activity in your App - In addition to URL handling, Andromo supports a special type of target URL that enables you to open a specific activity in your app when the user clicks on the notification.

The Target URL format used to open an activity is as follows:

andromo://<<internal-activity-identifier>>

Each activity contains an internal unique identifier that can be referenced for opening it. You can find each activity's reference URL in the "Activity URL" section of the activity's "Edit" page, below its Example Screenshot. Each activity's settings can be accessed from the "Activities" tab, by clicking the activity name or icon, or by selecting "Edit" from the Action dropdown next to the activity you're looking for. Below is an example of this value:

where "website158941" is the internal identifier for that particular activity. This value will be different for each activity in your project.

If an invalid activity identifier is used as the Target URL in AirBop, the notification will open the app's dashboard instead. If you'd like to specifically open the dashboard, you can specify the following value:

andromo://dashboard

The following Andromo activity types are NOT supported using the Target URL feature:

• Email
• Google Play
• PDF
• Phone