How to pass an identifier to marketo activity as part of a page visit

[milricks]

In Marketo,  all these web page visits are   recorded in the visit_web_page activity. This acitivity also has a time that is associated with each activity.

We are also tracking all the page activity via a separate home grown system that is similar to Google Analytics. Now, I need to associate the activity captured by marketo with the activity captured by this system. However, the dateTime between Marketo and the home grown system are not in sync. As a result I am not able to associate them 1:1.

I am trying to see if I can generate a unique id somewhere and pass it to marketo as well as the home grown analytics platform so that it makes it easier for me to join the two data source 1:1. 

[SanfordWhiteman]

You can’t append data to the built-in Munchkin events. Why not append the Marketo cookie (_mkto_trk) to your homegrown system? It’s already guaranteed unique, you don’t need anything else.

[milricks]

Hi @SanfordWhiteman 

We are already sending the munchkin cookie to the home grown system but the cookie provides uniqueness for a user but I am looking for uniqueness at the event level(since one user can have multiple events). Only then will I be able to deterministically associate the events between the two systems

[milricks]

Hi @SanfordWhiteman 
I came across this page and it appears that we can send custom attributes as part of the payload for web visit activity. Am I understanding this correctly? Basically, I am looking to take an attribute value that is stored in the browsers storage and send it as part of the web visit activity.

https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/javascriptapi/leadtracking/api-...

[SanfordWhiteman · Accepted solution]

Yes, you can programmatically send additional Visit Web Page and Click Link activities with a custom URL structure (I’ve written about this in the past).

But you can’t mark up the automatic Visit Web Page and Click Link activities — the ones that are sent/attached when Munchkin initializes.

If you send additional activities, you’ll have more flexibility if you embed information in the pathname, not the querystring. This is because Marketo doesn’t consider the querystring to be part of the {{trigger.web page}} in case you want to post-process that token. In other words, use a structure like this:

/additionalEvents/localData/variableName/XYZ123

Still, Munchkin isn’t a general purpose event collector. It has the scalability of course, but not the back-end programmability and reporting.