Option 1 – “Batch API” The Batch API solution allows you to extract multiple activity types (listed here ) over a long interval at your discretion. Each API call returns one page of data and the following. The first call requires you to create a paging token. https://developers.marketo.com/rest-api/endpoint-reference/lead-database-endpoint-reference/#/Activities/getActivitiesPagingTokenUsingGET For subsequent calls to this endpoint, use the nextPageToken returned from the response. This endpoint will always return the nextPageToken. A “next page token” which represents the subsequent page of data. A “moreResult” Boolean. You’ll loop through until a “false” is returned, indicating that there is no more data to be returned.     More information is here https://developers.marketo.com/rest-api/lead-database/activities/ and the API specifics are here https://developers.marketo.com/rest-api/endpoint-reference/lead-database-endpoint-reference/#/Activities   Restrictions See below   Option 2 – “Bulk API”             The Bulk Activity API may be used to extract up to 500mb of data per day, and up to a date range of 31 days in each call. the Bulk API has a very different process than the batch. At a high level it is as follows Create the Bulk Extract job (API call #1, returns the job ID) Enqueue the Bulk API Job using the job ID Poll the API using the Job ID until a status of “completed” is returned. This indicates the full CSV activity extract is ready to be streamed from the Marketo server. It will remain there for 7 days. Stream the file down (API call #4) You can have up to 10 jobs enqueued, two will run concurrently. A good practice is to extract them by calendar month. One call for January, One call for February, etc.                                                                                                                                                                                                                                                                                      More detail is available here https://developers.marketo.com/rest-api/bulk-extract/bulk-activity-extract/ and the API endpoints are here https://developers.marketo.com/rest-api/endpoint-reference/lead-database-endpoint-reference/#/Bulk_Export_Activities   Restrictions Limited to 500mb of data per day Limited to extracting a range of 31 days per call Limit resets at 12 midnight US Central Time   Helpful links Blog: https://nation.marketo.com/t5/Product-Blogs/Activity-Types-Attributes-and-Exporting/ba-p/244377 Activity types: https://docs.google.com/spreadsheets/d/1i-3GVbpUK7oc8YanOokY_1yd_Ly124urK2HHydrN0d8/edit#gid=1253153029 Retention Policy: https://nation.marketo.com/t5/Knowledgebase/Marketo-Activities-Data-Retention-Policy-Overview-amp-FAQ/ta-p/250750 ... View more

