NewPropertyBehaviour

New Property Behaviour

When you create new property you will have to chose from

• a Website Property
• a Mobile app Property

A Mobile app Property will only work with the Firebase SDK.
See: Measurement options for mobile apps

Use the Measurement Protocol

The Google Analytics Measurement Protocol is a standard set of rules for collecting and sending hits from any Internet-connected device to Analytics. It's particularly useful when you want to send data to Analytics from a kiosk, a point of sale system, or anything that is not a website or mobile app. Because, while the Analytics JavaScript and mobile SDKs automatically build hits to send data to Analytics from websites and mobile apps, you must manually build data collection hits for other kinds of devices. The Measurement Protocol defines how to construct the hits and how to send them to Analytics.

Whether you want to track

• from a SWF file running in the Flash Player plugin
  either online or offline
• from a SWF file running in the Standalone Flash Player
• from an Adobe AIR GUI application
  either mobile or desktop
• from a Redtamarin CLI program
  either shell script, .as/.abc/.swf program or executable (projector)
  either as local command-line app or server-side app

Just use a Website Property.

Use the library to send any kind of Hit types ('pageview', 'screenview', 'event', 'transaction', 'item', 'social', 'exception', 'timing') to the property, you will find all the data in the reports view.

see this old google+ post: Understanding User Behavior in a Multi-Device World

Analyze app and web data in the same reporting view

Any data you send to the same property appears in all of the reporting views, regardless of how you collected that data. This means that if you send data from the web or from a mobile app to one property, both data sets appear in your reports.

If you want to isolate data from one source, like if you only want to see web data in your reports, you can set up a filter to customize what you see. You can also use other tools to isolate each data set, including customizations in standard reports, dashboards, custom reports, and secondary dimensions.

Simply put, the library allow you to send any kind of Hit types but you have to decide what is best for your app and/or your tracking requirement.

Few scenarios:

• an Adobe AIR desktop app that work like "browsing pages"
  a PDF viewer, a browser, etc.
  then send pageview hits

• a local SWF in HTML that works like an "application with states"
  an animation, a multi-choice quiz, etc.
  then send screenview hits

• a server-side script that work like a "web page"
  for ex a form submission
  then send pageview hits

• a Redtamarin projector that works like a "command-line tool"
  for each command options, for example -h for help
  then send screenview hits

You could as well not send any pageview nor screenview hits, or send both, and/or decide to send event hits, etc.