Alex_Stanton1

Hi Blake,See if this makes sense:Stream:Email 1Email 2Email 3Cast schedule - every Monday. On Sunday 1/1 you add 5 records. On Monday 1/2 they all receive Email 1On Sunday 1/6 you add 6 records. On Monday 1/7 the first group of 5 will receive Email 2, the second group of 6 you added will receive Ema...

Crystal, I would suggest you use one single campaign.Smart List:Trigger - Filled out FormFlow: 1. Send Email 12. Wait 4 days3. Send Email - Choice 1 If not opened email is [email 1 - the one you originally sent] Email: [the second one you want to send] - Default (leave emp...

Unfortunately segments are not available as tokens so your best bet is to create a custom field that can be populated with the segment through a smart campaign.

Hi Rachel,Not that I am aware of, unfortunately. That said, you could set up a form for your staff to fill out (possibly on a mobile-friendly page and without tracking code) and use that to check people in at the event. You would set up a flow action that changes their program status if that form is...

Hi Heather,I am afraid that the date toked as you refer to it is available as part of a wait step in a flow action of a triggered campaign (Use a Date Token in a Wait Flow Action) but not as a token within an asset.An email script token however might be what you are looking for. Here is how to crea...

Marketo Champion Courtney Grimes wrote a couple of excellent and detailed posts on how to use UTMs. You can find them here Get on the Right "Track" with UTM Tagging and here The Ultimate Google Analytics and Marketo Integration Guide. Those should help with point 1.

If I understand correctly, you have list A, which you uploaded as part of program A and you also want people to be part of program B. If that is the case, then, all you need to do is to make a smart campaign that will change program status on program B.The smart campaign would be like this:SMART LIS...

If you are planning on embedding on a non-marketo page, this will also come in handy: Forms 2.0 » Marketo Developers

There are different schools of thought about duplicates in Salesforce - for example this SFDC Admin Best Practices suggest to avoid them​, but I have also seen them created on purpose. While that would not be my preferred course of action, I understand you have your reasons to move ahead with duplic...

I absolutely agree with Kenny and Sanford. I would not use queues, though, since contacts cannot be added to queues and that would still create duplicates. You could assign records that are pre-MQL to a designated (non-sales?) user so that are not clogging sales but are still visible when searched i...