Customers often ask about exporting Marketo Activity Data. This can be accomplished using the bulk activity API or the standard activity API.   Some things you might consider are... Is this a one-time or a recurring activity export? What activities do I need? Marketo Activities Data Retention Policy Lead Activity and Campaign Membership data will be stored for a rolling 25 months past the activity date, and certain high-volume activity data will be retained for a rolling period of 90 days past the activity date. If there are activities in your instance older than the policy dates they may be available to export. There's no guarantee they will be available if you wait to start your export.   The bulk API is a good option when you want to get activities in a maximum 31-day time frame. This is a great approach for a recurring extract with a start_date and an end_date. Once the file is ready for download, you'll be able to download a CSV of the data with the activity jSON parsed into columns. This approach has the following limitations By default, Marketo instances are limited to 500 mb of downloaded bulk data per day This API limit can be increased. You should speak to your CSM if you're interested. Bulk api downloads are limited to a window of 31 day time frame   The activity API is the better option for a wider window of activities "all activities in the past 12 months" for example. Up to 300 activities are returned per call, returned as jSON, along with a "has more records" flag and if appropriate, a "nextPageToken" to pass into a subsequent call This approach has the standard per- call limitations of the standard REST API, as follows By default, Marketo instances are limited to 50,000 calls per day. This API limit can be increased. You should speak to your CSM if you're interested. You may have up to 10 concurrent calls You may execute up to 100 calls in a rolling 20 second window Activity Types don't change for the great majority of Marketo instances (the exception might be extremely old Marketo instances).   Here are a few examples of what extracted activity looks like:   Visit Web Page - Example 1 Attribute                           Example Value marketoGUID                 3418151667 leadId                               130810022 activityDate                     2019-11-01T00:00:00Z activityTypeId                 1 campaignId                     null primaryAttributeValueId   10720672 primaryAttributeValue       www.acme-company.com/en/about-us/press/news/all-news.jsp attributes                            {"Client IP Address":"103.249.182.5","Query Parameters":"","Referrer URL":"https://www.acme-company.com/en/about-us/press/","User Agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3865.120 Safari/537.36","Webpage URL":"/en/about-us/press/news/all-news.jsp"}     Visit Web Page - Example 2 Attribute                                    Example Value marketoGUID                  3418179520 leadId                                130810022 activityDate                     2019-11-01T00:08:34Z activityTypeId                 1 campaignId                     139182 primaryAttributeValueId    60651643 primaryAttributeValue       partner.acme-company.com/partners/Menu/P_AU_WD2_Drive_Away attributes {"Client IP Address":"203.39.1.50","Query Parameters":"mkt_tok=eyJpIjoiT1RZNFpqQXlPVGN5TldRMiIsInQiOiJNQWZPN1dFUEJaVzl4WTg5SU1MeEJ1a2ptdHRTQjF1MHJqMk5Fd1BBWVl1dlBaRUxSRk1UNWNBVmhwNlNYTFJVZzNEUG9xYlgyK2Q3Q1RkdmZoblFwVlI3RU1yZ1FmQ3BKVm1vY08rWGY3TTVtZGZRb0tSM3E4T2xXemN5V20wbDVveVFcL1hmc0YrQjNXKzcwM1ZHNFZBPT0ifQ==","Referrer URL":"https://partner.acme-partner.com/partners/secur/frontdoor.jsp?sid=00DA0000000abSm!ARsAQMQb.ZPj5.J_qmU5zeeZ0S0HeaNcr1g78VCSEcccrFSkSlu9HS6hO2777h6w3kbebSPr4NTpsqz6ZbQaKWmmRpQ22qoA&retURL=/partners/Menu/P_AU_WD2_Drive_Away?mkt_tok=eyJpIjoiT1RZNFpqQXlPVGN5TldRMiIsInQiOiJNQWZPN1dFUEJaVzl4WTg5SU1MeEJ1a2ptdHRTQjF1MHJqMk5Fd1BBWVl1dlBaRUxSRk1UNWNBVmhwNlNYTFJVZzNEUG9xYlgyK2Q3Q1RkdmZoblFwVlI3RU1yZ1FmQ3BKVm1vY08rWGY3TTVtZGZRb0tSM3E4T2xXemN5V20wbDVveVFcL1hmc0YrQjNXKzcwM1ZHNFZBPT0ifQ","User Agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.70 Safari/537.36","Webpage URL":"/partners/Menu/P_AU_WD2_Drive_Away"}     Fill Out Form - Example 1 Attribute                                     Example Value marketoGUID                   3418150822 leadId                                 330682053 activityDate                       2019-11-01T00:00:16Z activityTypeId                   2 campaignId                       null primaryAttributeValueId      2399 primaryAttributeValue         Web - Email Footer Form attributes {"Client IP Address":"159.215.34.1","Query Parameters":"","Referrer URL":"https://www.acme.com/br/pt/work/solutions/system/s1/power-and-grid-systems.jsp","User Agent":"Apache-HttpClient/4.3.3 (java 1.5)","Webpage ID":19497957,"Form Fields":"a:23:{s:6:\"module\";s:11:\"leadCapture\";s:6:\"action\";s:4:\"save\";s:18:\"responsys-settings\";s:12:\"tcm:25-17355\";s:5:\"email\";s:25:\"jim_miller41514@gmail.com\";s:16:\"MW_CUSTOMER_TYPE\";s:11:\"Electrician\";s:20:\"g-recaptcha-response\";s:548:\"03AOLTBLTBm4ZxKR65f4d9wAehfQyyNqOg1wQffMpDpMTiVWpaCy2YrheUMK9QoBD5rEFadyCAoLGjKm6tmkakzZ6x6saN6s5wz6LzkMkeM5egSYdhIlD1wxuDTABO-AA2iai3VEXACMQcFVNTJjhCqVfWpW4UJLgi9OwNQJIu6v3Yy7QC0sCvn6El-raKjQH4YeBlrxqrlNsDoIGgG9f0VImxrGCT7umOMrj0hOfPopHNiy3YOaZaNd4KOAynA-9JuUtqfC-51fhd59wquJfJbgQE5gb-dU9dTA7YkLGjDdNjBjwsu1PKrxnXfcbNi3S1hwP3rxzciDryAF2lYbVYXmBk7zi_nSRzhCpZdleJuY6Vlxicqr7v4qDIF2sKlgwqixYTmEchffVQigIiooekMyvZy241GhUtNpQfUQScAzOevO6_iT8MJCesMLAbPcUHvpn53vP2VKXN8rtDS0JgAeNGObBzzog-7WkOG0S310b-al6CVkmSZ3I9XCJUlCELmoBuEhagpUTHOIPV7yvwTQgxCwJNvQZdpw\";s:12:\"reCaptcha_id\";s:13:\"tcm:25-371393\";s:5:\"Email\";s:25:\" jim_miller41514 @gmail.com\";s:4:\"iama\";s:11:\"Electrician\";s:10:\"MiddleName\";s:0:\"\";s:12:\"Unsubscribed\";s:5:\"false\";s:7:\"keyCode\";s:5:\"z609v\";s:10:\"LeadSource\";s:7:\"Website\";s:15:\"SourceDetail__c\";s:10:\"www.acme.com\";s:16:\"EmailPostingDate\";s:0:\"\";s:17:\"InferredCountry\";s:2:\"BR\";s:18:\"InferredLanguage\";s:2:\"pt\";s:6:\"formid\";s:4:\"2399\";s:13:\"_mktoReferrer\";s:76:\"https://www.acme.com/br/pt/work/solutions/system/s1/power-and-grid-systems.jsp\";s:12:\"referringURL\";s:25:\"https://www.acme.com/br/pt/\";s:8:\"_mkt_trk\";s:52:\"id:178-XXX-668&token:_mch-acme.com-1572566332033-60671\";s:10:\"munchkinId\";s:11:\"178-XXX-668\";s:4:\"form\";s:4:\"2399\";}"}     Fill Out Form - Example 2 Attribute                                     Example Value marketoGUID                     3418826618 leadId                                 222819241 activityDate                        2019-11-01T06:53:40Z activityTypeId                     2 campaignId                        91108 primaryAttributeValueId     5993 primaryAttributeValue        Enriched Profile Form - Global EN attributes {"Client IP Address":"41.202.207.139","Query Parameters":"mkt_tok=eyJpIjoiTVRjellqRTROell5TVdFNSIsInQiOiJtMGxvdXBKS1ZcL29FZUF5UzZCY3Y2V2tHbmJxNjY1cndrelFWalFZSUdNT3M4Z095WnhIeFwvbXpJUWRrVkpBdVBZUHpJcHZSbjZDUVRCR2s0cjJCSDhua2RyXC9OZ1EzdnhJM01BMVJIVFUwZmNOcHVRWTVOUGtqajFyeStDNGJSaENXYWV2czlqZGpQVEpQR055eWxFYlE9PSJ9","Referrer URL":"https://go.acme.com/WW_201903_Welcome-Program_01-Profile-Completion-EP-LP.html?mkt_tok=eyJpIjoiTVRjellqRTROell5TVdFNSIsInQiOiJtMGxvdXBKS1ZcL29FZUF5UzZCY3Y2V2tHbmJxNjY1cndrelFWalFZSUdNT3M4Z095WnhIeFwvbXpJUWRrVkpBdVBZUHpJcHZSbjZDUVRCR2s0cjJCSDhua2RyXC9OZ1EzdnhJM01BMVJIVFUwZmNOcHVRWTVOUGtqajFyeStDNGJSaENXYWV2czlqZGpQVEpQR055eWxFYlE9PSJ9","User Agent":"Mozilla/5.0 (Linux; Android 8.1.0; TECNO F1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.157 Mobile Safari/537.36","Webpage ID":50400813,"Form Fields":"a:30:{s:6:\"module\";s:11:\"leadCapture\";s:6:\"action\";s:5:\"save2\";s:9:\"FirstName\";s:12:\"Jean Paul\";s:8:\"LastName\";s:5:\"Mills\";s:7:\"Company\";s:11:\"Adobe\";s:4:\"iama\";s:19:\"Home Owner/Consumer\";s:5:\"Title\";s:6:\"Owners\";s:11:\"jobFunction\";s:11:\"Electrician\";s:7:\"Country\";s:2:\"CM\";s:10:\"LeadSource\";s:0:\"\";s:15:\"SourceDetail__c\";s:0:\"\";s:7:\"keyCode\";s:0:\"\";s:11:\"utmCampaign\";s:0:\"\";s:9:\"utmSource\";s:0:\"\";s:7:\"utmTerm\";s:0:\"\";s:6:\"gamify\";s:4:\"null\";s:18:\"InferredLanguage\";s:2:\"fr\";s:6:\"formid\";s:4:\"5993\";s:4:\"lpId\";s:6:\"469030\";s:5:\"subId\";s:2:\"52\";s:10:\"munchkinId\";s:11:\"178-XXX-668\";s:5:\"lpurl\";s:113:\"//go.acme.com/WW_201903_Welcome-Program_01-Profile-Completion-EP-LP.html?cr={creative}&kw={keyword}\";s:12:\"followupLpId\";s:6:\"469032\";s:2:\"cr\";s:0:\"\";s:2:\"kw\";s:0:\"\";s:1:\"q\";s:0:\"\";s:8:\"_mkt_trk\";s:68:\"id:178-XXX-668&token:_mch-acme.com-1572591226393-82542\";s:7:\"formVid\";s:4:\"5993\";s:7:\"mkt_tok\";s:248:\"eyJpIjoiTVRjellqRTROell5TVdFNSIsInQiOiJtMGxvdXBKS1ZcL29FZUF5UzZCY3Y2V2tHbmJxNjY1cndrelFWalFZSUdNT3M4Z095WnhIeFwvbXpJUWRrVkpBdVBZUHpJcHZSbjZDUVRCR2s0cjJCSDhua2RyXC9OZ1EzdnhJM01BMVJIVFUwZmNOcHVRWTVOUGtqajFyeStDNGJSaENXYWV2czlqZGpQVEpQR055eWxFYlE9PSJ9\";s:13:\"_mktoReferrer\";s:349:\"https://go.acme.com/WW_201903_Welcome-Program_01-Profile-Completion-EP-LP.html?mkt_tok=eyJpIjoiTVRjellqRTROell5TVdFNSIsInQiOiJtMGxvdXBKS1ZcL29FZUF5UzZCY3Y2V2tHbmJxNjY1cndrelFWalFZSUdNT3M4Z095WnhIeFwvbXpJUWRrVkpBdVBZUHpJcHZSbjZDUVRCR2s0cjJCSDhua2RyXC9OZ1EzdnhJM01BMVJIVFUwZmNOcHVRWTVOUGtqajFyeStDNGJSaENXYWV2czlqZGpQVEpQR055eWxFYlE9PSJ9\";}"}     Click Email - Example  Attribute                                     Example Value marketoGUID                   3418156845 leadId                                 254847408 activityDate                      2019-11-01T00:00:30Z activityTypeId                  11 campaignId                      106171 primaryAttributeValueId     156271 primaryAttributeValue       EG_201904_EDM-to-all-our-Database-Public-Services-correct.01-EDM to all our Database Email attributes {"Choice Number":"0","Campaign Run ID":"313553","Platform":"Android","Device":"Android","Step ID":"237885","User Agent":"Mozilla/5.0 (Linux; U; Android 9; ar-eg; Redmi Note 8 Build/PKQ1.190616.001) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/71.0.3578.141 Mobile Safari/537.36 XiaoMi/MiuiBrowser/11.1.7-g","Is Mobile Device":true,"Link":"https://www.acme.com/eg/en/work/campaign/energy-challenge.jsp"}     I've created a list of those types, here Activity Type Attributes - Common - Google Sheets which you're welcome to download and use. The first tab shows the different Activity Types and the second tab shows common attributes for all activities. The sheet also shows many different activity examples. In these examples the JSON has been parsed out.       Note: Please note the  attribute value for the fills out form activity can be confusing.    Activity Type Attributes are also shown to illustrate the fact that different activity types have different attributes.   Marketo Professional Services is happy to do this with or for you you, and for details you should reach out to your PS Engagement Manager who can help scope the effort. ... View more

