Hi Susan,

Getting the Custom APEX Trigger to save is certainly not as easy as they make it seem in the documentation, is it? I had to fight with this quite a bit too.

One thing that is not mentioned in the documentation is that you have to create Custom APEX Class that is a test class to test your trigger code in addition to the trigger code itself.

Here is a copy of the test class I used when I created my lead trigger:

/**
 * This class contains unit tests for validating the behavior of Apex classes
 * and triggers.
 *
 * Unit tests are class methods that verify whether a particular piece
 * of code is working properly. Unit test methods take no arguments,
 * commit no data to the database, and are flagged with the testMethod
 * keyword in the method definition.
 *
 * All test methods in an organization are executed whenever Apex code is deployed
 * to a production organization to confirm correctness, ensure code
 * coverage, and prevent regressions. All Apex classes are
 * required to have at least 75% code coverage in order to be deployed
 * to a production organization. In addition, all triggers must have some code coverage.
 * 
 * The @isTest class annotation indicates this class only contains test
 * methods. Classes defined with the @isTest annotation do not count against
 * the organization size limit for all Apex scripts.
 *
 * See the Apex Language Reference for more information about Testing and Code Coverage.
 */
@isTest
private class Trig_LeadTest {

    static testMethod void myUnitTest() {
        // TO DO: implement unit test
        Lead testLead = new Lead(LastName = 'Test Lead', Email = 'help@fanmailmarketing.com');
        insert testLead;
        testLead = [select Id, LastName from Lead where id = :testLead.Id];
        System.assertEquals(testLead.LastName, 'Test Lead');
    }
}

As for your trigger code itself, I would suggest simplifying it so that it just applies to all Leads and then just set the criteria for the triggered send when you create the triggered send. Here is my trigger code.

trigger Trig_Lead on Lead (after insert, after update) {
	et4ae5.triggerUtility.automate('Lead');
}

So, save the test class first, then the trigger. If you are deploying via the Force.com IDE then you can deploy them as part of the same package.

Once they are deployed you can go to the Marketing Cloud tab and then to the "Configure..." link and you will see the "Triggered Sends" option. You will create your whole triggered send definition from here, including selecting the email and delivery profile and setting the conditions for when to send an email. So this is where you would set the criteria for Type = Consumer.

Once you activate your triggered send in salesforce you will see the send definition show up your Marketing Cloud account in the Triggered Sends folder as usual.

Hope this helps!

~Josiah Kaiser