Andy_Varshneya1

Hi Britt,The way you would want to approach this is by considering what type of details you're referencing multiple times, and then thinking about if that content is being used repetitively only in the program or in multiple programs. For example, details like the name of an event will be used in th...

Hi Tom,It all depends on what content you have in your confirmation email. If the email does not depend on other triggers running as well, you can send it right away. However, if you have additional trigger campaigns that need to run first (i.e. Lead is created, then synced to SFDC and assigned to a...

Hi Sarah,No you can't do that with smart campaigns because those can only modify the entire field, not just a part of it.You'll want to check out external tools that are available such as Informatica​ or any other data enrichment service.

Ashley Ayan​, what you'll have to do is setup a smart list for each possible combination of which there are 10, and then have one more smart list checking to see if the lead is a member of any of those smart lists, and finally a trigger or batch campaign that executes the specific action you're tryi...

Yup, and unfortunately thats a scenario you can't prepare for without building a very complex solution for something that'll rarely happen, so I think we're both on the same page about the effort vs reward.

I would actually avoid using custom fields because it can clog up your system very easily over time. Instead, go the Smart List route, paired with a trigger or batch campaign checking to see if someone is added to that list.Use the Clicked Link in Email filter, set the Email criteria to be the 7 ema...

Hi Prabash,I built this system out for our instance, but instead of using URL parameters, I worked off of cookies so that we could credit a medium even if a lead landed on a page but then went to another and downloaded the asset there. It's a corner case, but made our lead tracking absolutely bullet...

Hi Laura,As a few people have mentioned already (and you seem to have figured this out), this is fairly common because of a few issues - the "winning" field data is not in the correct format as the field type, or the merge is across SFDC objects.You would be best off using a tool like RingLead or my...

And it will have issues scaling too should your instance change drastically.

Right, that's what I had assumed, just wanted to know if there was a way to not remove the leads from the database retroactively.Thanks for all the help.