How to use ID stitching option and Merge method? | Adobe Higher Education
Skip to main content
Luca_Lattarini
Luca_Lattarini
Level 9
September 18, 2022
Beantwortet

How to use ID stitching option and Merge method?

  • September 18, 2022
  • 3 Antworten
  • 3021 Ansichten

Hi All,

 

I m working on merge policy and I would like to understand when we need to use ID Stitching None OR Private Graph and when to use  merge method Dataset precedence OR Timestamp ordered, mostly how to combine them. Assuming that I have this use case:

1) I want to create 5 segments that qualifies profile from all of my dataset that are enabled for profile. These segments will be used for advertsing destinations

2) I want to create 1 segment that qualifies profile from DS1, DS2,DS3 that are enabled for profile. This segment will be used for email marketing/survery destination.

Any suggestion?

Thanks

Dieses Thema wurde für Antworten geschlossen.
Beste Antwort von ChetanyaJain-1

@luca_lattarini,

 

I would look at the data, its quality, and which source is sending it to decide the right merge policy to pick. The intention should be to get the right/best data to build the 360-view of profile for the activation. I would not look for activation/segmentation to decide which merge policy to pick.

 

If data is coming from 3rd party then the preference will be to pick 1st party data and in this case, dataset precedence is the best choice. For other cases, I would go with time preference.

 

Regards,

Chetanya

3 Antworten

V
Vikashyadav
Level 3
September 18, 2022

Hi @luca_lattarini,

 1] ID Stitching None : Multiple profile fragments are not stitched together to form single view of the customer though profile fragments may belong to same customer. This could result having multiple audience for same profile during segmentation.

2] ID Stitching Private Graph : Multiple profile fragments are stitched together to form single view of the customer. This could result only one audience for same profile during segmentation.

In following document, these concepts are explained in more detail.

https://experienceleague.adobe.com/docs/experience-platform/profile/merge-policies/overview.html?lang=en#dataset-precedence

    ChetanyaJain-1
    Community Advisor
    ChetanyaJain-1Community AdvisorAntwort
    Community Advisor
    September 18, 2022

    @luca_lattarini,

     

    I would look at the data, its quality, and which source is sending it to decide the right merge policy to pick. The intention should be to get the right/best data to build the 360-view of profile for the activation. I would not look for activation/segmentation to decide which merge policy to pick.

     

    If data is coming from 3rd party then the preference will be to pick 1st party data and in this case, dataset precedence is the best choice. For other cases, I would go with time preference.

     

    Regards,

    Chetanya

      Luca_Lattarini
      Luca_LattariniAutor
      Level 9
      September 18, 2022

      @chetanyajain-1 @vikashyadav Thanks guy for your suggestion. 

      Assuming that i want to create a segment by using qualities profile data from ALL datasets that have been enable for a profile. 

      If I use ID Stitching None method and Data precedence with ALL my datasets ordered by quality data (First 1st party data and last 3rd Party data).

      Am I able to have a good qualities of segment and use ALL datasets OR it is more accurate Stitching Private Grapgh method and Data precedence?

       

      ChetanyaJain-1
      Community Advisor
      ChetanyaJain-1Community Advisor
      Community Advisor
      September 18, 2022

      @luca_lattarini This is tricky and will depend from case to case and is heavily dependent on the data that is flowing in. Always do data profiling before you ingest and gain better confidence.

       

      N
      navin_kumar0601
      Level 4
      May 25, 2023

      So @luca_lattarini my POV is u should use id stitching : none, given its for Ad targeting. ie. topline growth, and not nearly an email campaign.

      Allgemeine NutzungsbedingungenAccessibility statement

      Loading footer...