Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: Marketo Improvements

Answered
David Irvine User

Marketo -> Snowflake.
The lead table fields names in Marketo have spaces, Snowflake doesn't allow this so the field names are transformed. The lead describe table give a mapping of RestAPI and front end names. Add to the the Transformed Lead Field names in snowflake Such that we can systematically return to the appropriate field names where necessary.

Please sign in to leave a comment.

Comments

3 comments

Date Votes
  • Official comment
    Calvin Fivetranner

    Hi David Irvine, Calvin from the product team here!

    Thanks for submitting this feature request. I need more details to help me understand what improvement you would like. What analytical questions are you trying to answer that you can't today with the 'lead' and 'lead_describe' tables? Can you provide an example please?

  • David Irvine User

    Hi Calvin,
    Its not so much a specific question but more improvements in the data modelling.

    When displaying the lead data ideally we would like to show the front end names of the data in the dashboards. Currently the lead describe table gives us a mapping from Rest API name to front end name.
    However the field names in snowflake don't match the rest API names in the lead describe table so we can't automate a mapping from one to the other.

    An example would be for example a custom Marketo Field "Lead Source - Most Recent" When showing in our Data Model this is the name we would like shown as this is familiar to the end users.
    Perhaps the Rest API Name is "lead_source_most_Recent__C"
    But in Snowflake the Field name is "LEAD_SOURCE_MOST_RECENT_C" Which is similar but not identical and not always systematic. if the Lead describe or another table also included the resulting Snowflake column name that would enable easy consistent mapping of the friendly names for each field in the resulting data model.

  • Calvin Fivetranner

    Thanks for the detailed response, David Irvine.

    This request makes sense from a data modeling perspective - I can understand why having the resulting Snowflake column name in a table for mapping purposes is useful. To clarify, the reason the Front End names don't always match up with the REST API names is because of our column naming rule set.

    I'm going to put this in the backlog for now so that we can look into how this request can be implemented and I'll continue to monitor demand via this feature request.