Audiences

The Audiences module maintains a hierarchical list of audiences.  Audiences are intended to logically group web site data by the audience by which  it will be view.  By default all web sites have a Root or Main audience.  Descendants of the root audience can be created uniquely within each web site. Starting on July 16, 2018 new prices systems are now in effect for the Google Maps Platform. This is only in affect if you are using the GeoCodes attribute in this module. Please see the User Guide and view this option's billing here. In addition to the standard audience attributes the Audiences module also contains Properties.  They are intended to create a custom set of attributes for each Audiences module.  The web site property 'Audience Properties File' defines the location of the properties XML file.  This web site property value can be changed for a custom set of audience attributes.  These attributes will also be accessible from the web sites CDA.

When logging into a console you are always logged in as a single audience.  You can then view the current audiences records and all descendant audience records.  You may change your current audience using the Audience Tree.  Module attributes are also appropriately filtered by the selected audience.  If a user is given access to an audience she is automatically given access to all descendant audiences.

Audiences: Create a new Website via Audiences

The instructions are for you to create a new website using CentralPoint's Audiences module. You can blend this into an existing design, or make it look like a completely different site all-together. The instructions below will assist you in the initial creation of a new audience/website.

Audiences play a huge factor in back-end management. You can assign Administrators to individual Audiences, and they will only be able to view/edit records that are assigned to the same Audience as their Administrator record.

1. Site Architecture > Audiences: Create your new audience using the console location in this step. Please note that your Audience system name will show in the URL bar within every page of that particular audience. I typically will keep them as short as possible, often using acronyms to abbreviate the system name.

   The "Main" audience is the root & default audience in every client console.

   Example: client-domain-here.com/main/navigation-system-name.aspx

   The bold piece of the example URL above is the audience system name. After creating your audience, this system name is set in stone. There is no way to change it, so please be certain this is desired from initially creating the audience.

   In this example, lets pretend we created an Audience with the system name being site1.

2. Site Architecture > Homepages: To access your new audience using a front-end URL, you will need to assign it to a record in this Homepages module. You can share a homepage with another audience, or create a brand new one specific to site1.

   In this example, lets pretend we created a new Homepage record with the system name being site1-home.

   Your front-end URL would now be: client-domain-here.com/site1/site1-home.aspx

   Please note the following. You still will not be able to access the front-end until the next step is complete. Each audience should ONLY be assigned to ONE & ONLY ONE homepage record. Audiences assigned to multiple homepages could, and most likely will produce errors on the front-end website.

3. Design > Styles: This is the final step before your new site/audience is ready for front-end viewing. You must either tag an existing Styles record to your new audience, or create a brand new one. Again, each audience should only be assigned to ONE & ONLY ONE record in Design > Styles. An audience assigned to multiple records in this section of the console could, and most likely will cause issues within your new audience/site.
4. If you have followed these steps exactly as laid out, you will now be able to access the front-end of your website @: client-domain-here.com/site1/site1-home.aspx

Audiences: Apply Unique Design

1. To first begin applying a unique design per audience, please step through all steps outlined in Audiences: Create a new Website via Audiences
2. You will want to assign this audience with a unique record in both Homepages & Design > Styles.
3. Site Architecture > Module Designer: You will want to begin with creating 2 new records here. One if for the Homepage layout, and the other is to control the interior pages / all pages pulling from the Navigation module. This is done using the drop-down menu labeled Module after you click the "NEW" button.
4. When inside these records it is best practice to set the field Use Navigation Content? to No.
5. Insert this CpScript to pull the primary content from these modules: [cp:scripting key='Attribute' systemname='Content' ExecuteCpScriptsInResult='true' /]
6. Go back to the Audience that you want to enable this new design for. Site Architecture > Audiences > (find / select audience)
7. Click the tab labeled Company.
8. Near the bottom of the record, there are two fields that you need to utilize to assign the newly created records built within Module Designer.
9. Near the bottom of the record, there are two fields that you need to utilize to assign the newly created records built within Module Designer.
10. Homepages Module Design (HomePagesModuleViews): Set this to new Homepages Module Designer record that you've just created.
11. Navigation Module Design (NavigationModuleViews): Set this to new Navigation Module Designer record that you've just created.
12. Now save the audience record, and refresh your new audience's URL. The homepage & navigation pages will be reading the design layout from these new Module Designer records.
13. Please note: You may need to also create other new records in Module Designer to finish your site. For example: If you're utilizing News & Events modules, there is a good chance that you will need to create new versions of these to specifically match the look & feel of your new audience.