Marketo Field Limits by Field Type | Community
Skip to main content
June 22, 2017

Marketo Field Limits by Field Type

  • June 22, 2017
  • 19 replies
  • 23752 views

Issue


Several types of fields in Marketo have requirements for the type of data that can be stored, as well as the limit to how much data can be contained in that field type. The Custom Field Type Glossary can tell you what fields are available, and this article will show you details on the type and maximum limits for those fields. 

 

Field Types & Limits

Boolean

Can only be set to “true” or “false” (stored in the database as 1 or 0).

 

Currency

Maximum value of 9223370000000000000.  Will be displayed with the currency set in your instance under Admin -> Location.

 

Date

Must be formatted “MM/DD/YYYY”.

 

Datetime

Must be formatted “MM/DD/YYYY HH:MM:SS”.

 

Email

Must be a properly formatted email (user@example.com).

 

Float

Can include decimals up to the hundredths place.  The value will round to the nearest hundredth (eg. 99.999 rounds to 100, 99.985 rounds to 99.99).  Maximum value of 10000000000.

 

Formula

See this guide: Create and Use a Concatenated String (Formula) Field 

 

Integer

Values are limited to between -2147483647 to 2147483647.

 

Percent

Must be a full number without decimals.  Maximum value of 9223370000000000000.

 

Phone

Can have letters, numbers, or characters.  Maximum of 2,000 characters.

 

Score

Maximum score of 2147483647.  If the score is increased higher than that, the score will reset to -2147483647.

 

String

Can contain letters, numbers and special characters.  Limit of 255 total characters

 

Text Area 

Can contain letters, numbers and special characters.   Limit of 65,535 total characters

 

URL

"http://"  will automatically be appended to the value if the value doesn't have that prefix or "https://" already.  Does not have to be formatted any further (Generic top-level domain not required).

 

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

19 replies

SanfordWhiteman
Level 10
June 22, 2018

but my understanding is that it is specific to how Marketo handles string fields, not on string fields in general

I'm definitely talking about Marketo's concept of Strings, not general concepts.

Three examples (of many) from one of my instances are:

  • Person Type - string(50), accurately described via API as string(50)
  • Marketo Social Facebook Profile URL - string(2000), accurately described via API as string(2000)
  • Business Unit - actually string(2000), inaccurately described via API as string(255)

Because of the inconsistencies, you must assume a field described as string(255) nevertheless requires string(2000) to store, or else you'll lose data. But you should also avoid inserting > 255 characters into the field -- wherever you have such control, that is.

July 2, 2018

Are these limits still correct as the current documentation found here Custom Field Type Glossary - Marketo Docs - Product Documentation has the following note?

Note 

Most fields don’t max out at number of characters, but instead at amount of bytes. Because of that, we’re unable to provide a definitive character limit for each field. The two exceptions, however, are Text Area (3200 characters) and String (255 characters).

That is quite a difference on the text area - 3200 vs 65,535 characters

SanfordWhiteman
Level 10
July 2, 2018

They docs aren't fully correct in either source (as you can see in my comment above and my blog posts on the topic).

Textareas are varchar(65535). However, you have to be acutely aware of the SFDC limit for Text Area (long) as well. If you sync Marketo Textarea ↔ default SFDC Textarea (32K) you will see truncated data.

September 26, 2018

If this URL is being used in the context of a template as an <a href="{{lead.url_field}}"> or in an email script token, how does it handle the tracking?

As far as I've seen, you have to always prepend URLs as http://${variable} or http://{{my.url_field}}... Would the url field avoid this requirement?

SanfordWhiteman
Level 10
September 26, 2018

Very astute question, and as far as I know the URL type does not solve (i.e. walks you right into) the tracking problem.

Julia_Rosentha3
Level 2
February 27, 2019

You've most likely solved your issue but thought I'd share this just in case... When importing a list these date formats worked for me:

02/27/2019T11:45:00.000Z

11/15/2018T15:36:00.000GMT+11:00

The 'Z' and 'GMT+11:00' refer to your local timezone

Hope you got your stuff sorted.

Jules

SanfordWhiteman
Level 10
February 27, 2019

Z is UTC, not local.

September 12, 2019

It's so confusing that key learning content such as this is hosted on the "nation" platform vs. in the Marketo knowledge base (docs) or developers. 

Julia_Rosentha3
Level 2
September 13, 2019