Token for Requesting Campaign | Community
Skip to main content
S
Steve_Carlton
Level 2
January 18, 2017
Question

Token for Requesting Campaign

  • January 18, 2017
  • 2 replies
  • 4806 views

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!

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    2 replies

    Grégoire_Miche2
    Grégoire_Miche2
    Level 10
    January 18, 2017

    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
      Josh_Hill13
      Level 10
      January 18, 2017

      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.

        S
        Steve_CarltonAuthor
        Level 2
        January 18, 2017

        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!

        Dan_Stevens_
        Dan_Stevens_
        Level 10
        January 18, 2017

        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:

        And here's how it renders:

          S
          Steve_CarltonAuthor
          Level 2
          January 18, 2017

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

          Dan_Stevens_
          Dan_Stevens_
          Level 10
          January 18, 2017

          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:

          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).

            Terms & ConditionsAccessibility statement

            Loading footer...