TIP: {{Trigger.}} tokens also work for "Change program status" events | Adobe Higher Education
Skip to main content
Grégoire_Miche2
Grégoire_Miche2
Level 10
March 15, 2016
Pregunta

TIP: {{Trigger.}} tokens also work for "Change program status" events

  • March 15, 2016
  • 5 respuestas
  • 4650 visualizaciones

Dear community,

I was wondering today how we could create interesting moments for the people who attended a seminar or a webinar. We try to favor centralized interesting moments. Doing some testing, we discovered that, although they are omitted in the doc (Tokens for Interesting Moments - Marketo Docs - Product Docs ) "Change program status" events do populate the {{trigger.name}} and {{trigger.Trigger Name}} tokens. The first one will have the name of the program, the second one will just read "Change status in progression" (not that valuable though )

Therefore, you can use the first one to create an interesting moment on event or program change in statuses. Just write "Attended event {{trigger.name}}" in the interesting moment description.

-Greg

    Este tema ha sido cerrado para respuestas.

    5 respuestas

    Dan_Stevens_
    Dan_Stevens_
    Level 10
    March 15, 2016

    I didn't realize this wasn't widely known - so it's great that you're surfacing it here.  We actually do this today within our centralized Interesting Moments campaigns:

      Grégoire_Miche2
      Grégoire_Miche2Autor
      Level 10
      March 15, 2016

      Hi Dan,

      I fact, it makes sense it works. Just the docs does not mention it.

      -Greg

      Dan_Stevens_
      Dan_Stevens_
      Level 10
      March 15, 2016

      Greg - this was something our Marketo consultant shared with us when we initially configured our environment a couple years ago.

      A
      Anonymous
      March 16, 2016

      Greg, I was literally working on something similar yesterday where Sales reps were complaining about the naming of programs, etc (The naming conventions work great for systems, not as much for Sales). This might help as one of those items to simply things.

      Justin_Norris1
      Justin_Norris1
      Level 10
      March 16, 2016

      Thanks for sharing this Greg.

      I had thought this worked but then checked docs recently and it wasn't there, so assumed I had been dreaming.

      Robb_Barrett
      Robb_Barrett
      Level 10
      March 29, 2016

      Hey @Grégoire Michel​ -

      I just tried this out today in a CDV and {{trigger.Name}} populated the form name, not the program name:

      Robb Barrett
      Dan_Stevens_
      Dan_Stevens_
      Level 10
      March 29, 2016

      I've never tried it like this (using it in a CDV flow step).  I suspect this is happening since you're not using an IM flow step, where you define the IM type (event, etc.); or based on your trigger type.

      A
      Anonymous
      October 21, 2016

      Thanks for sharing. I also thought this was widely known. This is exactly how we have our interesting moments populated in one program.

      Términos y condicionesAccessibility statement

      Loading footer...