Hi, I'm using offline data in Audience Manager, and have a data source and corresponding ID sync set up using the setCustomerID function. I would like to use the same data for reporting in Analytics, and am trying to set it up in Customer Attributes. My initial thought was that since I'm already sen...

Hi,We are trying to set up cross-domain tracking according to this guide: https://docs.adobe.com/content/help/en/id-service/using/id-service-api/methods/appendvisitorid.htmlIt seems this works fine when the user hasn't already visited the destination domain. They land on that domain and their experi...

What is the correct way to update customer attributes for already uploaded CRM IDs? For example when customer changes age group or segment.Case in point: I have uploaded a test customer with attribute "Age" as 29. I have previously logged in as this customer, and I see visits where Age=29 in Analyti...

Find the column reference here:https://marketing.adobe.com/resources/help/en_US/reference/datafeeds-reference.html

Hi,Following up on my previous question here: Experience target on customer attributes I have set up customer attributes and mapped them to Target. I uploaded a test customer and am trying to target this based on age. I called the customer attribute source "AnalyticsID-TEST".The customer attributes ...

Thanks for the reply. A follow-up question: would this require Target being implemented in the authenticated channel? Currently we don't have Target in there, but we do have the Experience Cloud ID Service and Analytics of course.

We have set up some customer attributes for testing, and are seeing them available in Target. The Customer ID we use is sent on the authenticated area of our site, but we also have many pages that people might visit before / after they log in.Can we target users on customer attributes after they hav...

I have since found a solution for this. It was because the segment was based on a success event that had visibility set to "builders". When I switched it to "visible everywhere" the error disappeared. But I agree it looks like a bug, so I've submitted it to Customer Care.

As far as I know it's not available in Workspace by default, but you can add a processing rule to populate a prop or eVar with it:

Hi,I'm trying to create a calculated metric based on a segment I have (it includes only internal traffic, based on an event we set by IP in processing rules).The segment works if I apply it to a report with a visit metric. The dimension is a prop that's present on every event on the site:And when I ...