Nancy_Rosentha4

Thanks Stanford. Yes, I totally agree, our unsubscribe should not be creating a new lead. this has to be addressed, but in the meantime, i have implemented a solution just as you had suggested.

Marketo support is saying this is an anonymous lead, since it has no email, name or company. They say that api pushes can created anonymous leads. I always thought it was only from traversing the website, tracking this info and prior to filling out a form, without being known, these are considered...

You can also submit a support ticket and Marketo will create such a list of fields with the following: Attribute IDAttribute NameAttribute Display NameField TypeData TypelengthObject IdObject NameAttribute Map IDAttribute Map NameAPI NameAttribute Map Display Name Hope this helps. I know it helped...

This is a Trigger Smart Campaign, with several triggers, as well as many filters in the Smart list to filter which leads would proceed through to the Flow. Then, in the Flow, just one flow step, Request a Campaign, with a few choices to dictate which campaign to request. I would like to filter ou...

@Steven_Vanderb3 I don't exactly understand what you are saying the correction would be here. Do we configure this differently from our end or from the BrightTalk side of the house, and if us, how/where do we configure to stop calling the "endpoint"? Any help is greatly appreciated.

This is exactly what I ended up doing. In reality, it was a total of about a dozen additional tokens with negative values, but easy enough to set these up and use these. It just would have been convenient to negate an existing token to enable wiping out an existing specific demographic score, such...

turns out the alias that was created was not created with the ability to send from an external source... note to self, validate others work. Thanks for your insight.