Hi Sanford, I'm very interested in two of the answers: Are we able to append fields to existing forms using the update endpointYou add with the /fields.json endpoint.Say we have a ...
Ok, so after every update / creation, first smart list qualification is determined / fixed and then all other search processes take place. When it comes to smart list memberships, ...
I see what you mean. As long as the source form includes the filters that you are using on the filter smart list, the trigger will fire correctly, because the necessary information...
Thanks for your suggestion. Yes, working within the flow steps seems like a 100% reliable method. I will definitely bear that in mind in general. I am inclined to agree with Sanfor...
Here is another suggestion... Never use "person created" as a trigger in your instance's smart campaigns. Always use instead "added to list: "Person created" ". Create the list "Pe...
Ok, so my takeaway from your answer is that its unreliable, same as Ronan, you are saying that if the data is already there when the trigger happens - it's relaible.Otherwise, you ...
Hi Ronen, Thanks for you answer!So you suggest I break that into two campaigns that happen in sequence. But doing that implicates duplicating the numbers of campaigns... perhaps in...
Hi, This is almost a philosophical question on the origin of things...I have a Smart Campaign that looks something like this: Smart listTrigger: Person is createdFilter: Country is...
The way google suggests you implement this, it only asks for you to create one GCLID field in SFDC, so i'm not sure the intended use of this is multi-touch attribution, but rather ...
Sorry, but I don't understand why two fields are necessary for this. Perhaps because I don't have a technical background. Shouldn't it be enough to grab the information from the co...