When you decide to secure your marketo landing pages using SSL, the final step will be Marketo consulting "cutting over" the server so that all of the landing pages redirect to their SSL versions. When that happens you need to worry about mixed content. What is that? Good question. Mixed content is non secure content (HTTP) served within a secure page (HTTPS), and it comes in two types, "active" and "passive". Passive mixed content such as the following will generall still render (depending on browser and version, but will result (again depending on the browser) in a warning] <img> src attribute <audio> src attribute <video> src attribute <object> where the object performs http requests Active mixed content will generally cause a larger problem with the page, such as the visual aspects not rendering (CSS) <script> src attribue <iFrame> src attribute All uses of CSS where the CSS is a url <object> (data attribute) All mixed content should be addressed, but only the active content will actually break the pages. The official definition of mixed content as defined by the W3C is here -->  Mixed Content ... View more

It's true. Here at Marketo we use Slack, and our Slackbot HATES server side post.. so much so that when you mention it, it chastises you. It's really pretty amusing. Fine! Jeez. Really though, Slackbot is completely right. Server side post has effectively been replaced by the following REST endpoint, which is great and scalable. http://developers.marketo.com/rest-api/lead-database/leads/#push_lead_to_marketo This, along with my other most recent blog, provide a good blueprint for associating leads in a non marketo form with only one REST call. No fewer than 3 customers have had this very question for me this week alone, so it seems like a hot topic. ... View more

