Token for Requesting Campaign

Steve_Carlton
Level 1

Token for Requesting Campaign

I'd like to consolidate some of our flows and I wonder if there is a token to get the original campaign/program name that is requesting a campaign.

For example:

- "Demo Request" campaign flow requests the "Send Lead Alert Email" campaign. Ideally our team would get an email with "Demo Request" as the subject, sent from the "Send Lead Alert Email" campaign flow.

- "Webinar Registration" campaign flow requests the same "Send Lead Alert Email" campaign but alert email subject is "Webinar Registration".

I have tried several of the trigger tokens and everything seems to be connected to the requested campaign, not the campaign requesting the action.

Any ideas to do this without having multiple send email campaigns and email templates? Thanks in advance!

10 REPLIES 10
Grégoire_Miche2
Level 10

Re: Token for Requesting Campaign

Hi Steve,

I would try {{trigger.Name}}, but may be this is what you did?

Otherwise, no, I do not think there is this possibility.

-Greg

Josh_Hill13
Level 10 - Champion Alumni

Re: Token for Requesting Campaign

That token only pulls the current campaign, not the requesting campaign.

Perhaps a way is to paste the original Campaign to a field Last Campaign Responded and then use that token in your Alert email.

Steve_Carlton
Level 1

Re: Token for Requesting Campaign

I didn't think of this, seems like it would work though I hate creating a field for it (not the end of the world I know).

At least I can get away with using one email using the {{trigger.Name}} token and just request the same email using different campaigns. We don't have too many variations and it's a big step up from where we are now with 15 different email templates (mostly doing the same thing) and a ton of orphan smart campaigns.

For anyone following along or that finds this in the future:

Since my original plan doesn't seem feasible out of the box my new plan is:

1. Create one email and use the {{trigger.Name}} for the subject line.

2. Create "Demo Request" and "Webinar Registration" smart campaigns with the "Campaign is Requested" trigger.

3. In any flow where I would like to the lead alert email I will just need to request to correct campaign that I created in step #2.

Thanks!

Steve_Carlton
Level 1

Re: Token for Requesting Campaign

Josh is correct. In this instance {{trigger.Name}} is "Send Lead Alert Email"

Grégoire_Miche2
Level 10

Re: Token for Requesting Campaign

Hi Steven & Josh,

Per the doc:

  • {{trigger.Trigger Name}} is always the actual trigger itself. For example: Clicks Link in Email.
  • {{trigger.Name}} is the name of the asset that triggered the campaign. For example: Clicks Link on Webpage is the URL itself, subject for Salesforce triggers, etc.

So, if it was logic, Trigger.Name should give the triggering smart campaign not the triggered one

-Greg

Steve_Carlton
Level 1

Re: Token for Requesting Campaign

Just ran a quick test, this is what I got between the two:

Screen Shot 2017-01-18 at 1.20.17 PM.png

Unfortunately {{trigger.Name}} in this instance is the campaign I am requesting (to send the email).

Dan_Stevens_
Level 10 - Champion Alumni

Re: Token for Requesting Campaign

We use a similar approach to send out an alert to the campaign manager and the field/country marketer any time someone converts with any gated campaign content on our site.  Here's the design of the alert:

pastedImage_0.png

And here's how it renders:

pastedImage_1.png

Steve_Carlton
Level 1

Re: Token for Requesting Campaign

Nice, so is the "Avanade Last Touch Program" a simple text/string field that is updated before requesting the campaign?

Dan_Stevens_
Level 10 - Champion Alumni

Re: Token for Requesting Campaign

Yes it is.  Any time a conversion takes place within a program, these are common flow steps that we include in all of our programs:

pastedImage_0.png

The "Last touch xxx" fields are also used to populate the stage-specific fields when a lead progresses (e.g., "MQL Program/Date", "SAL Program/Date", etc. - essentially giving credit to the program that was responsible for progressing the lead to a new lifecycle stage).