comScore

comScore is a self-service portal that helps you tag all your digital assets and ensure the right exposure of your online content like web pages, videos, mobile apps, ad networks, and more.

Getting started

RudderStack supports sending events to comScore only in mobile device mode.

Once you have confirmed that the source platform supports sending events to comScore, follow these steps:

1. In your RudderStack dashboard, go to Directory > Destinations > Cloud Destinations and search for Comscore.
2. Connect your source and click Continue.

Connection settings

Configure the following settings to set up comScore as a destination in RudderStack:

• Publisher ID: Enter the client ID/C2 value associated with your mobile app. See FAQ for more information on obtaining this value.
• App Name: Enter your source app name. RudderStack includes this parameter in the events to specify the source app for getting the tags and data.
• Only auto update when app is in foreground: This setting is turned on by default and updates your app usage data only when the application runs in the foreground.
• Auto update when app is in foreground and background: Turn on this setting to update your app usage data when the application is running in the foreground and background.

Note that if turned on, this setting will override the Only auto update when app is in foreground setting.

• Auto Update Interval: Use this setting to specify the time interval between the updates.

Note that:

• This setting is applicable only if the auto updates are turned on.
• The default value of this field is 60 seconds.

• Client-side Event Filtering: This setting lets you specify which events should be blocked or allowed to flow through to comScore. See Client-side Event Filtering for more information.
• OneTrust Cookie Categories: This setting lets you associate the OneTrust cookie consent groups to comScore.
• iOS/Android SDK Settings: As this is a device mode-only integration, the Use device mode to send events setting is toggled on by default.

Adding device mode integration

Once you add comScore as a destination in the RudderStack dashboard, follow these steps to add the native mobile SDK to your project depending on your integration platform:

implementation 'com.rudderstack.android.sdk:core:[1.17.0, 2.0.0)'
implementation 'com.rudderstack.android.integration:comscore:[1.1.0,)'

// It enables Comscore to collect a privacy-friendly publisher-specific device identifier, App Set ID, for estimating the number of unique users for audience research purposes.
implementation 'com.google.android.gms:play-services-appset:16.+'

val rudderClient = RudderClient.getInstance(
            this,
            WRITE_KEY,
            RudderConfig.Builder()
                .withDataPlaneUrl(DATA_PLANE_URL)
                .withFactories(ComscoreIntegrationFactory.FACTORY)
                .build()
        )

pod 'Rudder-Comscore'

#import "RudderComscoreFactory.h"

RSConfigBuilder *builder = [[RSConfigBuilder alloc] init];
[builder withDataPlaneUrl:DATA_PLANE_URL];
[configBuilder withFactory:[RudderComscoreFactory instance]];
[RSClient getInstance:WRITE_KEY config:[builder build]];

Identify

You can use the identify call to set the user ID and traits as persistent labels in comScore.

RudderStack maps the identify events to comScore’s addPersistentLabels API, followed by making a call to comScore’s notifyHiddenEvent API.

A sample identify call is shown:

RudderClient.getInstance()?.identify(
            "1hKOmRA4GRlm",
            RudderTraits()
                .putEmail("alex@example.com")
                .put("trait_key_1", "trait_value_1")
                .put("trait_key_2", 4567),
            null
        )

Track

You can use the track call to record user actions. RudderStack also sends any associated properties as labels to comScore.

RudderStack maps the track events to comScore’s notifyHiddenEvent API.

A sample track call is shown:

RudderClient.getInstance()?.track(
            "Event name",
            RudderProperty()
                .putValue("property_track_key_1", "property_value_1")
                .putValue("property_track_key_2", 987654)
                .putValue("prop3", "value3")
        )

Screen

You can use the screen call to record whenever a user views their mobile screen and capture any properties about the viewed screen.

RudderStack maps the screen events to comScore’s notifyViewEvent API.

A sample screen call is shown:

RudderClient.getInstance()?.screen(
            "Screen event name",
            RudderProperty()
                .putValue("property_screen_key_1", "property_value_2")
                .putValue("property_screen_key_2", 9876542)
        )

For both track and screen events, RudderStack maps the event name with comScore’s name field. It sends all the other properties to comScore as is, without any modifications.

Reset

Use the reset call to reset userId and the associated traits.

A sample reset call is shown:

RudderClient.getInstance()?.reset(true)

FAQ

Where can I find the comScore Publisher ID?

1. Log in to your comScore Direct account.
2. Go to the Mobile app tab.
3. Click Get Tag and copy the C2 value.

Questions? Contact us by email or on Slack