Grégoire_Miche2

And you may also like this idea :

Hi Chloe,Just remember one thing : reading a cookie from domain A when the lead is navigating in domain B is considered as a Cross-Scripting (XSS) technique and is considered as extremely bad practices, if not illegal, in many countries even if the 2 domains belong to the same company.At some point...

Hi Kyle Rassel,There is a feature in Lead performance reports that few people know of : custom columns, that may do the trick. Here is how to use it :Create 10 smart lists, one for each of your 10 emails, using the "Opened email" filter. name them in a short and yet easy to recognize way.Go to analy...

Hi AJ,To get it though the API, you will have to export activity logs and sort them out. It's not an easy task, as there is nothing such as a "became member of a campaign" activity log.I had the same idea, but from the UI perspective, a couple of days ago : -Greg

Hi again Jason,Account Num is a SFDC standard field that gets synchronized by default.-Greg

Hi Nate,Ask support, but I would be surprised if this is possible.Surprising there is no long text field available.-Greg

Hi Mindy Westerman,Have you tried to use the Engagement Stream performance type of report ?-Greg

Hi again,That's normal. It means they are new leads that have been acquired by the program. Which is why they need to be created in SFDC.-Greg

Hi Annaliese,Apparently; the lead source field has been made mandatory on SFDC side.Create a smart campaign :2 filters :member of program = True, program = [your program]Lead source is emptyFlow steps :Change data value : lead source = Your new valueSync lead to SFDCRun it once.-Greg