Overview

The comScore Application Tag provides complete usage reporting about an application's lifecycle. For applications on mobile devices this includes usage reporting even when the device does not have any available data connection.

How to Implement

Step 1. Add the Tag

This Tag is available in Tealium's Tag Marketplace. Refer to the Tags Tab article to learn how to add a Tag to your Tealium iQ profile.

ComScore_Mobile_1.png

Step 2. Enter Vendor Configuration

  1. Title: Enter a unique name to identify the Tag. This is important if you are adding multiple instances of this Tag.
  2. Client ID (required): The Client ID is also known as the C2 value. This is a number of at least 7 digits, provided by comScore.
  3. Publisher Secret Key (required): The Publisher Secret Key is used to create the ADID. The ADID is an anonymous unique value that is generated by the Application Tag library and is persistent only between applications of the same publisher.
    • It is the same for all of your applications, but unique to you.
    • This is required for security, and to protect the privacy of your application's users.
  4. Enable Auto Update:  The Application Tag library contains an auto-update feature that will update the application usage times on regular intervals. The default configuration is True. If you want to disable this feature, you will need to select false in the tag configuration settings.
  5. Keep Alive Event: The Keep Alive Enabled parameter determines if the Application Tag library will transmit a keep-alive event once every 24 hours if – during that period – the application was active and no other events were transmitted.

    • The default configuration setting value is false. If you want to enable this event, you will need to select true in the tag configuration settings.

Step 3. Apply Load Rules

Load Rules determine when and where to load an instance of this Tag on your site. The 'Load on All Pages' rule is the default Load Rule. To load this Tag on a specific page, create relevant Rule conditions to apply to the Tag.

Best Practice: [insert text].

Step 4. Add Data Mappings

Mapping is the simple process of sending data from a variable, in your Data Layer, to the matching destination variable of the vendor Tag. The destination variables for this Tag are available in the Data Mapping toolbox and are grouped in different categories for ease of use.

For instructions on how to map a Variable to a Tag destination, see Mapping Variables.

[Category #1]

Destination Name Description
view_name (required) Page Names: Map the TrackWithViewEvent variable (screen_title) to view_name to track page names 
appName (required) AppName: The reported application name. The Tealium auto generated variable, app_name is available to map to this parameter.

appVersion (required)

AppVersion: The reported application version. The Tealium auto generated variable, app_version, is available to map to this parameter.

plat.os_version  OS Version: Map device_os_version to plat.os_version
plat.connection_type

Connection Type: Map connection_type to plat.connection_type

plat.name Platform Name: Map platform to plat.name
plat.app_rdns

RDNS: Map app_rdns to plat.app_rdns

plat.deviceName Device Name: Map device to plat.deviceName

comScore-Mobile-1.png

[Category #2]

Destination Name Description
plat.dev_language

Device Language: Map device_language to plat.dev_language

plat.dev_resolution

Device Resolution: Map device_resolution to plat.dev_resolution

labels.gl_uid

VisitorID: Map uuid or visitor_id to plat.VisitorId

labels.gl_guid

Labels: Map labels to labels to labels.XXXX

 

More about Labels

 

The Application Tag allows you to specify (custom) labels. You can either specify persistent labels or event-specific labels.


Persistent labels will be included in every measurement that is sent by the Application Tag library. They will contain their last known value. You could consider these labels to be application-wide.

Please note the following when you enable the auto-update feature and allow it to be active while the application is in the background:

Event-specific labels will be included to the measurement that is sent for the tagged event. These should be used for collecting information which only applies to a single event.

labels.ns_category [insert description here]
view_name [insert description here]
send_event:hidden  Hidden

 

  • Map link_id to the event trigger send_event: hidden

 

Any application event or user action that does not categorize as a View event can be reported as a Hidden event. Like View events, Hidden events also have a page name that is used in reporting to identify the application view or screen where the application event or user action took place.

Examples of cases where the application event can or will be used:

  • A user taps or clicks on a button, for example, to enable a feature in the application.
  • The application performs a certain (internal) activity, like sending data from a filled in feedback form.
view:view

View

 

  • Map call_type to the event trigger view:view to dispatch events with appropriate labels

 

You may report a View event whenever the application screen changes. This screen impression or screen view is the equivalent of the page impression or page view used in web analytics.

 

The View event is intended to be used in the following cases:

 

  • When the application changes the current screen.

 

  • When the contents of the current screen are changed significantly even though the application does not change the current application screen.

 

  • When the application transitions to foreground.

comScore-Mobile-2.png

[E-Commerce]

[Map to these destinations for sending ecommerce–specific Data Layer variables. We typically recommend using Tealium's E-Commerce Extension for this purpose. Why? When it is properly configured, the Extension automatically maps your variables to the appropriate destinations for all E-Commerce enabled Tags in your profile. That way you don't have to map those variables over and over for every one of your Tag. If you, however, decide to override any Extension variable, or otherwise your variables are not available to the Extension, you must manually map a variable to its destination using the toolbox.]

Destination Name Description E-Commerce Extension (RECOMMENDED)
[Order ID] [Unique identifer assigned to the final order] ["_corder" maps to this destination]
[Sub Total] [Sub total amount of the final order] ["_csubtotal" maps to this destination]
[List of Product IDs] [Unique identifier of each product in the product array] ["_cprod" array maps to this destination]
[List of Product Names] [Name of each product in the product array] ["_cprodname" array maps to this destination]
[Shipping] [Cost of shipping the product] [NA]
[tax] [Tax applied to the final order] [NA]

[Events]

Map to these destinations for triggering specific events on a page.[insert description as needed.]

Here's how to map an event:

  1. Select an event from the dropdown list. You may choose from the pre-defined list or create a 'Custom' event.
    For 'Custom' event, enter a name with which to identify it.
  2. In the 'Trigger' field, enter the value of the variable you are mapping to this destination. When the value is found, the event will trigger on the page.
  3. To map more events, click the + button and repeat steps #1 and #2.
  4. Click 'Apply'.

[insert screenshot]

Step 5. Save and Publish

That's it! You have successfully set up the Tag in your profile.

Vendor Documentation

Attachments
Version history
Revision #:
17 of 17
Last update:
‎10-13-2016 12:10 PM
Updated by: