I'm attempting to query our mobile push demographics table that's tied to the contact record to pull some Application Version data and I'm struggling in Query Studio.
The name of the table is MobilePush Demographics.
I've attempted FROM:
[MobilePush Demographics], __[MobilePush Demographics], ent.[MobilePush Demographics], ent._[MobilePush Demographics]
MobilePush Demographics holds information sent to the Marketing Cloud by your application. You can also import contacts into MobilePush and you will see the data for the contacts in the table. It is also the table where you will add any custom attributes you wish to pass to the Marketing Cloud.
The SubscriberID on the table is an auto-populated field which populates when a contact record is created; it is not the same thing as ContactKey/SubscriberKey. The ContactKey (SubscriberKey) is a root table value and is not part of MobilePush Demographics since MobilePush Demographics relates back to the root table on ContactID.
When a new contact record is created by your application sending a registration call to the Marketing Cloud it is create on the root table and on MobilePush Demographics.
Here is information for setting the SubscriberKey for iOS: http://salesforce-marketingcloud.github.io/JB4A-SDK-iOS/features/subscriber-key.html
Here is information for setting the SubscriberKey for Android: http://salesforce-marketingcloud.github.io/JB4A-SDK-Android/features/subscriber-key.html
Have you tried linking the DEs? Consider going to Data Extension in Contact Builder and then linking in JB. Contact Key and SubscriberKey should be equivalent. Here are a couple of sample screenshots.
Best Answer
The proper name for the Mobile PushDemographics data view is
_PushAddress.There's an answer made by @Daniel that lists all default fields and their datatype here, but be aware that you your data extension field names can't begin with an underscore, so when you query this data view, you need to rename them using an alias, for example:
If you have any custom attributes added to MobilePush Demographics, their names in this data view will not be proceeded by an underscore, so using an alias won't be needed.