SOLVED

Re: Marketo Outlook add-in: Issue tracking correct ip address tracking sender's activity vs recipient's

Go to solution
Augie_Kuron
Level 2

Marketo Outlook add-in: Issue tracking correct ip address tracking sender's activity vs recipient's

I recently started using Marketo's Outlook add-in feature to help track if lead's have opened or clicked in emails that I've sent.  The only problem I seem to be having, and this is only in a few rare instances, is that some of the leads are tracking my web activity and not that of the recipient of the email.

For example:  I sent out a one-off email to a lead using the 'send and track' button from outlook.  The lead responded and a couple more emails were sent back and forth.  A few days after communication had ceased I noticed this lead had a high amount of clicking and web-page visits- Though I quickly discovered that the activity it was tracking was my own and not the activity of the lead's.  

I've had similar issues for a few other leads as well.  Does anyone know why this may be happening and how to prevent it?
Tags (1)
1 ACCEPTED SOLUTION

Accepted Solutions
Anonymous
Not applicable

Re: Marketo Outlook add-in: Issue tracking correct ip address tracking sender's activity vs recipient's

It sounds like during your email exchange, you clicked on one of the links in the reply message/the message in the Sent folder. Which in turn cookied you as that lead, so that you would be tracked as that person. 

Clearing out your cookie should fix the problem; There is no real way to prevent this from happening, you'd need to be wary of what links you click in your exchange of messages.

View solution in original post

1 REPLY 1
Anonymous
Not applicable

Re: Marketo Outlook add-in: Issue tracking correct ip address tracking sender's activity vs recipient's

It sounds like during your email exchange, you clicked on one of the links in the reply message/the message in the Sent folder. Which in turn cookied you as that lead, so that you would be tracked as that person. 

Clearing out your cookie should fix the problem; There is no real way to prevent this from happening, you'd need to be wary of what links you click in your exchange of messages.