A common question we see in consulting relates to how a customer can use a non Marketo form, but still associate that lead with a known lead in Marketo. With Marketo forms, of course, it's simple, you jhust submit the form. With Non Marketo forms, its a bit tricker, but still possible. One reason you might do this is because you're submitting a login form, and obviously that doesnt really make sense as a Marketo Form. Not to worry! First, lets talk about some confusing names of important items related to the Marketo Munchkin Cookie and this process Item What is it? _mrk_trk The name of the hidden form field (more on that in a moment) _mkto_trk The name of the Marketo Munchkin Tracking Cookie. The cookie contains the Munchkin ID of the instance along with a unique identifier for this lead (known or anonymous. The details on the tracking cooke are shown below. I use a plugin called "Awesome Cookie Manager" to view cookies. You can see yours by going to any site that leverages munchin Tracking Cookie Marketo Munchkin Cookie Value Armed with this knowledge, we can look at the solution here. the process is straightforward and we're helped by Munchkin. When you create a form field called "_mkt_trk" within a non marketo form on a page where Munchkin code is running, Munchkin knows enough to populate the value of that form with the Munchkin Cooke value. Cool right? So, what does that mean? That means that in the following really simple non marketo form, youll not only receive the regular form fields.. youll also have the lead's cookie ID as well... and with THAT, you can use REST from your back end process to associate the lead. That brings us to the second step which is associating the lead. for this youll need the marketo ID and the cookie ID. you've now got the cookie ID, and getting the Marketo ID is a simple matter of getting it from Marketo. You'll need to call the following two REST endpoints. first you'll use GetMultipleLeadsByFilterType, passing in the Email address to get the Marketo ID (http://developers.marketo.com/rest-api/endpoint-reference/lead-database-endpoint-reference/#!/Leads/getLeadsByFilterUsin… ) then, you'll use AssociateLead (http://developers.marketo.com/rest-api/endpoint-reference/lead-database-endpoint-reference/#!/Leads/associateLeadUsingPO… ), passing in that ID, and the cookie Id. Alternatively, you can use a amazing new REST endpoint .... "push lead to marketo" which you can read about here!  http://developers.marketo.com/rest-api/lead-database/leads/#push_lead_to_marketo ... View more

I've talked before about using Postman to make REST API calls, and it's perfectly fine for one off calls for testing.. but what about those times when you need a full on programming language to upsert leads or custom objects, or perform some other function using the REST API? Well, you can write your own libraries to make it easier, or you can leverage the Marketo Rest Python library created by Jep Castelein This article will serve as a step by step guide for getting up and running and making basic hello world calls using Python. Products We'll be using the following, all of which are free. Python (Download the latest version here) pip for Python - A great installer program we'll use to install the library Marketo-Python-REST library PyCharm - A great Free IDE (the Community Edition is free) Step 1 - Python 3.x.x In MacOS , you'll notice that python 2.7 comes pre installed, but its perfectly acceptable to run more than one version of Python. Download the Python DMG file and install it. Make sure it installed by opening up a terminal and typing python3 . Simple! Step 2 - PIP You can follow the directions here, downloading get-pip.py from https://bootstrap.pypa.io/get-pip.py , then running the following command, making sure you run it against Python 3.51 as follows python3 get-pip.py Seriously. It's that easy. Step 3 - The Marketo Rest Python Library Again, very simple. At the command line, ensure you have pip installed by typing pip -V It should indicate that you're installed on version 3.x.x (depending on your version) Note that you might have installed it as pip3, so check that. Next, type the following (adding sudo on the mac) pip install marketorestpython It should look rather like this: Step 4 - PyCharm You guessed it. Download the dmg file for mac, and install it. Create a project called "Marketo Python" and get creative.. maybe you want to set up folders for your different tasks. For this one, I created a hello world folder Create a new file, and enter the following substituting your own Marketo instance credentials from marketorestpython.client import MarketoClient munchkin_id = " your value " client_id = "your value" client_secret = "your value" mc = MarketoClient(munchkin_id, client_id, client_secret) lead = mc.execute( method = 'get_lead_by_id' , id = 1001 ) print (lead) The library is quite well documented here.. so get creative! Let us know in the comments how you're using it! https://github.com/jepcastelein/marketo-rest-python Update! If you get an error like "HTTP Get Exception! Retrying....." and / or "SSLV3_ALERT_HANDSHAKE_FAILURE" in Mac OS Sierra, you likely need Install requests with extra security packages using: pip install requests[security] . It's further discussed in this requests issue on github . ... View more

Previously I talked about creating nested SPF entries , but as was pointed out to me by our excellent deliverability team and Kiersti Esparza​ specifically.. there is another way to handle this, and there are a few things we commonly see as misconfigurations and causes of breakage with SPF, and I'll talk about them here! If you have a large set of IPs and or domains and want to include them ALL in SPF, it can get out of hand quite quickly. Character String Length SPF records have a limit of 255 characters in a single string. Any more than that and the record will come back as invalid. We have some workarounds, however... Approach 1 - Multiple Strings To have more than 255 characters in an SPD record, the record can be broken into multiple strings. The strings are then concatenated together, without spaces, as shown. IN TXT "v=spf1 .... first" " second string..." MUST be treated as equivalent to IN TXT "v=spf1 .... first second string..." EXAMPLE text = "v=spf1 ip4:199.15.212.0/22 ip4:72.3.185.0/24 ip4:72.32.154.0/24 ip4:72.32.217.0/24 ip4:72.32.243.0/24 ip4:94.236.119.0/26  ip4:37.188.97.188/32 ip4:185.28.196.0/22 ~all" (could be) text = "v=spf1 ip4:199.15.212.0/22" " ip4:72.3.185.0/24 ip4:72.32.154.0/24 ip4:72.32.217.0/24" " ip4:72.32.243.0/24 ip4:94.236.119.0/26" " ip4:37.188.97.188/32 ip4:185.28.196.0/22 ~all" Approach 2 - Some more detail on the previous blog - Nested or Cascaded entries This example if for Marketo.com, and you can see that marketo.com is the top level SPF entry. In this case, the marketo.com SPF record includes a number of other, different SPF records.  (include:_spf.salesforce.com include:spf.protection.outlook.com include:mktomail.com include:email.influitive.com include:stspg-customer.com) All entries in the “included” entries are now considered to be part of the marketo.com record. A great tool to see all nested records in an SPF record is the DMARCIAN SPF Surveyor. Caveat: This approach has limits There is a limit of 10 additional “include:” records in an SPF record. The "include", "a", "mx", "ptr", and "exists" mechanisms as well as the "redirect" modifier count against this limit of 10, but the "all", "ip4", and "ip6" mechanisms do not count against this limit. Also remember, when you “include:” a record in your SPF record, then your record now includes all mechanisms in the “include:” record.  So if your SPF record has 1 “include:”, but the SPF record you are including has 10 already, then your record will now have 11 and will break! Null Records in the SPF Record A record that is NULL or does not exist will break an SPF record.  This means be extra careful about typos in your record.  If you “include:” a domain that doesn’t exist, this will break your record. Repetitive Records in the SPF Record In order to prevent against unnecessary processing that can cause mail systems to slow down repeated mechanisms aren’t allowed.  There is a MAX of 2 repeated look ups in an SPF record.  More than that and the record will break.  This prevents SPF records from being used in Denial of Service style attacks. If we have learned anything at Marketo over the years it is that DNS for email is hard!  We have experts on our team who can help unravel the most complicated SPF records.  Raise your hand and let us know if you need help. ... View more

If you're setting up Marketo you're no doubt familiar with how to set up SPF and DKIM to ensure higher deliverability rates, but did you know that there is a limit of 255 characters in an DNS entry, and you'd have to span DNS entries to have an SPF entry longer than 255? so, if you have a TON of domains you want to include in your SPF.. how do you do that? Excellent Question. In short you're able to nest them within the top level domain. I've enclosed an example below, blurring the domains and IP's to protect the innocent. In order to see if SPF is set up, head over to www.mxtoolbox.com and type in the domain. For example, type in "Marketo.com" and you'll see that Marketo allows MArketo to send emails on behalf of Marketo. Not surpriusing, Marketo has always been a great customer of Marketo. Again, I'm blurring everything not related to the discussion at hand. So, here's how it looks when you NEST entries. the top level SPF entry. In this case, the mktomail.com include is in spf-c, so if we run the MXTools query on _spf-c.company.com (name redacted!) youll see this Meaning that all the sub entries will be added to the list of SPF entries. ... View more

That's a mouthful isnt it? In the spirit of "a picture is worth a thousand words", I've recorded a video walking you through how to do this in Boomi. Its tricky only in that you have to tweak the XML that Boomi finds in the Marketo WSDL. You can see the video here! Video Link : 1351 Fig 1 - the completed Opportunity and Opportunity Person Role Process What I really wanted to share here is a bit more about the XML format you're creating in the video. The following are the XML's being created by Boomi with the recommended configuration. <ns1:Opportunity xmlns:ns1=" http://www.marketo.com/mktows/ ">    <externalKey>       <name>oppKey</name>       <value>1001</value>    </externalKey>    <attribList>       <IsClosed>1</IsClosed>       <IsWon>1</IsWon>       <Name>Opportunity from Boomi</Name>       <oppKey>1001</oppKey>    </attribList> </ns1:Opportunity> Fig 2 - Opportunity Upsert XML <ns1:OpportunityPersonRole xmlns:ns1=" http://www.marketo.com/mktows/ ">    <attribList>       <IsPrimary>1</IsPrimary>       <Role>Marketing Manager</Role>    </attribList>    <associationList>       <mObjAssociation>          <mObjType>Opportunity</mObjType>          <externalKey>             <name>oppKey</name>             <value>1001</value>          </externalKey>       </mObjAssociation>       <mObjAssociation>          <mObjType>Lead</mObjType>          <externalKey>             <name>leadKey</name>             <value>89001</value>          </externalKey>       </mObjAssociation>    </associationList> </ns1:OpportunityPersonRole> Fig 3 - Opportunity Person Role XML Fig 4 - The XML Setup as seen in SOAPUI So, you can see where the structure of the XML comes from. Cool right? ... View more

Quite a few people have asked recently what a good use case is for using RTP's User Context API, Document here on the developer site. At a high level, what the User Context API allows us to do is store bits of information about a (typically anonymous) user within RTP, and then leverage those bits of information for segmentation. Obviously RTP's set of data about an anonymous user is rich, but there could be custom items we might not return. Here are some examples: RTP doesn't return longitude and latitude, but other 3rd party products might. If that's important in the context of a campiagn, you could choose to store those in two "custom" variables RTP doesnt know if an anonymous visitor is a customer... but other 3rd party products might. In that case, you could use that 3rd parts's API to get that information, store it in a custom variable.. then segment on it. When you're building your segment, here's how you use all this information Step 1: Look under API for User Context API Step 2: Drag over User Context API Step 3: Choose the custom variable you're storing your data in Step 4: Choose the value in the fiedl you want to segment on! You can then create a campaign based on this segment and serve up the right content to the right people! The User Context API is not on by default.. so talk to your support rep to get that enabled. Its important to note that the custom fields in RTP are actually named "Custom 1" - "Custom 5". Whatever data you get from your other source is just placed in a variable with that name, then used. ... View more

I freely admit this is an esoteric topic, but trust me when I tell you when you need to use it, it's best not to mess it up. The use case is as follows.. suppose you have customers that might exist in some home grown external system with a unique PID (Person ID) that is not the marketo ID, and your business depends on that being unique. In addition, imagine some people in your database may not have emails (I know, I know, but this happens). Now imagine that you can have duplicate emails in Marketo.. but youll never have a duplicate PID. An example would be when a caretake signs up for an account for someone else (Im leaving that intentionally vague). In such a case you need to upsert data into Marketo, but you may or may not have email.. and you definitely dont have a Marketo ID. If you're using REST, its not a problem as you can specify a non email dedupe field.. but if you're using SOAP.. its not that simple. In that case you might consider using the "Foreign System ID". Wait.. the Foreign System what? It's true, this exists, and its documented, if rarely used, and its important you use it correctly. In the above use case you'd use the following two versions of an input XML to upsert a lead into Marketo. In my humble opinion, Case 1 is more insteresting... because you're passing in the MarketoID and UPDATING the Foreign System Person ID. Case 1: NO Email <soapenv:Envelope xmlns:soapenv=" http://schemas.xmlsoap.org/soap/envelope/ " xmlns:mkt=" http://www.marketo.com/mktows/ ">    <soapenv:Header>       <mkt:AuthenticationHeader>          <mktowsUserId>${#TestCase#userid}</mktowsUserId>          <requestSignature>${#TestCase#signature}</requestSignature>          <requestTimestamp>${#TestCase#timestamp}</requestTimestamp>       </mkt:AuthenticationHeader>    </soapenv:Header>    <soapenv:Body>       <mkt:paramsSyncMultipleLeads>          <leadRecordList>             <leadRecord>                <Id>3767415</Id>                <ForeignSysPersonId>DEF1234</ForeignSysPersonId>                <ForeignSysType>CUSTOM</ForeignSysType>                <leadAttributeList>                   <attribute>                      <attrName>FirstName</attrName>                      <attrValue>Ben</attrValue>                   </attribute>                </leadAttributeList>             </leadRecord>          </leadRecordList>          <dedupEnabled>TRUE</dedupEnabled>       </mkt:paramsSyncMultipleLeads>    </soapenv:Body> </soapenv:Envelope> Case 2: With Email <soapenv:Envelope xmlns:soapenv=" http://schemas.xmlsoap.org/soap/envelope/ " xmlns:mkt=" http://www.marketo.com/mktows/ ">    <soapenv:Header>       <mkt:AuthenticationHeader>          <mktowsUserId>${#TestCase#userid}</mktowsUserId>          <requestSignature>${#TestCase#signature}</requestSignature>          <requestTimestamp>${#TestCase#timestamp}</requestTimestamp>       </mkt:AuthenticationHeader>    </soapenv:Header>    <soapenv:Body>       <mkt:paramsSyncMultipleLeads>          <leadRecordList>             <leadRecord>                <ForeignSysPersonId>ABC123</ForeignSysPersonId>                <ForeignSysType>CUSTOM</ForeignSysType>                <leadAttributeList>                   <attribute>                      <attrName>FirstName</attrName>                      <attrValue>Alicia</attrValue>                   </attribute>                   <attribute>                      <attrName>Email</attrName>                      <attrValue> Alicia@Test.com </attrValue>                   </attribute>                </leadAttributeList>             </leadRecord>          </leadRecordList>          <dedupEnabled>TRUE</dedupEnabled>       </mkt:paramsSyncMultipleLeads>    </soapenv:Body> </soapenv:Envelope> The key it turns out is the ForeignSystemType. In order to properly upsert the lead, you NEED to tell marketo what the ForeignSystemPersonID is.. as well as the ForeignSystemType! ... View more