Including Campaign Member Fields

[Anonymous]

It's be great if Marketo could pull in the custom Campaign Member fields.  It would be even better if we could update these fields with Marketo. 
Example: tracking session preferences (attending AM or PM)  for an upcoming event using our custom campaign member fields

[Anonymous]

Just to follow up, cross-obect workflow on campaign member will do it for any campaign.  The workflow is triggered on creation of a campaign member and you don't have to specify the name of the campaign in the workflow.  When the campaign member is created in any campaign, then execute the field update on that campaign member in that campaign.  Specifically, I wanted to capture the name of the lead source that was driving people to a particular campaign.  We parse that data out of URL parameter and capture it on a Marketo form.  The form inserts that value into a custom field on either the Lead or Contact.  You use the Marketo action Add to SFDC campaign to add the lead or contact to a SFDC campaign.  When the campaign member is created by that action, then the SFDC workflow does a field update from the Lead/Contact record in SFDC to the campaign member.  In my opinion, the SFDC cross-object field update workflow eliminates the need for this functionality in Marketo.  Yes, it would be nice to have so you don't have to create that workflow in SFDC, but at this point, I can't envision any scenario where I would need Marketo to update a field value on a Campaign Member because I can do it in SFDC.

[Anonymous]

This is a big deal for us, as we use Marketo for event sign-ups and need to add extra membership information.  I'd prefer not to have to use the cross-object workflow -- while it works, the functionality is outside of Marketo and anyone coming to the system cold would have no idea how those fields were getting updated.  I would love to see a Marketo-native implementation for these fields.

[Anonymous]

Subscribing! - Delinda

[Anonymous]

voted -- subscribing

[Anonymous]

This would be extremely useful to be able to track the promotion source for a specific lead for each campaign. Then we can see which promotion sources (Facebook vs. Twitter vs. email syndication) works best for driving responses to different types of campaigns (webinars vs. white papers, etc.).

[Anonymous]

Dani, would you (or anyone) be willing to share the Trigger code that updates the campaign member field?

[Anonymous]

We use a pair of cross-object workflows in SFDC to address this.

Workflow 1: Lead: Custom Field to Campaign Member: Custom field
- Check to make sure it's not a lead and the Campaign Member: Custom Field is null.
- Then trigger a field update to copy the value from the Lead: Custom Field to the Campaign Member: Custom Field

Here is the WFR on Campaign Member:

ISBLANK(ContactId ) && 

ISBLANK(CampaignMemberCustomField__c)

Workflow 2: Contact Custom field to Campaign Member Custom field
- Check to make sure it's a Contact, that the Contact: Custom Field is not null, and the Campaign Member: Custom Field is null.
- Then trigger a field update to copy the value from the Lead: Custom Field to the Campaign Member: Custom Field

Here is the WFR on Campaign Member:

NOT(ISBLANK(ContactId )) && 

ISBLANK(CampaignMemberCustomfield__c) && 

NOT(ISBLANK(Contact.Customfield__c))

Important Note:  There is some important sequencing in your MKTO Sync Programs for this to work correctly.
This SFDC WFR is triggered when the Campaign Member is created.  The SFDC Campaign Member is created by a MKTO Action Add to SFDC Campaign.  It is important to MKTO Sync the lead to SFDC, then add a Wait 5 Minutes step, before triggering the MKTO Add to SFDC Campaign Action.  The Wait step ensures that Sync has completed updating the Custom Field on the Lead or Contact before creating the Campaign Member - which in triggers the SFDC Cross Object Field Update to copy the value from the Lead/Contact Custom Field into the Campaign Member Custom Field.

Other cool things that we did with this:
- We pass this custom field data via URL parameters so we can track every lead source
- We created cookies that store the latest URL parameter on the visitor's browser so we can maintain the tracking if they abandon the MKTO landing page to visit our corporate website and return to the landing page later.
- We use hidden javascript on our MKTO landing pages and pass the SFDC Campaign ID into custom Lead/Contact fields.  Then we use a Token to tell the MKTO which SFDC Campaign to Add the Lead to.
- Next steps: we're working on expanding our URL parameter strategy to facilitate A/B testing with different links and link placements in emails.
 

[Anonymous]

Dani - Thank you for spelling that out! That's easier than the route I was going and it works great.

[Anonymous]

voted!

[Anonymous]

Dani, would be very interested in know more about the other cool things you were able to do.
Do you have more information on any of these things?

- We pass this custom field data via URL parameters so we can track every lead source
- We created cookies that store the latest URL parameter on the visitor's browser so we can maintain the tracking if they abandon the MKTO landing page to visit our corporate website and return to the landing page later.
- We use hidden javascript on our MKTO landing pages and pass the SFDC Campaign ID into custom Lead/Contact fields.  Then we use a Token to tell the MKTO which SFDC Campaign to Add the Lead to.
- Next steps: we're working on expanding our URL parameter strategy to facilitate A/B testing with different links and link placements in emails.