Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
There's been previous conversations about how "before" date filters include blank values, and whether or not that is ideal behavior. I think the best solution to this would actually be to add another constraint to date/datetime fields called "include blanks: true/false." That way you could make dete...
It would be nice when filtering email activity history and email triggers (e.g. "was delivered email," "opens email") to have a filter for whether or not the email was operational. Obviously this wouldn't be that important if you are filtering the activity for one specific email, but if you wanted, ...
Am I correct in assuming that (at this point at least) this can be controlled in the "Communication Limits" section in Admin by changing the "Default behavior if a person is over communication limits" option? See screenshot below.
I think this is related to this idea from 2014 (a shame that these ideas have been around for a decade!) I would upvote the other one if you haven't yet 😁
This is like a slightly more defined version of this idea from 2014 - could probably be merged! Definitely upvote that one if you haven't already 😁
It's been a few years, but I did this exact thing using Zapier. In my case I was maintaining subscription preferences across multiple records. I had a smart campaign set up so that when someone filled out our preference form, if they were a possible duplicate, it would trigger a webhook into Zapier ...
@Zoe_Forman I do set expiration dates for contractors, but employees also expire and have to be renewed due to our security policies. Granting 200 users access to the system forever isn't a thing when you work at a cybersecurity company haha.
@Zoe_Forman yes, I'm referring to the function in People view called "Last Cast." It's not really feasible to use the method you describe (cross-checking members and program reports) because I'd have to do that for every email in every stream to get a clear picture. Though now I'm thinking maybe I c...
No, I am using Update User Attribute. I'm updating system users, not person records, which is why I don't have the ID - it's directly in the URL. It is a datetime according to the documentation: expiresAt (string) - Date and time when user login expires. Example: yyyy-MM-dd'T'HH:mm:ss.SSS't'Z
An hour-by-hour chart that showed the volume of records processed through the campaign queue would be a fantastic complement to this. Think similar to "membership by week" in smart campaigns but hourly for the past 48 hours.