Hydration of profile attribute is unstable

[ButhpurKiran]

Hi Team,

We are working on creating an audience that qualifies profiles based on the Edge Merge Policy where the ECID and attributes of the profile will be added to "Hub" option, that converts into "Edge" which takes around 10 to 15mins for the attribute to get added into Edge segment. We have observed that not all profiles are getting converted into Edge even after 4 to 5 hours. Have anyone experienced similar issue and any isights can greatly help us moving forward.

Thanks in advance!

Kind regards,

Kiran Buthpur

[Jyoti_Yadav]

Hi @ButhpurKiran ,

The issue you're describing with the Edge Merge Policy, where profiles aren't consistently converting from "Hub" to "Edge" within the expected timeframe, is a common problem stemming from several potential causes:

• Data Volume and Processing Time: The time it takes to merge profiles and update the Edge segment is directly related to the volume of data being processed. If you have a very large number of profiles, the 10-15 minute estimate might be significantly underestimated, especially during peak processing times.
• Data Quality Issues: Problems with the data itself, such as inconsistencies in ECIDs or malformed attributes, can cause individual profiles to fail the merge process. This can lead to a backlog of profiles that never successfully convert to the Edge segment.
• Merge Policy Configuration: There might be an issue with the configuration of your Edge Merge Policy itself. Incorrect settings or conflicts with other policies could prevent profiles from being correctly merged.

Please try these troubleshooting steps to resolve the issue:

1. Monitor AJO Performance: Use AJO's monitoring tools to check for resource constraints or performance bottlenecks during the merge process.
2. Review Merge Policy Logs: Examine the logs related to the Edge Merge Policy to identify any errors or warnings that might indicate why specific profiles are failing to merge.
3. Data Quality Audit: Conduct a thorough audit of your profile data to identify inconsistencies or errors in ECIDs or attributes that could be causing merge failures.
4. Review Merge Policy Configuration: Double-check the configuration of your Edge Merge Policy to ensure it's correctly set up and doesn't conflict with other policies.
5. Contact Adobe Support: If you've exhausted all other troubleshooting options, contact Adobe support. They have access to system-level information and can help diagnose the problem.

Thanks,

Jyoti

[ReenaJohn]

Hi @ButhpurKiran  ,

Yes, we had faced similar issue and had raised an Adobe ticket to have Adobe check on this. The data volume that we had was huge and that was causing the delay in realization. Try and optimize the data that is being ingested using the Edge Merge Policy. If you still persist to have issue, please raise an Adobe ticket and the support team can help identify the RC and with the next steps.

Warm Regards,

Reena John

[Pulkit_Jain_ · Accepted solution]

@ButhpurKiran 

Delays or incomplete profile propagation to Edge are known architectural challenges. The most common reason profiles do not propagate to Edge is that they lack the required ECID or the ingested event was not marked as edge-enabled.

To resolve this, review your schema and dataset mappings and use the merge policy preview tool in AEP to verify how profiles will be merged.

[Sukrity_Wadhwa]

Hi @ButhpurKiran,

Were you able to resolve this query with the help of the provided solutions, or do you still need further assistance? Please let us know. If any of the answers were helpful in moving you closer to a resolution, even partially, we encourage you to mark the one that helped the most as the 'Correct Reply.'

Thank you!