Are you the primary Localytics go-to in your organization? Then, this is your how-to section for basic day-to-day management of the platform.
App keys are one of the best mechanisms for providing top-level separation of data. Best practices dictate one app key for each app, device platform, and environment. Creating separate app keys enables you to easily uncover insights between platforms, send more customized messaging campaigns by platform, and separate test data from production. Use cross-app analytics to compare data across multiple app keys.
|Name||For an app platform with both iOS an Android versions, create new app keys with the following names:
• My App [iOS] Test
• My App [iOS] Production
• My App [Android] Test
• My App [Android] Production
|Platform||Select the appropriate device platform|
|Category||Select the appropriate category. The Usage report will include data for benchmarking performance against your selected category|
|Select icon (optional)||Upload your icon to display in the selector dropdown|
Choose the time zone in which you want your data to be reported.
Hint: choose the time zone of your company headquarters or UTC. Your marketing campaigns will be delivered according to this time zone, except when you specify delivery in a user's time zone.
|Customer Value||Select the value you want to use for tracking in your reports. Choose Tracked as Money to track $$$ related to revenue or purchases. Choose Raw Data if you want to map the value to another metric such as "movies watched" or "ads viewed."|
|Custom Dimension Labels||Custom Dimensions are assigned a numeric value during the tagging process. Apply a label here to describe and display Custom Dimensions in the Dashboard. For example:
|Channels (for Android)||
Starting with Android Oreo (v8.0) you're required to specify a channel (shown as a category on the end user's device) for all push messages sent. You’ll need to specify channel information within your app or platform. Be sure the information is kept up to date in Localytics. Push messages sent without a specified channel will not reach your end users.
To avoid this, Localytics creates a default channel for push messages when none is specified. This default channel assumes basic default specifications such as importance, name (shown as the channel ID), sound and vibration setting. It is un-editable within the Localytics dashboard. Check out the official Android information on creating channels here.
Select the gear icon in the top bar of each app key to manage your app keys or to add push messaging certificates.
Follow the instructions to add your iOS Push Certificate and/or your Google Cloud Messaging API key to enable push messaging. Prevent push errors by correctly matching development and production certificates with the Push Mode drop-down.
Most of the time creating an app in the Localytics Dashboard will be covered by our onboarding team. If, however, you'd like to add another iOS/Android app, web app, an API, etc. you can do so from the settings page.
From your Localytics Dashboard select the ellipse and choose Settings.
You'll land on the Apps section, where you'll see a list of all of your apps in Localytics. To create a new app, select the green + Create an App button.
From here you'll be able to add your app to Localytics. Make sure to fill out all of the required fields (Name, Platform, Category, and Time Zone).
If you're using the Events API (to connect systems like your point-of-sale system) choose the Platform of API.
Fill in any additional Custom Dimensions and scroll down to Save your settings.
Localytics' Rapid Push Verification helps you confirm that you have properly configured your app to receive Localytics push notifications and detects any issues with your integration, providing guidance on how you can fix the problem.
To perform a Rapid Push Verification test, go to the Localytics Dashboard > Settings. Scroll down until you see the app you want to test and click on Test Push Integration. Then follow the instructions.
For more step-by-step instructions to successfully test or troubleshoot your push integration, check out the video below. For more on how Rapid Push Verification works and its capabilities, you can also read this blog post.
In the next section, we'll walk through user permissions. This section is intended to help you decide what level of access or permission to give your Localytics users based on their roles.
To access user permissions, click on the Users tab. Here's you'll be able to invite new users and assign their permissions. Once you set a new user's default permission and role, they'll be sent a confirmation email.
Permissions are assigned at one of two levels:
• Org-level permissions apply to all applications and platforms included in your Localytics account.
• App-level permissions are more granular and provide access only to an individual app.
Org-level permissions provide access to all apps within your Localytics account. You can assign users one of three roles depending on their job: Admin, Creator, or Member. Each role has its own level of access.
An Admin user has access to all actions available within the Localytics dashboard and can add users, remove users, and manage their permissions.
A Creator is unable to manage other users but is able to perform task-oriented actions: create apps, modify app permissions, share custom dashboards, as well as bulk upload Profiles.
A Member has read-only access and is unable to perform any specific actions. Here's a full breakdown of those permissions:
|Manage default permissions||✓|
|Create new apps||✓||✓|
|View app permissions||✓||✓|
|Modify app permissions||✓||✓|
|Share custom dashboard||✓||✓||✓|
|Profile Bulk Upload||✓||✓|
|View Localytics API Key||✓||✓|
Application-level permissions let users access and manage a particular app. There are three application-level roles: Owner, Marketer, and Viewer.
An Owner has access and permission to perform all actions within a given app. This includes things like building and managing audiences, campaigns, and reports. Owners also control the events for filtering the data.
A Marketer has the ability to create and manage messaging campaigns but can’t create or manage audiences, reports, or events.
A Viewer is similar to the Member at the organization-level and has read-only access to a limited view of the dashboard functionality.
|View app data||✓||✓||✓|
|Create or edit Attribution campaigns||✓||✓|
|Create/edit Marketing campaigns||✓||✓|
|Profile Bulk Upload||✓||✓|
|Modify app settings||✓|
Need help figuring out which user should get which type and level of permission?
A few quick guidelines may help you figure out the correct Localytics permission assignments in your organization.
- Think about the role of an individual—do they need all-encompassing org-level permissions or will they be working on specific tasks within a specific app?
- Be careful when you assign multiple individuals the same permission levels. Make sure they know it's their responsibility to coordinate their Localytics activities if they're working on the same campaigns or apps.
- Use Member and Viewer roles as your default. These are "do no harm" assignments for project stakeholders that provide read-only access. You can always upgrade them if you need to.
You can change permissions by app, user, or permission type. To modify any permissions, head to the Permissions section under Settings.
To modify app-level permissions, select the app in the By App menu. To change by user, select your user in the By User menu.
If you want to modify permissions for several users at the same permission level, you can filter by permission level using the By Permission menu once you select an app or user.
Click on the Organization tab in Settings to view your active Localytics analytics and marketing subscriptions. You can also edit your organization name and view a summary of your billing method.
Localytics allows you to manage the Events and Event Attributes that are displayed within Localytics. Use the Events tab of the Settings menu to perform actions like renaming Events, disabling Events, disabling Event Attributes, or informing Localytics to treat numerical Attributes as numbers (rather than text).
When you rename Events, you are simply assigning a different display name within Localytics; your event will still be tagged and named the same way within your code base. For convenience Localytics allows you to alter the name that gets displayed within the dashboard.
When you disable Events or Attributes, you're telling Localytics to stop collecting this information moving forward. All historical data will be preserved and archived.
Localytics attempts to detect if the values that have been captured as an Event Attribute are numeric. When this is the case, we'll attempt to display these as numeric values (rather than text). This means, for example, that we will visualize results by bucketing numeric values.
If, however, Localytics has made a mistake, this can be easily adjusted by toggling the on or off Enable Numeric Features, which is only visible for Event Attributes (not Events). To see all Event Attributes associated with an Event, select the carrot next to the Event name.
For more on Events and Event Attributes, check out this helpful guide.
Localytics makes it easy to manage and share your daily Localytics reports and analytics.
To see a summary of the reports scheduled to be emailed to you, simply click on the Scheduled Reports tab in Settings.
If your subscription includes any custom reporting from Localytics, you'll be able to access these reports from the Settings page. Simply select Custom Reports from the Settings menu to access your custom dashboards.
If you're importing or exporting data from Localytics, you can do so from the Settings menu. Here you'll be able to manage your imports/exports. Simply select Data Imports or Data Exports for more information.
You can access imported Audiences from the Data Imports page. For more on Audience Imports, check out our developer guide.
If you're exporting data on a regular cadence, you'll see those exports available on the Data Exports page of your Settings menu. Here you'll see Current Exports and Recently Disabled Exports. These will be divided between Audience exports and Profile exports.
The Localytics API Key grants to access to all of Localytics APIs. To access your Localytics API Key select API Keys from the top menu in Settings.
You can use the regular API key for access to all APIs. For more limited access to the Query API key, please contact support.
Localytics provides the ability to define and set custom password policies via our Password Policy tab in Settings. You can choose to select either our Strong or Very Strong pre-configured policies or define a custom policy to meet your specific needs.
|Security Level||Total Characters||Uppercase||Lowercase||Numbers||Special Characters|
To set a custom policy, simply select Custom, and add your specific length and complexity requirements.
Alternatively, you can also limit the reuse of previously used passwords, and set an expiration policy.
In addition to the policy settings you select, Localytics automatically prevents the use of common or easily guessable passwords.
It’s important to note that password policies are set to a specific organization. In instances where a user belongs to more than one organization, Localytics will enforce a composite set of password requirements to ensure that the most secure settings are respected. To ensure the strictest security, we'll choose the most aggressive requirements from each organization the user belongs to.
Need to reset your Localytics password? Go to the login screen and select Forgot Password.
Enter your email address and hit Send Password Reset Instructions.
We’ll send you an email with a change your password link that will allow you to change your password. Finally, enter your new password. Confirm it and you’re all set.