Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
Hi Everyone,Normally, we report our event programs (almost always Webinars) at a high level, but I got a request for YTD Event Program Engagement (Webinar Registrations, Attendees, etc.) for a specific audience segment. Besides pulled the numbers for each individual event program, is there a way to ...
To elaborate on Sanford's idea (which is an very creative solution), you're going to write a velocity token that is essentially:##HIDE SECTION FOR SEGMENTS#if (${lead.NAME_OF_SEGMENT_Segment__c} == "Value1" || ${lead.NAME_OF_SEGMENT_Segment__c} == "Value2")
I believe the Reply-To name is dictated by the person's address book, not dictated by Marketo which is why you can dictate in incoming name, but not an outgoing name (only to which address it should be going).
This is an awesome idea. I'm going to talk to my devs to see if I can get something like this rolling. Thank you for the idea!
I'm not sure, since that filter would exclude anyone who downloaded a non-focus file in the last 90-days, even if the trigger event itself was valid.
Hi Everyone,We use the "Clicks Link on Web Page" trigger for some lead scoring when users download PDFs off the website (Clicks Link on Web Page --> Link Name [Contains] .pdf, screenshot below)My question is, I want to use the same trigger, but EXCLUDE certain documents from the trigger. I.e., Link ...
You could go with something using "First Touch" since basically you're trying to attribute the first touched BU. Customer Source BU is another option.
The unfortunate news is... you can't clear it. As you input new emails in the send to text area, it will overwrite those older addresses, but there's not a way to remove them from the list (at least not from what I've found across the documentation and community)!Sorry
Yea, I didn't think that would be the sources of the problem as I had already encountered THAT issue and had the permissions updated! Those permission changes were accidentally overwritten, causing the issue to occur again. Luckily this time around I had stopped the field updates from SFDC Sync so ...
Hi Everyone,After some investigation, turns out the Marketo Integration User Permissions had been mistakenly overwritten to be read-only for the field. Lucky for me, I already had block field updates from SFDC Sync enabled for the field inside Marketo, so Marketo's data is still clean. We updated th...