Hack around 90 days constraint. Opened Emails + Page Views | Community
Skip to main content
Simon_Lessard
Simon_Lessard
Level 3
June 28, 2016
Question

Hack around 90 days constraint. Opened Emails + Page Views

  • June 28, 2016
  • 1 reply
  • 1355 views

Hi,

I have a database with significant users who haven't opened any email nor visited any Web page in more than 2 years. I'd need to identify them in order to treat them accordingly. I got to support to extend the 90 days constraint on related filters but since that operation doesn't de-archive information and is a going forward process, it's a no go.

I'd really like to have your input guys on a way to hack around this situation. I have RCE enabled if it helps.

Regards,

Simon

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

1 reply

SanfordWhiteman
SanfordWhiteman
Level 10
June 28, 2016

You'd would need to have the data (or the proof of absence of data) to act with confidence.

Without actual activity logs, you could do some very loose information gathering by checking (using the API) the cookies associated with your leads. If the timestamp in the cookie name is within the past 2 years, then you for sure know they have visited within the past 2 years.  However, that only lets you perhaps prioritize those leads.  It doesn't let you delete other leads, because someone with an even older cookie may have visited your site > 90 days but < 2 years.

Simon_Lessard
Simon_LessardAuthor
Level 3
June 29, 2016

As you say, it's a bit too loose for the context.

While I dug a little deeper, I've found an old reply from Mark Townsend​, in an unrelated thread mentioning something about taking members of lead scoring campaigns as they gather this kind of humans. Basically, those campaigns apply score to any opened email and visited webpages. I'm lucky enough that those campaigns are active for the past 12 months in our instance. I'm going to use this data and apply a more custom "going forward process".

Thanks for your reply

Terms & ConditionsAccessibility statement

Loading footer...