Get ready! An upgraded Experience League Community experience is coming in January.
SOLVED
Issue: Shared Analytics Segment/Audience (3 views logic) not qualifying in Target
Analytics segments when published to experience cloud from analysis workpsace reaches to Target but note that there is a latency of 24 to 48 hours as it is a batch processing. qualification happens after data processing, not during the visit.
https://experienceleague.adobe.com/en/docs/experience-cloud-kcs/kbarticles/ka-16471
I would recommend for this type of use case (frequency based, same session personalization), Target profile attributes are the best approach. Target updates profile attributes near real time when the visitor interacts with the site & unlike Analytics segments, profile attributes are evaluated client side and stored in Target’s profile instantly.
If you are using adobe web sdk, then send profile attributes under the __adobe.target so they persist in the Target profile.
Example create this data element in custom code
// with some counter logic, here am using localstorage
var pdpCount = parseInt(localStorage.getItem("pdpCount") || 0);
pdpCount++;
localStorage.setItem("pdpCount", pdpCount);
var data = {
__adobe: {
target: {
"profile.visitedPDP": pdpCount
}
}
};
return data;and sendEvent by updating data object:--
Then also test in experience platform debugger to see the audience qualification or go to the interact call on n/w tab to see whenever the PDP loads, the counter increments in the 'data'. The updated value is sent to target via Web SDK.
then simply create the audience in Target, it should work near real time.Refresh the page to view the experience.
If not using web SDK similar logic you could do for updating mbox profile parameter and it would work similarly.
hi @EJCS
even with no AEP and no Web sdk it is fine, you can still achieve this using at.js profile parameters Pass Parameters: Target.
The issue with AA segments not syncing after 48 hours suggests that the Core Services audience sharing might be broken (e.g., ECID sync issues etc or something with the integration) because normally, even with latency, the audience should appear in Target after processing.
I understand you want to use AA segment since your requirement is based on historical behavior but you should also do this for real time qualification, by just using Target profile parameters:
With this at.js targetPageParams code below logic, it can be tried to the PDP page if using adobe tags/Launch or directly in your site code.
// Increment PDP view count
var pdpCount = parseInt(localStorage.getItem("pdpCount") || "0", 10);
pdpCount++;
localStorage.setItem("pdpCount", pdpCount);
// Pass profile parameter via targetPageParams
targetPageParams = function() {
return {
"profile.visitedPDP": pdpCount // This persists in Target profile
};
};
Or use in adobe tags/launch with this extension of adobe target to add page param:--
Then create a Target audience based on this mbox profile as shared before with profile.visitedPDP >= 3
This will qualify the user on the next page load after the audience qualification.
Also, you can debug by using experience Platform Debugger - Target -Profile tab.
or just enable 'Target Trace' to confirm the profile parameter (visitedPDP) is being sent and updated.
You’ll see the activity in the next visit once the audience qualification is met.
When I had AAM I used profile viewer https://experienceleague.adobe.com/en/docs/audience-manager/user-guide/features/visitor-profile-view... to check if the same aam uuid/mid qualifies for the analytics audience.
If you don’t have AAM, Go to your Experience Cloud - People - 'Audience Library' How to Create an Audience in Audience Library
check if your audience appears here with historical counts, you can also create an audience here (real-time with AA variables or based on shared Experience Cloud to see the count). Because these should also sync to Target if then all is working.
If this still doesn’t work, it’s worth checking with Adobe Target forum as suggested by @Jennifer_Dungan or Customer Support team to confirm if the audience sharing integration is correct or not, so this is worth checking with adobe Support.
Related Conversations
