Action based upon SFDC Campaign Type

[Loren_Posendek]

Hi all — Has anyone ever used a trigger and/or filter to perform an action based upon a specific SFDC campaign type?

Here's the scenario: added to SFDC campaign (type=Event), data value changes, update member status (type=Event) to specific a value.

Ideally, it'd be helpful to use a SFDC campaign type filter rather than entering each campaign name.

Thank for any ideas in advance!
Loren

[Grégoire_Miche2 · Accepted solution]

Hi Loren,

This will be impossible because campaign type is not an information that Marketo is aware of. Vote here:

Here is a workaround to this: In SFDC, create a workflow on the campaign object that will structure the name of the campaign and enforce a naming convention that enables to identify the campaign type from the name. For instance all events will be named [EVT]-Name of the campaign. Then, in Marketo, just have your trigger to be set as:

-Greg

[Loren_Posendek]

Thank you! That was going to be my second option, but wanted to put the question out there. Appreciate the advice!

[Casey_Grimes]

Hi Loren,

So this is possible, but like so many things in Marketo, requires a bit of a hack-around—and what you're willing to do in order to make it work.

When you use a filter like "Member of SFDC Campaign" or a trigger like "Added to SFDC Campaign," Marketo is actually reading the Campaign Member object rather than Campaign itself. What does interact with Campaigns directly, though, are Marketo Programs! The Channels that you set up in Marketo directly correspond to your Campaign Type if you create your SFDC Campaign inside Marketo rather than inside Salesforce. From there, you can just listen for people being added to those programs (or any program with your Event-specific statuses.)

If that's not practical, you could always write a workflow that makes a note in some field on the Campaign Member object when a record is created under a Campaign with the type Event. In that case, you'd just use your standard Member of SFDC Campaign trigger/filter combo with a constraint on that particular field.

[Grégoire_Miche2]

Hi Courtney,

I thought of using the programs as well, but the program Channel is not a constraint on "added to program" trigger or "member of program" filter. Plus, unlike SFDC, you cannot normalize the name of a program through a workflow, you have to rely on user's skills and goodwill.

See ​ and

Also, SFDC campaign member fields are not accessible from Marketo either. Vote there:

-Greg

[Casey_Grimes]

Hi Greg,

You're correct that there's no Channel constraint on Program filtering, but there is Channel definition in your Status constraint, so you can just add all applicable statuses. It's a weird workaround, but that's how I roll. Moreover, with Campaign Member fields you can at the very least use them for constraining on filters, even if you can't (normally) access the values in the field, which would meet this use case.

[Grégoire_Miche2]

Hi again Counrtney,

May because I was a SFDC expert before become a Marketo consultant, I'll stick to the workflow enforcing a naming convention on campaigns

-Greg