Timeline for How to convert Mobile Push List into Data Extension
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 3, 2019 at 17:07 | comment | added | EazyE | two things One you can use a list as an entry source using the audience list: help.salesforce.com/… Two I don't understand the use case where you need the attributes in the entry source DE | |
| Dec 3, 2019 at 16:59 | comment | added | Naveen VM | So the use is that, we dont have any contact's now. Let's say if you have downloaded an app then you will come into Mobile Opt-in. Then I will try to send a push notifications via Journey. To send a push via journey i need a data extension as source. That is the reason I was asking if there is any way that we can convert all the attributes of list into data extension? | |
| Dec 3, 2019 at 16:54 | comment | added | EazyE | I still don’t see what your use case to have all the attributes in the de | |
| Dec 3, 2019 at 16:49 | comment | added | Naveen VM | Hey @EazyE thanks so much for your response. Is there any way that I can get alI the data from list to data extension? just needed it to be in data extension because I can select the source as data extension in Journey. If keep it in the List then I can't use it in Journey. | |
| Dec 3, 2019 at 16:32 | comment | added | EazyE | You can access any of the attributes in the journey even if they aren’t in the DE since they are part of the contact model | |
| Dec 3, 2019 at 15:53 | comment | added | Naveen VM | Thanks @EazyE for your help! It's weird that other attributes are not accessible. How we can move from Mobile List to Data extension and capture all attributes in data extension to be used in journey? | |
| Dec 3, 2019 at 15:52 | vote | accept | Naveen VM | ||
| Dec 3, 2019 at 15:32 | comment | added | Gortonington | Too quick for me. Great job @EazyE | |
| Dec 3, 2019 at 15:31 | history | answered | EazyE | CC BY-SA 4.0 |