Complicated Segment Question | Adobe Higher Education
Skip to main content
D
dlynch80
Level 2
July 26, 2023
Beantwortet

Complicated Segment Question

  • July 26, 2023
  • 2 Antworten
  • 2289 Ansichten

I believe what I'm trying to accomplish is possible, but I'm having trouble setting it up in Workspace.  What I want is for the segment to look back from today minus 60 through 120 days to identify a population of customers that had a specific payment method.  Once the population is identified, I want to look back the past 60 days on that same population to see how it has fared in the last 60-days.  The tricky part is identifying the population in one date range (minus 60-120 days from today) and then showing metrics for that population in another date range (minus 1-60 days from today) within the same segment.

Dieses Thema wurde für Antworten geschlossen.
Beste Antwort von Jennifer_Dungan

I would suggest using 2 segments not one, particularly since you are trying to compare the 2 time frames... 

 

Or you can have one segment for the specific payment method, then just have 2 custom date ranges for "last 60 days" vs "120-60 days ago"....

 

The Date Ranges should be easy:

and

 

You can use these date ranges in your columns, or as your Breakdown:

 

 

And then use one genetic "Payment Method X" segment.. you you can add these data ranges into two separate Payment Method segments "Payment Method X - Last 60 Days" and "Payment Method X - 120 - 60 Days Ago"

 

 

 

 

Why do you need both ranges in a single segment? That would be no different than just pulling 120 Days ago to Yesterday... the segment will only return one group of data... 

2 Antworten

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe ChampionAntwort
Community Advisor and Adobe Champion
July 26, 2023

I would suggest using 2 segments not one, particularly since you are trying to compare the 2 time frames... 

 

Or you can have one segment for the specific payment method, then just have 2 custom date ranges for "last 60 days" vs "120-60 days ago"....

 

The Date Ranges should be easy:

and

 

You can use these date ranges in your columns, or as your Breakdown:

 

 

And then use one genetic "Payment Method X" segment.. you you can add these data ranges into two separate Payment Method segments "Payment Method X - Last 60 Days" and "Payment Method X - 120 - 60 Days Ago"

 

 

 

 

Why do you need both ranges in a single segment? That would be no different than just pulling 120 Days ago to Yesterday... the segment will only return one group of data... 

    D
    dlynch80Autor
    Level 2
    July 27, 2023

    Thank you for the information.  My issue is that I'm trying to identify a list of customers in the "Identification Period" (Days 61-121) less today and then see their activity in the the "Performance Period" (Last 60 Days).  That's the distinction.  I don't necessarily care about their performance in the "Identification Period", just the list of customers.  I may not be approaching it right with the one segment, but the above is what I'm trying to accomplish.

    D
    dlynch80Autor
    Level 2
    July 28, 2023

    Unless for some reason your "Payment Method" is set to a Visitor Level expiry, which really wouldn't make any sense... this segment will only return users with that specific payment method within the specified time frame (Last 60 Days).

     

    Even IF they had purchases in the 120-60 range, those will not trigger the rule above, unless your Payment Method is configured to maintain its value...

     

    If it is, you can throw another AND clause with an "Instance of Payment Method exists" into the Performance Period.

     

     

    Your definition of what you want isn't very clear... I gave you what I thought you were looking for based on your messages

     

    - Users with Purchase Method X IN Performance Period

    - The above Users must also have come to the site in the preceding period

     

    The Users may or may not have made a purchase in 120-60 Days, because we didn't add any logic there to care if they did.. the only thing the segment cared about was purchases IN the last 60 Days. (again, based on the assumption that Purchase Method is a HIT level dimension... which it should be, why would you associate a purchase type to all future visits?)

     

    Is this what you are looking for, because your most recent message sounds completely different...

    Then the prior 60-day performance period would give me all from that cohort, even those who had no orders in the performance period. 

     

    So you don't care if these uses have made a purchase in your performance period?

    Are you just looking for users that came to you site (regardless of their actions) in both last 60 days AND 120-60 days?

     

    If you just want to identify users who came in both periods, then just look for:

    [120-60 Days AND Visits exists]

    AND

    [60 Days AND Visits exists]


    I apologize for not being as clear as I should have been.  I'm trying to put into words what is in my head, but it may not make sense to everyone.  I thought it would be easier to show a graphic of what I'm trying to do:

     

     

    yuhuisg
    Community Advisor
    yuhuisgCommunity Advisor
    Community Advisor
    July 28, 2023

    Instead of using segments, would a Cohort Table help you? I assume that you want your segment for the purpose of running a report, not for activation (i.e. by publishing the segment to Experience Cloud for use in other Adobe products).

    The only thing about the Cohort Table's results that you won't like is that you start from your end point, i.e. 60+60 days ago, and see what percentage of that old cohort has been retained up to today.

      D
      dlynch80Autor
      Level 2
      July 28, 2023

      Thanks for the idea and I did try that, but some metrics were not available with that method, such as conversion rate, which is really what I'm interested in seeing.

      Allgemeine NutzungsbedingungenAccessibility statement

      Loading footer...