Skip to main content
10 events
when toggle format what by license comment
Jun 11, 2021 at 22:23 comment added Macca @Anna_orellfuessli I'm not aware of any particular data retention in place for profiles held by Einstein. There might be, but not 9 months. Anecdotally, I just took a look at one of my clients' account that's had recs set up for a little while and I can see purchases going back to 2018 that are there and still associated with contacts. The IGO/PI data extensions don't have any data retention policy set up, either. Email recommendations are cached for 72 hours.
Jun 11, 2021 at 9:33 comment added Anna_orellfuessli Sorry I got one more question. Do you know how long Einstein stores the data? I've heard, that it only stores data for 90 days?
Jun 9, 2021 at 9:01 comment added Anna_orellfuessli Thanks all for your relevant help!
Jun 4, 2021 at 15:35 history edited Macca CC BY-SA 4.0
added 1 character in body
Jun 4, 2021 at 15:07 comment added Macca Yes. I agree. Use cases are sparse for using raw PI/IGO DEs. Your way's the way to go for Contact Builder, @LukasLunow
Jun 4, 2021 at 14:52 history edited Macca CC BY-SA 4.0
added 3 characters in body
Jun 4, 2021 at 14:04 history edited Macca CC BY-SA 4.0
added 144 characters in body
Jun 4, 2021 at 7:16 comment added Lukas Lunow Very good explanation. I would not be too concerned about the mapping of email to email in contact builder. This assumes one would use the default data extensions directly in Journey Builder. I really can't think of a single use case where this is feasible. Instead, processing (utilising Query Activity in Automation Studio) the IGO data model into a single denormalized DE; mapped with 1:1 cardinality on Contact Key in data designer, is indeed a better way to go.
Jun 3, 2021 at 23:47 history edited Macca CC BY-SA 4.0
added 11 characters in body
Jun 3, 2021 at 23:38 history answered Macca CC BY-SA 4.0