Workarounds for needing to use over 250 values for a string attribute in an audience

[NickMannion]

Hi Adobe Community,

Our team is trying to paste an excel document with 3000 values into a string attribute in AEP but we are running into the issue where the attribute has a max value of 250 values that you can insert. Anyone know of any workarounds for this?

Thanks,

Nick

[Tof_Jossic]

@NickMannion can you maybe split those in multiple OR conditions within Segment Builder?

[NickMannion]

Yeah that's the only solution I've seen so far. It's just a little time consuming have to create 12 different excel files of 250 each and then adding the attribute in 12 different times with OR in between and pasting each unique group of 250 zip codes into the 12 attributes 

[brekrut]

Are there 3K unique values or do they have similar patterns?  

What is the goal your team is attempting to accomplish?

[NickMannion]

Yeah it is 3000 unique values. Ah I see what you're getting at. Like if all the values start with 500 then just do "starts with 500." I'll have to double check on that but it is essentially 3000 different zip codes that we want to include.

[brekrut]

Another item to consider is leveraging Data Distiller is to create an audience with the zipCodes which are being considered.  

[NickMannion]

Yeah, that's another good idea. I think we would like to stay away from that route because SQL audiences in our platform only have a 30-day time to live so that wouldn't be a manageable long-term solution for us

Thanks,

Nick

[Vinoth_Govind]

Hi @NickMannion 

If you are trying to create a segment for the 3k zip codes, 

Why cant we create a lookup dataset (with zipcode as the primary identity) and ingest the 3000 codes into the dataset

In your main Profile Schema, create a relationship between your zipcode attribute field and your new Lookup dataset.

In Segment Builder: Instead of "Zip Code equals [Paste 3000 values],we can simply drag in the relationship and say: "Where Zip Code is not null in the new dataset".

Never tried it , but logically sounds good.

[NickMannion]

Hi Vinoth - yeah that totally makes sense to me and definitely is a very clever workaround. Unfortunately, that would require development and validation from our team which would take some time. Additionally, we have multiple different audiences that will use different zip codes so unfortunately, that would require many different lookup tables. My main hope was to find a quick kind of on demand way that someone could just go in and put these 3K values in an audience.

Thanks,

Nick

[Abie]

Hi @NickMannion ,

I am not sure if I understood the problem precisely; I assume you are trying to create an audience with a condition that the zip code could be any of 3000 values? And then you bump into a problem that the condition doesn't allow more than 250 values.

If this is the problem, then you could also create segment of segments. Create 250*12 segments for these 300 zip codes and include the segment check in the audience.

Not sure if this is contextual per your problem. But thought to make a suggestion anyways.

Thanks!