Hey Michael.There are lots of different opinions on this question.Before establishing our connection with our Paid environments, we did significant amounts of testing on match rates between our platforms.Once we had a good idea of what to expect when porting audiences over, we ran our queries to che...

But yes, using a customer audience, I think you should be able to use opens

We trigger off of sends, not opens, but you should be able to do the same. 

We have implemented a use case similar to this. You can make an audience for that specific action, and then have a different journey using a read audience that triggers daily. 

Yeah unfortunately you cannot  Easiest workaround is to only select the columns that you need and then create a subquery, then regenerate your new column with your new data!

Hey! We've had a lot of success for the functionality you're describing by making new versions! It keeps the continutity for the OOTB IDs. You can additionally combine this with a 'Close to new entrants' on the previous itteration and it should be able to solve for those issues you're describing

Hey - in case you're not using it already, you should be setting dataLabels on all URLs. You can either hard code this into the HTML, or in the email designer, you can click the links icon on the left hand pane, in which you can set tracking labels for every URL or external link in your email. These...

This is almost exactly what I ended up doing. I just set the timestamp date as a dateTime field for right now and added my 'correct' timestamp field to another empty field I had on the dataset and just mapped that to timestamp for my external integration. Glad we had the same thought Vinod!  Thanks ...

Hey all! Running into an issue I'm wondering if anyone else has faced before. We're working on a new integration that we need to export 2 years of historical transaction data to support. The first year was super easy, we have it in a profile enabled dataset, so we were able to export that to our S3 ...

Hey Michael. Ran into this same issue and unfortunately, uncompressed JSON is not supported. You can see some additional guardrails here - Default guardrails for data activation | Adobe Experience Platform