Skip Navigation
Show nav
Heroku Dev Center
  • Get Started
  • Documentation
  • Changelog
  • Search
  • Get Started
    • Node.js
    • Ruby on Rails
    • Ruby
    • Python
    • Java
    • PHP
    • Go
    • Scala
    • Clojure
  • Documentation
  • Changelog
  • More
    Additional Resources
    • Home
    • Elements
    • Products
    • Pricing
    • Careers
    • Help
    • Status
    • Events
    • Podcasts
    • Compliance Center
    Heroku Blog

    Heroku Blog

    Find out what's new with Heroku on our blog.

    Visit Blog
  • Log inorSign up
View categories

Categories

  • Heroku Architecture
    • Dynos (app containers)
    • Stacks (operating system images)
    • Networking & DNS
    • Platform Policies
    • Platform Principles
  • Command Line
  • Deployment
    • Deploying with Git
    • Deploying with Docker
    • Deployment Integrations
  • Continuous Delivery
    • Continuous Integration
  • Language Support
    • Node.js
    • Ruby
      • Working with Bundler
      • Rails Support
    • Python
      • Background Jobs in Python
      • Working with Django
    • Java
      • Working with Maven
      • Java Database Operations
      • Working with the Play Framework
      • Working with Spring Boot
      • Java Advanced Topics
    • PHP
    • Go
      • Go Dependency Management
    • Scala
    • Clojure
  • Databases & Data Management
    • Heroku Postgres
      • Postgres Basics
      • Postgres Performance
      • Postgres Data Transfer & Preservation
      • Postgres Availability
      • Postgres Special Topics
    • Heroku Redis
    • Apache Kafka on Heroku
    • Other Data Stores
  • Monitoring & Metrics
    • Logging
  • App Performance
  • Add-ons
    • All Add-ons
  • Collaboration
  • Security
    • App Security
    • Identities & Authentication
    • Compliance
  • Heroku Enterprise
    • Private Spaces
      • Infrastructure Networking
    • Enterprise Accounts
    • Enterprise Teams
    • Heroku Connect (Salesforce sync)
    • Single Sign-on (SSO)
  • Patterns & Best Practices
  • Extending Heroku
    • Platform API
    • App Webhooks
    • Heroku Labs
    • Building Add-ons
      • Add-on Development Tasks
      • Add-on APIs
      • Add-on Guidelines & Requirements
    • Building CLI Plugins
    • Developing Buildpacks
    • Dev Center
  • Accounts & Billing
  • Troubleshooting & Support
  • Add-ons
  • All Add-ons
  • FollowAnalytics
FollowAnalytics

This add-on is operated by FollowAnalytics

Next-generation Low Code platform for Rapid Mobile App Development

FollowAnalytics

Last updated April 04, 2020

Table of Contents

  • Provisioning the add-on
  • Local setup
  • Using FollowAnalytics
  • Using with Rails from 3.x to 5.x
  • Migrating between plans
  • Removing the add-on
  • Support

FollowAnalytics is an add-on for providing mobile apps analytics, user profiles and engagement.

Adding user profiles to an application allows you to add context to your service, to personalize your communication with your customers and to broaden your customer knowledge.

FollowAnalytics is accessible via an API and offers a client library for Ruby.

Provisioning the add-on

FollowAnalytics can be attached to a Heroku application via the CLI:

A list of all plans available can be found here.

$ heroku addons:create followanalytics
-----> Adding followanalytics to sharp-mountain-4005... done, v18 (free)

Once FollowAnalytics has been added, the FOLLOWANALYTICS_SOR_IDENTIFIER, FOLLOWANALYTICS_API_KEY and FOLLOWANALYTICS_API_TOKEN settings will be available in the app configuration and will contain the credentials required to exchange profile data with FollowAnalytics.

This can be confirmed using the heroku config:get command.

$ heroku config:get FOLLOWANALYTICS_SOR_IDENTIFIER
a3e4b65caa34001

After installing FollowAnalytics the application should be configured to fully integrate with the add-on.

Local setup

Environment setup

After provisioning the add-on it’s necessary to locally replicate the config vars so your development environment can operate against the service.

