> ## Documentation Index > Fetch the complete documentation index at: https://docs.zeotap.com/llms.txt > Use this file to discover all available pages before exploring further. # Granular Consent > In recent times, under most regulations, consent does not behave as a simple opt-out signal. It has rather become explicit and specific. The user has the choice to define the specifics of how their data must be used by granularly opting in or giving consent. The opt-in option covers the different usages of their data. To support the granular consent collected from each of your users, Zeotap provides you with an easy-to-use DIY interface to define consent attributes in your Zeotap catalogue for the regulations under which you operate. ## Step 1 - Define the Consent Attributes As a brand you can manage your consent in Zeotap by first starting with defining the consent attributes in your catalogue, followed by which you have to map them to your source fields. Note that every source type can bring in different types of consent data and that can easily be defined using our catalogue. Through the catalogue, you can define as much consent as you capture across sources, store them against the user profiles and then use them as per the activation use case of your business. To know more, refer [here](/articles/unify-customer/adding-a-consent-category). ## Step 2 - Map and Ingest the Consent Attributes Once you have defined the consent attributes in your catalogue, next you have to map your consent fields in the source. Once the mapping is successfully achieved, the system then makes these consent fields available in the various other touch points across the Zeotap CDP platform like Segmentation in Connect or Workflow creation in Symphony. To know more, refer [here](/articles/unify-customer/map-the-catalogue#consent-purpose). We highly recommend that every source must have consent attributes attached to its user data. This helps us to map consent to the user’s 360 profile and eventually use them as per the user’s preferences. ### Consent Resolution Consent information for a purpose can come in the following ways: * From multiple sources * Against multiple IDs * At different times, and/or * With different values Collect handles all these disparate signals to store the latest consent per customer. The following are the steps involved in handling these disparate data: 1. The system starts by identifying the Unique Customer ID based on the [ID strategy](/articles/unify-customer/id-strategies) and incoming IDs in the request. 2. We then evaluate if the incoming record has a valid, non-null consent signal. 3. Next, we compare the event timestamps (especially valid for batch files or server-to-server calls) to decide which is the latest signal. 4. Finally, we update the consent value and the corresponding properties as per the resolution. ### Storing the Consent Purposes Zeotap store the consent purposes in the customer’s profile against the Unique Customer ID as follows: `{{regulation}}_{{consent_purpose1}}` The system removes the spaces and symbols while storing the consented purpose in the data store. For example, CDP Storage added under **GDPR PURPOSES** on the UI is stored as a consent attribute named **gdpr\_cdp\_storage** in the Collect profile store. ## Step 3 - Define Rules for Consent Orchestration Now that you have defined the consent attributes and ingested in your Zeotap account, the third step is to define the rules for the consent activation layer using the consent attributes. Through orchestration, you can automate your consent and set up high-level rules for your account to be adhered to whenever any data segmented or pushed out of the Zeotap CDP platform. For example, during segmentation, user data is filtered out based on a rule applied to the segment. Similarly, the orchestration rules are also applied at the destination level whenever data is pushed from multiple platforms. To know more, refer  [here](/articles/collect/consent-orchestration-2830401643). ### Mapping Consent Purposes for Audience Activation You have to map the relevant consent purposes and their values for the purposes of advertising audiences. Once the consent purposes are mapped, this condition is evaluated for all segments created on the Connect module. The following steps summarize the way this works: Once a segment is created, Connect pulls the consent purposes and values mapped to the *Audience Creation for Advertising* activity and adds this as a default filter. The Zeotap extensions are applied to the filtered users, only. The third-party audience is combined with the filtered users. In the Summary section of the segment details, the excluded user count is displayed.