Today, we will explore how to run special campaigns to improve your instance. These are fun tips to ensure your instance is full of surprises and runs super smoothly. Experts only!
The CEO Message
Ever want to throw a party and get the CEO to pay for it? Here’s your chance. Even AB test it to see which party choice wins!
- Smart List: Employee Seed List
- Flow: Send Email
- Email From Address: CEO@yourcompany.com
- Schedule: Once every 90 days, every time.
- Smart List: Customers
- Send Email: “We are closing immediately and deleting your data.”
- Delete Lead, in SFDC = TRUE
- Schedule: Once in 30 days from today
- Bury in five folders.
- Smart List: All leads
- Email Address = NULL
- Company Name= NULL
- Customer Status=FALSE
- Email Invalid=TRUE
- Schedule: 30 days from today
- Bury in five folders.
The Land Mine
Create a trigger (or a batch) flow to find leads and then delete or modify key fields. With list size being the primary driver of costs, it’s a good way to keep your costs down.
Name: Random Sample Routing Tool – Test
- Smart List: Data Value Changes IS ANY or Lead is Created
- Random Sample = 25 > Add to List 1, 2, 3, 4
- If Member of List 1, Delete Lead
- If Member of List 2, Phone Number = NULL
- If Member of List 3, Email Address = email@example.com (or your CEO!)
- If Member of List 4, Unsubscribed=T
- Schedule – every time.
Alternatively, you can use this flow to re-assign leads to other users. Think of the days of fun your colleagues will have tracking this down.
Be mysterious – be sure they delete your user immediately after you leave so the campaigns are missing names.
The Missing Role
Remove Roles from all Marketo Users late at night. Wait for the frantic calls. They didn’t all need access, did they?
The Missing Record Type ID
- Smart List: Record Type ID IS NOT EMPTY
- Flow: Change Data Value: Record Type ID = NULL or whatever.
- Schedule: daily, starting 65 days from now.
Take bets on how many days it will take to figure out why the sync broke. My personal record is 6 days.
- First, it shows you how easily you can damage the database.
- Second, it is good troubleshooting.
- Third, if you think an employee is disgruntled or is leaving under bad circumstances, then be sure to NOT remove their user yet and check things they owned. And practice good security by removing access asap, I’ve seen a lot of systems with active users who are no longer contractors or employees. Very dangerous.