Use the Heroku Local command-line tool to configure, run and manage process types specified in your app’s Procfile. Heroku Local reads configuration variables from a .env file. To view all of your app’s config vars, type heroku config. Use the following command for each value that you want to add to your .env file.

$ heroku config:get FOLLOWANALYTICS_SOR_IDENTIFIER -s  >> .env
$ heroku config:get FOLLOWANALYTICS_API_KEY -s  >> .env
$ heroku config:get FOLLOWANALYTICS_API_TOKEN -s  >> .env

Credentials and other sensitive configuration values should not be committed to source-control. In Git exclude the .env file with: echo .env >> .gitignore.

For more information, see the Heroku Local article.

Using FollowAnalytics

FollowAnalytics allow you to instrument apps to obtain user analytics and perform messaging campaigns. FA holds a customer profile repository where multiple sources can push and fetch attributes.

To use the mobile app part of the product, you can login through your Heroku add admin panel. Please get in touch with support@followanalytics.com to get a mobile app provisioned on your account so that you can start instrumenting. Our Customer Success team will be delighted to accompany you along the steps to get started.

You can also access the profile repository from your Heroku app, as described below.

Using with Rails from 3.x to 5.x

Ruby on Rails applications will need to add the following entry into their Gemfile specifying the FollowAnalytics client library.

gem 'followanalytics'

Update application dependencies with bundler.

$ bundle install
# In an initializer:
Followanalytics.configure do |config|
  config.api_key = ENV['FOLLOWANALYTICS_API_KEY']
end

Using the attributes

Create a client

client = Followanalytics::Attributes::Client.new(ENV['FOLLOWANALYTICS_SOR_IDENTIFIER'])

Setting a value to a predefined attribute

client.set_first_name("Tim", "customer-00001")

Setting a value to a custom attribute

client.set_value("apple", "favorite_fruit", "customer-00001")

Unsetting an attribute value

client.unset_value("favorite_fruit", "customer-00001")

Adding a value to an attribute of type set

client.add_set_value("strawberry", "fruit_salad", "customer-00001")

Removing a value to an attribute of type set

client.remove_set_value("strawberry", "fruit_salad", "customer-00001")

Migrating between plans

Application owners should carefully manage the migration timing to ensure proper application function during the migration process.

When migrating to a new plan, your level of access to the FollowAnalytics platform might change. However, no data can be lost in the process, and you can always rollback.

Use the heroku addons:upgrade command to migrate to a new plan.

$ heroku addons:upgrade followanalytics:newplan
-----> Upgrading followanalytics:newplan to sharp-mountain-4005... done, v18 ($49/mo)
       Your plan has been updated to: followanalytics:newplan

Removing the add-on

FollowAnalytics can be removed via the CLI.

This will destroy all associated data and cannot be undone!

$ heroku addons:destroy followanalytics
-----> Removing followanalytics from sharp-mountain-4005... done, v20 (free)

Support

All FollowAnalytics support and runtime issues should be submitted via one of the Heroku Support channels. Any non-support related issues or product feedback is welcome at support@followanalytics.com.

Keep reading

  • All Add-ons

Feedback

Log in to submit feedback.

Ziggeo Gemfury

Information & Support

  • Getting Started
  • Documentation
  • Changelog
  • Compliance Center
  • Training & Education
  • Blog
  • Podcasts
  • Support Channels
  • Status

Language Reference

  • Node.js
  • Ruby
  • Java
  • PHP
  • Python
  • Go
  • Scala
  • Clojure

Other Resources

  • Careers
  • Elements
  • Products
  • Pricing

Subscribe to our monthly newsletter

Your email address:

  • RSS
    • Dev Center Articles
    • Dev Center Changelog
    • Heroku Blog
    • Heroku News Blog
    • Heroku Engineering Blog
  • Heroku Podcasts
  • Twitter
    • Dev Center Articles
    • Dev Center Changelog
    • Heroku
    • Heroku Status
  • Facebook
  • Instagram
  • Github
  • LinkedIn
  • YouTube
Heroku is acompany

 © Salesforce.com

  • heroku.com
  • Terms of Service
  • Privacy
  • Cookies