Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
Any ideas on how to handle blocking a field update from a particular vendor vs all API integrations? We have a vendor for which we don't trust their data for job title, if we already have a job title. Is it possible to just block this field for this particular vendor
I am trying to run a report to check where phone = Mobile.I tried (Mobile Phone Number IS {{lead.Phone Number}}ORPhone IS {{lead.Mobile Phone Number}})AND Phone IS NOT EMPTYThis results in no leads, but I know is a fact there are many leads that exist this way in our database. Any suggestions?
@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...
We are creating a new Lead Scoring Program, but we would like to accommodate for changes in jobs by wiping out the score value for the previous job title, and assigning the score value for the new job title category. there are only 4 categories for which we are referring to here. i tried adding a...
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.
We are trying to send an alert to multiple people, including a string token populated with an email and an alias email in the "Send Alert" flowstep. I was wondering if there are any limitations? Our alerts are not working and I suspect it is because the token is of type "String". One of the token...