New Token Type - Data Token | Community
Skip to main content
JaredEl
JaredEl
Level 2
July 9, 2026
New

New Token Type - Data Token

  • July 9, 2026
  • 9 replies
  • 175 views

Attached/below. Keen to hear counterpoints and other considerations for use.

 

    9 replies

    BlaneMcMichen-1
    Adobe Employee
    BlaneMcMichen-1Adobe Employee
    Adobe Employee
    July 9, 2026

    Can’t you already do this with Self-Service Flow Steps or other tools, like FlowBoost?

    JaredEl
    JaredElAuthor
    Level 2
    July 9, 2026

    Not entirely sure, but that’s within the Flow domain it seems.

    Above idea is the ability to include a token within Smart List filter(s) that pull a column of values from the configured data token(s) (and does intersect with the broader expressed desire of MKTO users to be able to “use tokens anywhere/everywhere”)

    JaredEl
    JaredElAuthor
    Level 2
    August 3, 2026

    Curious what you think of this one ​@Chris_Willis1 ; this comes up fairly frequently for us and I can imagine how adding this new token type could help Smart Lists become more responsive to important external data changes (operational in nature and campaigns) and not have to rely on a manually pasted values column. 

    Chris_Willis1
    Adobe Champion
    Chris_Willis1Adobe Champion
    Adobe Champion
    August 4, 2026

    I agree with ​@SanfordWhiteman ‘s comment below.  I believe a more applicable request is to allow a smart list filter to reference another field in the database and compare data values between one field and another.  If I’m reading the idea correctly, this appears to be what you are requesting.  

    Chris Willis - Fractional GTM Operations Consultant
      JaredEl
      JaredElAuthor
      Level 2
      August 5, 2026

      What you describe is something different and potentially a feature request and/or something Compute Formula (SSFS) could address in part (comparative functionality)

      SanfordWhiteman
      SanfordWhiteman
      Level 10
      August 3, 2026

      Upvoted but “data token” seems too broad. A Velocity token, for example, can contain JSON data (and in sophisticated setup you have lots of those). To me, it’s a picklist token. You literally plug it in where user-configurable picklists* are currently supported.

       

      * As opposed to system-mapped picklists like SFDC Users or SFDC Campaigns. Those currently can’t be overridden/appended with userland data so I would not expect them to support picklist tokens, either.


       

      JaredEl
      JaredElAuthor
      Level 2
      August 3, 2026

      yeah, true, as an expansion of Picklist Management perhaps, but then I wonder if gets too admixed with that feature; these are almost micro integrations in a sense so wondering if there’s a term (integration token?) between specificity of “picklist token” and too-broad/vague “data token” that gets at the fact that picklist values are not user-managed/added as documented in Picklist Management feature but pull from an external platform within the respective martech ecosystem; table token?

      sandy_logitech
      User Group Leader
      sandy_logitechUser Group Leader
      User Group Leader
      August 7, 2026

      I don’t see any reason for these to be marketed as “external” and they certainly wouldn’t be stored outside the standard Marketo db once you write them.

       

      They just have a different editor in the UI (key-value mapping, along the lines of the Form Editor Select/Radio/Checkbox editor) and are API-accessible like every other {{my.token}}.

      Terms & ConditionsAccessibility statement

      Loading footer...