Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

Avoiding Repetition of Audience Attribute Comparisons

emarks87
Level 2
Level 2

We have the following business requirements for a given audience:

 

profile attribute "stateA" is present AND does not equal "CT" 

OR 

profile attribute "stateA" equals "CT" AND mbox param zipCode equals one of a list of 300 zip codes

 

This has been implemented successfully into an audience.

 

Where we foresee future issues is with a follow up set of requirements:

profile attribute "stateA" is not present AND profile attribute "stateB" is present AND does not equal "CT"
OR

profile attribute "stateA" is not present AND profile attribute "stateB" equals "CT" AND mbox param zipCode equals one of a list of 300 zip codes

 

I'm wondering if there's a way to store the list of 300 zip codes in a centralized place to avoid repeating the list across multiple audiences whenever we need to reference it. If the list of zip codes has to change, we would prefer only having to update it in one place, instead of multiple places.

0 Replies