Timeline for Automate looking up data based on subscriberkey and populating a data extension with extended info
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 14, 2020 at 9:28 | comment | added | Swati Mishra | Can you just not set the journey re entry settings 'Re entry only after exiting'. This will ensure that they do not renter again :) | |
| May 14, 2020 at 8:46 | comment | added | Felix Sanchez | Yes, that would be a way. But, If the subscriber has always been added to the Journey, I'd not let them be a part of the Journey DE before having exited it. So, I'd delete individual records in the Journey DE with a retention policy that matches the length of the journey. When moving them from Room DE to Journey DE, I'd only move them if they're not a part of the Journey DE already. This is why I want to be able to empty the DE after having moved the subscribers. Hope it makes sense | |
| May 14, 2020 at 7:38 | comment | added | Swati Mishra | You need not empty it, if you have data action as 'Update' on the query activity'. The primary key could be subscriber key and room type. Each time, it will see if there is already a record with that subscriber key and room type, it won't add the record again. If there is no such record, it will add it. Makes Sense? | |
| May 13, 2020 at 20:08 | vote | accept | Felix Sanchez | ||
| May 13, 2020 at 20:07 | comment | added | Felix Sanchez | This really makes sense. But how would I empty the Room DE after having moved those subscribers to the Entrydefinal1 DE? If not emptying it, I'd add the same subscribers to the Entrydefinal1 DE over and over again, right? | |
| May 13, 2020 at 10:57 | history | answered | Swati Mishra | CC BY-SA 4.0 |