---
schema_version: "1"
id: 647f9739a621d0617f520cb3de43657d50682de666a6648230e8816df441b13b
title: Create a Calculated Insight to Select the MobilePush SubscriberKey
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_omni_ci.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_omni_ci.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: faeeb7011aaadecc23423263444f09715424cf0c5d4ec982db8fed3786f8128d
description: Data 360 has numerous controls to select and activate a channel contact point. However, for some scenarios, you must create a Calculated Insight to filter or select a specific channel contact point. For example, Data 360 doesn’t support activating the Email, SMS, and MobilePush channels together.
products:
  - Data 360
release: "264"
---
# Create a Calculated Insight to Select the MobilePush SubscriberKey

Data 360 has numerous controls to select and activate a channel contact point. However, for some scenarios, you must create a Calculated Insight to filter or select a specific channel contact point. For example, Data 360 doesn’t support activating the Email, SMS, and MobilePush channels together.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/images/icon_note.png)

Note If your Omni-Channel journey includes Email and SMS but not MobilePush, you can skip this step.

The Calculated Insight output includes the attribute MobilePush Key, which you can add as a direct attribute when you activate the Unified Individual. This action ensures that the activated data extension in Marketing Cloud Engagement has the contact point values for the Email, SMS, and MobilePush channels. Journey Builder can use these contact points to orchestrate Omni-Channel journeys.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/images/icon_note.png)

Note Marketing Cloud Engagement requires a [SubscriberKey to execute MobilePush sends](https://help.salesforce.com/s/articleView?id=mktg.mc_mp_who_receives_your_message.htm&type=5&language=en_US).

Using this SQL, Cumulus creates a Calculated Insight that searches all of a Unified Individual’s MobilePush SubscriberKeys and selects the SubscriberKey with the most recent app engagement.

`select rk.ssot__Id__c as UnifiedIndividual_Id__c,rk.ssot__PartyId__c as MobilePush_SubscriberKey__c,count(*) as NUMRECORDS FROM ( select UnifiedIndividual__dlm.ssot__Id__c as ssot__Id__c ,ssot__ContactPointApp__dlm.ssot__PartyId__c as ssot__PartyId__c, rank() over (PARTITION by ssot__ContactPointApp__dlm.ssot__PartyId__c order by ssot__DeviceApplicationEngagement__dlm.ssot__EngagementDateTm__c desc) as rank__c FROM UnifiedIndividual__dlm INNER JOIN IndividualIdentityLink__dlm ON UnifiedIndividual__dlm.ssot__Id__c = IndividualIdentityLink__dlm.UnifiedRecordId__c LEFT JOIN ssot__ContactPointApp__dlm ON ssot__ContactPointApp__dlm.ssot__PartyId__c = IndividualIdentityLink__dlm.SourceRecordId__c LEFT JOIN ssot__DeviceApplicationEngagement__dlm ON ssot__DeviceApplicationEngagement__dlm.ssot__IndividualId__c = IndividualIdentityLink__dlm.SourceRecordId__c WHERE IndividualIdentityLink__dlm.ssot__DataSourceId__c = 'YOUR_SFDATASOURCE' ) rk where rk.rank__c = 1 group by rk.ssot__Id__c, rk.ssot__PartyId__c`