Adobe Audience Manager跨设备访客拼接技术咨询

Hey there! Since your team already has Adobe Analytics (AA) integrated with Adobe Audience Manager (AAM), you’re well-positioned to build that unified visitor journey you’re after. Let’s walk through exactly how to set up cross-device cookie stitching once users authenticate (like after logging in):

Before diving into steps, it’s key to grasp AAM’s core identity types:

• ECID (Experience Cloud ID): The default device-level ID stored in cookies, tied to a specific device/browser.
• Authenticated ID: Your system’s unique user ID (like a member ID, hashed email, etc.) that identifies a user across devices once they log in. Cross-device stitching relies on linking multiple ECIDs (from different devices) to the same Authenticated ID.

1. Double-Check Your AA-AAM Integration #

Since you’ve already completed the integration, confirm these critical settings to ensure identity data flows smoothly:

• Server-Side Forwarding (SSF): Make sure SSF is enabled in your AA admin console. This lets AA send hit data (including identity variables) directly to AAM without extra client-side calls, which is more reliable for identity stitching.
• Variable Mapping: Verify that any AA variables you plan to use for authenticated IDs are mapped to AAM traits/identity fields. You’ll need this to pass the user’s authenticated ID from AA to AAM.

2. Capture the Authenticated User ID Post-Login #

Once a user successfully logs in, you need to send their unique authenticated ID to AAM. You have two solid options here:

Option A: Use AA Custom Variables (eVars/Props) #

Assign an unused eVar to store the authenticated ID, then set it on the login success page. For example:

// Assuming you're using AppMeasurement.js
s.eVar10 = "user_12345"; // Replace with your actual user ID and eVar number
s.events = "event1"; // Optional: Tie to an event to trigger immediate data send
s.t(); // Send the hit to AA, which forwards to AAM via SSF

Then, in AAM, go to Identity Management > Identity Namespaces and map this eVar to your authenticated ID namespace.

Option B: Directly Call AAM’s DIL Library #

If you’re using the Data Integration Library (DIL), you can set the identity directly:

// Initialize DIL if not already done
var dilInstance = DIL.create({
    partner: "your_aam_partner_id"
});

// Set authenticated ID post-login
dilInstance.api.setIdentity({
    id: "user_12345", // Your unique user ID
    namespace: "your_authenticated_namespace" // Namespace you created in AAM
});

3. Configure Identity Stitching Rules in AAM #

This is where the magic happens—telling AAM to link ECIDs to the same authenticated ID:

1. In the AAM UI, navigate to Identity Management > Identity Stitching.
2. Click Create Rule.
3. Name your rule (e.g., "Cross-Device Stitching for Logged-In Users").
4. Under Stitch Based On, select your authenticated ID namespace.
5. Set the Stitch Trigger (most teams use "Always stitch when the identity is present").
6. Define the Stitch Expiry (e.g., "Never expire" for permanent user profiles, or a timeframe if you prefer).
7. Save the rule—it will start processing new identity data immediately.

4. Validate Your Setup #

To make sure everything works:

• Use the AAM Visitor Profile Tool to look up a test user’s authenticated ID. You should see multiple ECIDs linked to it if you tested across devices.
• Check AA’s reports: Segment users by their authenticated ID and verify that behavior from different devices appears under the same user profile.

• Namespace Consistency: The identity namespace you use in AA/DIL calls must exactly match the one created in AAM. Mismatches will break stitching.
• Privacy Compliance: Don’t forget to align with regulations like GDPR or CCPA. Ensure users have given consent for cross-device data collection and stitching before implementing.
• Test First: Run end-to-end tests in a staging environment—simulate login on a mobile device, then access your site on a desktop with the same authenticated ID, and confirm the profiles are linked.

内容的提问来源于stack exchange，提问作者Adwait