Problems with sending an audience that was created from a CSV file

[JuanOrozco_96]

Hello everyone

I'm currently trying to send an audience created from a CSV file from RT CDP to a  POS destination. When I make the audience with the option "Import audience", this action automatically creates an dataset and a adhoc schema which i can't activate to profile. When I try to send this audience to the destination it shows an error saying that the dataset is no activated to profile. How can I activate this imported audience? or how can i activate this dataset to profile to commit my sending ?. Thanks a lot. I look forward for your answers.

[DavidRoss91 · Accepted solution]

Hi @JuanOrozco_96 

When enabling for profile, have you enabled the schema first and then attempted the dataset? Or are you having issues even getting that far?

David

[MichaelAn3]

Hi @DavidRoss91,

I'm having this same problem. When I import an external audience created from a CSV file, it automatically creates an adhoc schema and dataset. When I view the schema, there is no way to enable it for profile. Other schemas that I create manually do have the option available, but the adhoc schemas that get created through importing audiences via csv do not appear to have the option. Any assistance with this would be greatly appreciated.

Mike

[TylerKrause]

Hey Mike! Instead of doing it this way, can you do a local file upload on your profile Schema? This way it should get ingested into your Profile spec and you should be able to utilize it as any other audienc/profile.

You can do this by going to Sources in AEP, Local File Upload and then go through the mapping. This feature is extremely helpful.

Best, 
Tyler 

[MichaelAn3]

Thanks for this advise! I can try that, but will need to figure out how to create an audience from the dataset. My high level goal is activate these externally defined audienes to Adobe Target. One thing I've tried is to use a segment definition schema with a non-person identifier marked as primary identity, with our custom identiy added to that to identify the customer - that allows me to target the dataset in the segment builder, but unfortunately no profiles are realzied in that segment. I'm wondering if at this point I need switch external customer Id to primary within the segment definition.

Thanks, Mike

[TylerKrause]

There's a native integration between AEP and Target via AAM that allows you easily sync your audiences between the two systems. 

Are these profiles you're uploading known profiles in AEP already, or a true external list? 

[MichaelAn3]

They are in the system via analytics connector - I've marked a custom dimension evar prop as our customer identity.

[TylerKrause]

Ooooo! Even better then if they're known in AEP already!

Here's the workaround we did in our envrionment to get around it. 

We have an event schema and dataset that we titled something to the effect of "Custom Lists". It is an event schema, that has nothing on it other than the Primary ID, and a field called customListGroup.

You can than do that local file upload to this dataset, and when you do the mapping, make sure you add a custom _id (I usually make it a SHA256 of some of my other fields concatted together), and then map your timestamp, custom list group and Identifier. Than all you need to is make your audience whatever you upload for your custom list group and just like that you have a totally scalable solution! 

[MichaelAn3]

Innovative solution!

For the audience creation, I'm currently using segment builder to hunt for the new customListGroup field under events in the UI but not seeing it yet. Will keep digging, thanks for the suggestion!

[TylerKrause]

Make sure both Schema and Dataset are profile enabled, and then load some sample data through. Should be smooth sailing from there

[MichaelAn3]

Got it! Thanks for the help! I see that show up now in segment builder. On sample data upload have you ever seen it error on the _id field? I've concatenated an id field with the current timestamp, hashed it usiing SHA256 but it's still giving an error for:

The following unmapped paths are required: _id. Please include the required paths and try again.

Thanks again this was very helpful.
-Mike

[TylerKrause]

Far too familiar with the error, hahaha. If the function that you use to feed into the _id that you map is null, it will throw this error. Here's an example of a functional one that would be commonly used if as an example the identity you feed in is "CUID" for your upload.

sha256(concat(now(),"_",CUID))

Let me know if that does the trick!