2 Replies Latest reply on Feb 28, 2018 11:46 AM by Jim Orfan

    Capturing time series data

    Jim Orfan

      Hello,

       

      I'm new to Marketo and have a question for the community. We have a status segment we use in our email campaigns.  For example we'll send out emails to contacts who are "active", "inactive", or "lapsed".  We'll use smart lists for each segment.  Sometimes they'll get the same creative sometimes its different.

       

      We want to capture the status a contact was in at the time the email was sent and report on it in a scaleable manner. I understand that if we had a campaign and sent an email by segment we would have email delivery metrics by that segment but it seems like it would be a challenge when trying to scale that for many complex campaigns. 

       

      Does anyone have any experience capturing point-in-time data in a contact history file that include a custom field such as "status" in Marketo so that this could be done?  Our attribution is often inferred (e.g., sent email, clicked link, made appointment afterwards) so we need more than just capturing the query string parameters. 

       

      Curious to see if anyone else has faced this challenge (without getting overly detailed) and what kind of solutions may have been implemented.

       

      Thanks,

      Jim

        • Re: Capturing time series data
          Grégoire Michel

          Hi Jim,

           

          The best way to do this is to use a long tex field and stored the timestamps, email send and status in a json format.

           

          Create a field and call it for instance "Historical email send status".

           

          Then create a smart campaign on trigger "is send email". In the flow, add a "data value change" flow step. Field is "Historical email send status". New value is

           

          {"DateTime":"{{system.DateTime}}","Email Sent":"{{trigger.Name}}","Status":"{{lead.Status}}"},{{Lead.Historical email send status}}.

           

          For the status, you might have to store the segment name is a "status" field prior to being able to use it.

           

          -Greg