Webpage Host attribute missing from getLeadActivity | Community
Skip to main content
A
Anonymous
June 26, 2014
Question

Webpage Host attribute missing from getLeadActivity

  • June 26, 2014
  • 8 replies
  • 1719 views
Using the SOAP API to get lead activity (getLeadActivity), the Webpage Host attribute recently disappeared. We need this attribute to correctly resolve which web page a lead visited.  

Can you shed some light on why this attribute disappeared in the response, and how we can get the hostname for an activity?
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

8 replies

A
Anonymous
June 26, 2014
Could you please post the activity log before this change and after? 
A
Anonymous
June 27, 2014
See below.  The part in bold is no longer being sent over.

Before: 

<activityRecord>
<id>22821293</id>
<activityDateTime>2014-04-07T23:48:15-05:00</activityDateTime>
<activityType>Visit Webpage</activityType>
<mktgAssetName>
www.example.com/resources/ebooks/rockstar/
</mktgAssetName>
<activityAttributes>
<attribute>
<attrName>Webpage ID</attrName>
<attrType xsi:nil="true"/>
<attrValue>15920</attrValue>
</attribute>
<attribute>
<attrName>Webpage Host</attrName>
<attrType xsi:nil="true"/>
<attrValue>
www.example.com
</attrValue>
</attribute>
<attribute>
<attrName>Webpage URL</attrName>
<attrType xsi:nil="true"/>
<attrValue>
/resources/ebooks/rockstar/
</attrValue>
</attribute>
<attribute>
<attrName>Query Parameters</attrName>
<attrType xsi:nil="true"/>
<attrValue>
LDT=Ebook&LD=Rockstar eBook
</attrValue>
</attribute>
<attribute>
<attrName>Referrer URL</attrName>
<attrType xsi:nil="true"/>
<attrValue>
http://socialmediatoday.com/
</attrValue>
</attribute>
<attribute>
<attrName>Client IP Address</attrName>
<attrType xsi:nil="true"/>
<attrValue>198.185.18.207</attrValue>
</attribute>
<attribute>
<attrName>User Agent</attrName>
<attrType xsi:nil="true"/>
<attrValue>
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:28.0) Gecko/20100101 Firefox/28.0
</attrValue>
</attribute>
<attribute>
<attrName>Message Id</attrName>
<attrType xsi:nil="true"/>
<attrValue>1545637</attrValue>
</attribute>
<attribute>
<attrName>Created At</attrName>
<attrType xsi:nil="true"/>
<attrValue>2014-04-07 23:48:15</attrValue>
</attribute>
<attribute>
<attrName>Lead ID</attrName>
<attrType xsi:nil="true"/>
<attrValue>1398486</attrValue>
</attribute>
</activityAttributes>
<campaign/>
<personName xsi:nil="true"/>
<mktPersonId>1383012</mktPersonId>
<foreignSysId xsi:nil="true"/>
<orgName xsi:nil="true"/>
<foreignSysOrgId xsi:nil="true"/>
</activityRecord>

Atfter:
<activityRecord>
<id>22821293</id>
<activityDateTime>2014-04-07T23:48:15-05:00</activityDateTime>
<activityType>Visit Webpage</activityType>
<mktgAssetName>
www.example.com/resources/ebooks/rockstar/
</mktgAssetName>
<activityAttributes>
<attribute>
<attrName>Webpage ID</attrName>
<attrType xsi:nil="true"/>
<attrValue>15920</attrValue>
</attribute>
<attribute>
<attrName>Webpage URL</attrName>
<attrType xsi:nil="true"/>
<attrValue>
/resources/ebooks/rockstar/
</attrValue>
</attribute>
<attribute>
<attrName>Query Parameters</attrName>
<attrType xsi:nil="true"/>
<attrValue>
LDT=Ebook&LD=Rockstar eBook
</attrValue>
</attribute>
<attribute>
<attrName>Referrer URL</attrName>
<attrType xsi:nil="true"/>
<attrValue>
http://socialmediatoday.com/
</attrValue>
</attribute>
<attribute>
<attrName>Client IP Address</attrName>
<attrType xsi:nil="true"/>
<attrValue>198.185.18.207</attrValue>
</attribute>
<attribute>
<attrName>User Agent</attrName>
<attrType xsi:nil="true"/>
<attrValue>
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:28.0) Gecko/20100101 Firefox/28.0
</attrValue>
</attribute>
<attribute>
<attrName>Message Id</attrName>
<attrType xsi:nil="true"/>
<attrValue>1545637</attrValue>
</attribute>
<attribute>
<attrName>Created At</attrName>
<attrType xsi:nil="true"/>
<attrValue>2014-04-07 23:48:15</attrValue>
</attribute>
<attribute>
<attrName>Lead ID</attrName>
<attrType xsi:nil="true"/>
<attrValue>1398486</attrValue>
</attribute>
</activityAttributes>
<campaign/>
<personName xsi:nil="true"/>
<mktPersonId>1383012</mktPersonId>
<foreignSysId xsi:nil="true"/>
<orgName xsi:nil="true"/>
<foreignSysOrgId xsi:nil="true"/>
</activityRecord>
 

A
Anonymous
August 20, 2014
Any resolution on this?
A
Anonymous
August 20, 2014
Could you please open a support ticket with a link to this thread?

https://community.marketo.com/case_create_page
A
Anonymous
August 20, 2014
Seems like I am getting the runaround here.  First I emailed member of the partner support staff, who told me to create a forum post, and now two months later, I am told to file a case.
 
I'll do it, to get the issue solved, but it's annoying to say the lease.
 
Seems contrary to what you're preaching on own blog which I read from time to time:
http://murtza.org/takeaways-from-developer-evangelist-meetup/
 
First, if a person emails you a question about your API, then there are probably other people facing the same issue. First answer them via email. Then make the solution available publicly in your documentation.
A
Anonymous
August 20, 2014
I am sorry that this is taking a long time to get resolved. I understand why it is frustrating, so I'll give you more context from our side.

I talked with the product team, and they are not aware of any change that would be causing this. So in these cases, we have to go through our support channel to figure out if this is limited to your Marketo instance or a more general bug. Two months ago, partners could not file support tickets. We recently enabled this. I hope this make sense? 
A
Anonymous
August 21, 2014
Thanks for the clarification, Murtza.

1. This is not limited to our Marketo instance, we are seeing this across multiple instances in several companies.  Happy to provide more data in a support ticket if needed.

2. Makes sense from your internal standpoint. But for an outside developer who is not privy to your interal workings, the end result appears to be a protracted timeline to getting these issues resolved.

Look forward to getting this resolved through the support channel.
A
Anonymous
September 4, 2014
Thanks a lot for the attention to this bug, and for fixing it.
Terms & ConditionsAccessibility statement

Loading footer...