0

Is it recommended and viable that the mobile app uses the standard marketing cloud Create Contact API instead of using the contact registration of mobile push sdk for Android and IOS?

1

For push, it is not recommended that you register devices/contacts outside of the provided SDKs.

|improve this answer|||||
  • @[Bill Mote] would you mind to expand a little bit your feedback and explain the reason why is not recommended? Additionally now the question is become for the entire mobile push sdk: if it's viable and recommended to replace it entirely (not only for contact registration) with Marketing Cloud APIs . – Emanuela Giraudo Jan 23 at 1:25
  • 1
    As of 20200123 the Contact/Device registration routes, analytics routes as well as the device and message routes are not publicly documented routes and can change without notice. What is the reason for avoiding the SDKs? We have a BILLION registered devices across a lot of customers. – Bill Mote Jan 23 at 14:44
  • As per my understanding it's seems that the company in charge of the mobile app development saves effort using the API instead of the SDK and do not fully support the integration of that kind of SDK. What do you mean by "routes are not publicly documented routes and can change without notice"? Do you mean that is a different set of API, not the ones documented here? – Emanuela Giraudo Jan 24 at 15:14
  • That is correct. – Bill Mote Jan 24 at 18:18

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.