Skip navigation
All Places > Products > Blog > 2016 > September

A question from top Marketo user GM in this post led to an interesting, even disturbing, hour of troubleshooting.  Finally, I've gotten around to writing it up.


When Munchkin sees a 2-letter TLD like .io or .ly, it makes a bad guess about the proper domainLevel — the domain at which it sets the vital web activity tracking cookie.  Using TLDs like .au as a model, the code incorrectly assumes that you cannot have registered a domain directly under the TLD and automatically sets {domainLevel: 3}.

Read the full post on TEKNKL :: Blog →

This post will address how you can display progressive web campaigns (with Web Personalization (RTP)), by changing the campaign based on the web visitor's previous visit and what they viewed. It's like nurturing for a web visitor, if the visitor saw Campaign A, then next time (separate session/visit) they come to the website show them Campaign B, and then the next visit after that show them Campaign C (based on seeing Web Campaign B and Campaign A).


One way to do this in Web Personalization (RTP), is segmenting based on the number of visit. For a 1st visit, show campaign A and then another segment for a 2nd visit, showing Campaign B, etc...


However, this does not completely satisfy the case above, as the user may not have seen a campaign to "move" onto seeing the next campaign or the visitor may not be coming in for their 1st or 2nd visit, they may be a 10th time visitor.


So, how to create a web nurturing campaign based on previous visit history and what campaigns the web visitor saw in previous visitors?


The answer: Using the User Context API in Segmentation.


Additional Info

See more on the User context API Here. "The User Context API exposes user and visitor level data across multiple sessions to enable advanced personalization capability leveraging historical user behavior and data."


NOTE: You need to request from Support to enable the User Context API for your Web Personalization (RTP) Account.


Make sure you read how to locate the Web Campaign ID.


Assuming we want to show the web visitor, the following campaigns in this order for each of their visits:


  1. Campaign A (id = 111)
  2. Campaign B (id = 222)
  3. Campaign C (id = 333)


In Web Personalization > Segmentation, create the following Segments:


Drag and Drop the User Context API, Select "Campaigns - Viewed" and insert the Campaign ID




Segment: WHERE User Context API "Campaigns - Viewed" IS NOT "111"




Segment: WHERE User Context API "Campaigns - Viewed" IS "111" AND IS NOT "222"




Segment: WHERE User Context API "Campaigns - Viewed" IS "222" AND IS NOT "333"


This post shows how to locate the Web Campaign ID. The Campaign ID is usually used for Javascript API use cases.

In the Web Personalization (RTP) app, Go to Web Campaigns, hover over the Campaign Name to locate the Campaign ID in brackets.


Are you wondering what content or places, or even people are getting the most attention in Community? Here are some metrics that will be updated quarterly, for the previous quarter, to let the Nation know what our most popular areas are so you can check them out!


Updated Sept 2016 for Q3


Top 5 Content


Top 5 Places



The specified item was not found.91,703
The specified item was not found.19,682
Champion Program18,122


Top 5 Marketo Recommended Places




Questions : Average Response Time


  • 96% questions responded to
  • 26% questions received helpful answer*
  • 17% questions received correct answer*

*Note this is a user behavior so is not a clear indication of questions that were in fact helpful or correctly answered. It shows how many people manually marked questions as helpful or correct. The more you do this the more everyone learns!


User Adoption & Participation


Avg. of 10,200 visitors to the site

15% of visitors are engaging


Top 5 Users

UserPoints (this quarter)Total PointsFollowers
Sanford Whiteman3,197104,949243
Grégoire Michel2,981137,340278
Josh Hill1,799264,596294
Dory Viscogliosi1,13377,37499
Geoffrey Krajeski97019,50957

Your #1 requested item in the community is here! Audit trail gives you real-time visibility into what users and admins are doing within your subscription! It will provide value to everyone, but will be especially useful for customers who have large teams using Marketo and for those with "creative" users.


With audit trail, you can answer many questions such as:

  • What happened to this asset or setting, and who last updated it?
  • What has user X been up to?
  • Who is logging into our account?


Audit trail provides many benefits!  Lets walk through a few of them:

  • Create accountability. The fact that user (and admin) actions are being audited, will create a sense of accountability across your teams...slightly big brotherish!
  • Save time. The reality is, unexpected things happen when using Marketo. With audit trail, you can quickly pinpoint what happened and apply corrective action on your own. This will save time from having to call our support team!
  • Support your teams. Perhaps you have a set of newbies who are ramping up using Marketo. Audit trail can show you what they’ve been up to and perhaps who needs some guidance. If you comp your teams based on what they create in Marketo, audit trail can provide that information! You can filter by a specific user then reward them!
  • Keep a close eye on security! Maybe somebody left your company and you want to see everything they did prior to their departure. If that person has an audit history it will show up for you to review. Also, if you wear a security hat, then you can see who is logging into your system, even that person who left the company (hopefully this doesn’t happen).


Now, you're probably wondering what we actually audit. It's all documented here! Keep in mind, audit trail is an evolving feature. We are auditing the most important elements and have more being added in our fall release. If you have a particular auditing need, please reach out to me or start a discussion. Also note, that audit trail tracking officially began on Sept 14, 2016. This means, when you view your audit trail, the farthest back you can see is on that date. If something is missing or you need information about an action that occurred prior to that date, then you can contact support as they have more history available to them (we just can't expose it in this new framework)

I really hope you find value in audit trail! I'm excited to finally see it come to life and thank each of you for your contributions.



Christina Fuentealba

Lead product manager

Marketo had a very exciting week last week with our much anticipated Marketo Account Based Marketing Event. 350-plus customers, prospects, partners, influencers, analysts, and media in a packed room at the Four Seasons San Francisco, we unveiled Marketo ABM in a whole new way. Our customers were inspired by what they saw and even more excited about the potential that Marketo ABM will deliver for their business. #MarketoABM was even trending at the top in San Francisco! To watch the recording of this exciting live event, click here.


The event was live streamed to the Marketing Nation globally. A huge thank you to the 15 Marketo User Groups that held watch parties to celebrate the launch in cities such as Atlanta, Chicago, Cleveland, Dallas, Houston, New York City, and Vancouver, among others. Over 90 minutes, we unveiled our new offering, hosted a CMO panel on ABM, and capstoned the day with a discussion with Andre Iguodala of the Golden State Warriors who spoke on the essentials for building a championship team.


If you haven’t already, I strongly encourage you to join our ABM Virtual User Group (simply click follow in the top right corner) where you can find everything Marketo ABM. Ask questions about our offering or about ABM in general and as our product is released and rolled out, this is the place you can get first hand customer stories, successes, discuss challenges, and stay up to date with upcoming ABM webinars and webinars on demand!


We look forward to engaging with you in the ABM group soon.

Filter Blog

By date: By tag: