Serving up dynamic content based on a person's previously viewed content | Community
Skip to main content
Brittany_McDona
New Participant
June 4, 2021
Solved

Serving up dynamic content based on a person's previously viewed content

  • June 4, 2021
  • 1 reply
  • 2012 views

Is it possible to use dynamic content to serve up a different image/blog based on whether or not a contact has already viewed and/or been served that blog elsewhere? So if the user has viewed Blog A but not Blog B, display Blog B. If user had viewed Blog B but not Blog C, serve Blog C etc. And then I'd probably need an option for it they've viewed all of the possible blogs already, like driving them to the website or something. 

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

You can create a Textarea field — as this is easier than creating an ever-growing set of individual Datetime fields — and append the {{trigger.web page}} and {{system.datetime}} to the value each time they view something interesting.

 

Then use that field in segments in a segmentation, which in turn can be used with Dynamic Content.

 

However, this is going to be supremely hard to manage once you have to manage more than, say, 6 different combinations. At that point you would be better off skipping the segmentation and outputting the {{lead.token}} into the page, then using JavaScript to show/hide content.

 

Marketo's Web Personalization product, or one of the competitive standalone products, would be a more scalable option.

1 reply

SanfordWhiteman
SanfordWhitemanAccepted solution
New Participant
June 4, 2021

You can create a Textarea field — as this is easier than creating an ever-growing set of individual Datetime fields — and append the {{trigger.web page}} and {{system.datetime}} to the value each time they view something interesting.

 

Then use that field in segments in a segmentation, which in turn can be used with Dynamic Content.

 

However, this is going to be supremely hard to manage once you have to manage more than, say, 6 different combinations. At that point you would be better off skipping the segmentation and outputting the {{lead.token}} into the page, then using JavaScript to show/hide content.

 

Marketo's Web Personalization product, or one of the competitive standalone products, would be a more scalable option.

Brittany_McDona
New Participant
June 14, 2021

Thank you, this makes sense. Sounds like it may be too hard to manage long-term, but good to know how we could do it.