What is the best way to export device tokens and relevant device details of Mobile App subscribers from Legacy system to ACS for history migration purpose? | Community
Skip to main content
Level 3
August 25, 2021
Solved

What is the best way to export device tokens and relevant device details of Mobile App subscribers from Legacy system to ACS for history migration purpose?

  • August 25, 2021
  • 1 reply
  • 3060 views

What is the best way to export device tokens and relevant device details of Mobile App subscribers from Legacy system to ACS for history migration purpose to send them Push Notifications?

 

- Campaign Workflows ?

- SDKs/APIs ?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by dsmims

Hey,

 

I'd say via the SDKs would be the easiest/cleanest (& potentially best).

 

But if you can't, I have managed to do it at some point from a file import to ACS with tokens, Name of the App & Platform (ios, android) + any other data required (if you extended the appsubrcp resource).

 

In terms of loading the data, its kind of a 2 step process:

 

1. Load data to the AppSubRCP, need to do a enrichment of data linking the incoming data to existing Apps (using the value in your file & @2175539 in Mobile Applications, that way you can update the mobileApp link). I also loaded the first 10 Characters of the token to the marketingcloudID field.

 

2.At the same time, load the same data to the PushNotificationStatus resource (just token & marketing cloudID). Similar to point 1, I loaded the first 10 Characters of the token to the marketingcloudID field.


Point 2 seems to be needed, otherwise you cant' actually view or see the appsubrcp data.

 

Cheers,

Don 

1 reply

dsmimsAccepted solution
Level 2
September 9, 2021

Hey,

 

I'd say via the SDKs would be the easiest/cleanest (& potentially best).

 

But if you can't, I have managed to do it at some point from a file import to ACS with tokens, Name of the App & Platform (ios, android) + any other data required (if you extended the appsubrcp resource).

 

In terms of loading the data, its kind of a 2 step process:

 

1. Load data to the AppSubRCP, need to do a enrichment of data linking the incoming data to existing Apps (using the value in your file & @2175539 in Mobile Applications, that way you can update the mobileApp link). I also loaded the first 10 Characters of the token to the marketingcloudID field.

 

2.At the same time, load the same data to the PushNotificationStatus resource (just token & marketing cloudID). Similar to point 1, I loaded the first 10 Characters of the token to the marketingcloudID field.


Point 2 seems to be needed, otherwise you cant' actually view or see the appsubrcp data.

 

Cheers,

Don 

AKP3Author
Level 3
September 27, 2021

Thanks!