Why do I see multiple profiles in a single request?

Forum|Forum|2 years ago
December 22, 2023
1 reply
1945 views

I am trying to send an audience to a webhook to test the output of my custom created DSDK, but in the output I see several duplicate profiles and some of those occur in a single request as well. I am ingesting the profiles using the HTTP API from Postman, please tell me what might be causing this issue.

Experience Platform

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

Best answer by abhinavbalooni

Hi @abhinavbalooni, what if I add a profile with same primary id (Email Address here), with other attributes being different, will that update the previously existing profile? Does this thing depend on the merge policy?

@pareek1 Now you are talking about data ingestion into AEP instead of sending data out of AEP.

To answer your question, it depends on a few factors. If you have upsert enabled on the dataset which you are using to ingest profile information, then your profile would be filled with information for fields which are new to the profile and the existing fields would get updated (Upsert - Update + Insert). If your dataset is not upsert enabled, the latest profile information sent through would overwrite the existing profile. This would hold true in line with a time based merge policy. Since the data in this scenario is being sent to only one dataset, hence dataset precedence merge policy would not be relevant/applicable.

Hope the above helps.

Cheers,

Abhinav

abhinavbalooni

Community Advisor

Hey @pareek1

When you say duplicate profiles. Which field is the identity here ? Is it marked as an identity field in AEP ? Did you check under profiles? Is it coming up as one profile ?

P

Pareek1Author

Level 2

Hi @abhinavbalooni the Email Address is the primary identity here, yes it is marked as an identity field in AEP, yes I had checked in profiles and it is coming up as one profile. I am using a pebble template in my server config, that might be causing the issue but I am unsure how, so adding the unescaped template.
There are many profiles that are coming up only once, but some profiles have this problem.

{% for profile in input.profiles %}
{
   "body": {
     "CreateLeadRequest": {
       "MessageId": null,
       "MessageType": null,
       "IntObjectName": null,
       "IntObjectFormat": null,
       "ListOfANTM Creat Lead IO": {
         "LeadInfo": [ {
           "Email Address": "{{profile.attributes.Email_Address}}",
           "Reference_Number":"{{profile.attributes.Reference_Number}}",
            "Response_Create_Date":"{{profile.attributes.Response_Create_Date}}",
            "Routing_Code":"{{profile.attributes.Routing_Code}}",
            "Vendor_Lead_Id":"{{profile.attributes.Vendor_Lead_Id}}",
            "Vendor_Source":"{{profile.attributes.Vendor_Source}}"
                   }]
       }
     }
   }
 }{% if not loop.last %},{% endif  %}
{%endfor%}

P

Pareek1Author

Level 2

@pareek1 Now you are talking about data ingestion into AEP instead of sending data out of AEP.

To answer your question, it depends on a few factors. If you have upsert enabled on the dataset which you are using to ingest profile information, then your profile would be filled with information for fields which are new to the profile and the existing fields would get updated (Upsert - Update + Insert). If your dataset is not upsert enabled, the latest profile information sent through would overwrite the existing profile. This would hold true in line with a time based merge policy. Since the data in this scenario is being sent to only one dataset, hence dataset precedence merge policy would not be relevant/applicable.

Hope the above helps.

Cheers,

Abhinav

Hi @abhinavbalooni, Thanks a lot. This will surely help me.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded