Community Settings

1: Settings

1.1: General settings

Name: Name of the current community, used only for internal purposes and is never displayed to your panelists.
Rewards Administrator: Selected user is in charge of approving point redemption requests submitted by panelists. All rewards-related emails are sent to this user.
Initial Reward Points upon Joining: Initial points awarded to panelist when they sign up to this community.
Send a Notification Email: Panelists are sent an email notification when their reward redemptions have been approved.

Note: Automated redemptions will not trigger a notification email.
Community Notifications are sent to community members by using:
- Email: All outgoing messages will be sent as HTML emails.
  
  Note: Email is the only option if has not been configured.
- SMS: All outgoing messages will be sent as text messages. Notice that your panel has to have all necessary data points (carrier, phone number) set up. If sending the SMS fails for some reason, it will send an email instead.
- Use both email and SMS: Panelists will receive both email AND SMS. If sending the SMS fails, it will not fall back to email.
- Automatic (based on device): Depending on the device that the user was using or the circumstances under which the message was requested, the panel will determine automatically which type of message is sent.
- Use both email and SMS: Panelists will receive both email AND SMS. If sending the SMS fails, it will not fall back to email.
- Automatic (based on device): Depending on the device that the user was using or the circumstances under which the message was requested, the panel will determine automatically which type of message is sent.

1.2: Community settings

Mode: Allows for two community modes:
- Panel (Built In) uses all of the built-in features of the Community Manager.
- Other (API) uses the Panel Management Community API to allow third party software or sites/applications outside of Panel Management to use a limited set of Community tools.
Note: Separate API access and whitelisting is required to use API mode. Contact your account manager to setup access.
Published (available for panelists): Toggles Community accessibility. When set to No, the message "This site is currently down for maintenance" is displayed to panelists.
Allow login for unsubscribed panelist: Toggles whether a panelist who has opted out of your panel can access your Community. Default value is Yes. If desired, conditions can be applied to menu items, pages, components, or widgets to restrict access for those that are unsubscribed or blacklisted
Allow login for blacklisted panelist: Toggles whether a panelist who has been flagged for blacklisting by an administrator can access your Community. Default value is Yes. If desired, conditions can be applied to menu items, pages, components, or widgets to restrict access for those that are unsubscribed or blacklisted.
Maximum number of referrals per month: Limits how many referrals each individual panelist is allowed to submit per month. There are instances where it is a good idea to limit the number of referrals per month, especially when you are giving out reward points for doing so.

Note: Enabling this feature will count referrals retroactively.

For example, if you set this value to "2" and a particular panelist already referred two panelist this month before the limit was turned on, they cannot refer any more panelists for the rest of the month.
Notify referrers: When set to Yes, the system sends a notification email to the referrer of a panelist when the referred panelist registers and opts in through the referral link they were sent. Once activated, the notify email can be customized under the Auto notifications section of the Community Manager.
Enable automated birthday emails: Toggles whether or not you want to send an automated birthday greeting to panelists.

Note: Birthday e-mails require that date of birth is collected from panelists and set as a system field within the datapoint manager. Users can also configure a customized message within the Community Auto Notifications tool.
Default time zone: Defines a default time zone per community. This default is used when the panelist does not have a time zone selected, usually right after registering.
Published (available for Panelists): Select Yes to make the community accessible. When No is selected, panelists will see a message that the site is down for maintenance.
Enable mobile device detection: Toggles whether your community will utilize Panel Management' multi-device optimization. A mobile framework will be displayed if a mobile or tablet device is detected. Default value is Yes.

Note: Changing this value takes effect for the panelist after their session has expired or the panelist has logged out.
Default page - Select the home page displayed to site visitors prior to login when visiting the community's root domain. Pages available in the drop-down must be built in the Community Pages area of Community Manager.
Default logged-in page: Select the default page displayed when a panelist logs into your community. If set to none, the Default Page is used.

Note: Assigning a condition to the default or default logged-in page is not recommended and may result in an error when that page is visited by a panelist.
Default privacy policy page: Select the default page displayed when a panelist logs into your community. If set to "none", the Default Page is used.
Default terms and conditions page: Select the default page displayed when a panelist logs into your community. If set to "none", the default page is used.

1.2.1: Community Settings: API Mode

Receiver URL for landing pages (API Only): The URL that the user is sent to after their interaction with the panel when the built-in Panel Management Community functionality is not used.

For example, if you specify "https://clientdomain.com/landing.php" as your API-landing page URL and a panelist completes a survey, Panel Management will add a special parameter onto the end of this URL. For example: "https://clientdomain.com/landing.php...DEcnj3ddf[...]".

The value of this parameter must then be passed back to the panel through the API and the correct landing page texts in the panelist's selected language (including all data point replacements, etc.) are returned.
Piping panelist data in the landing page receiver URL:
- Use standard bracket notation for system fields: https://supercommunity.com/landing.php?email=[email]
- Use the tilde for data points: https://supercommunity.com/landing.php?fn=~Qfirstname~
- The data is sent in encrypted form. The resulting URL, if encrypted data is added, looks like this: https://supercommunity.com/landing.php?kslp=AkjdJDEcnj3ddf[...]&data=ZlZh7xo-kuebukPy2YF[...]
- The data you included in your url parameters is in the encrypted URL parameter called data.
  
  Below is an example code in PHP on how to decrypt the data.
  
  Use the following code snippet to decrypt datapoint data passed back from the landing page reciever URL.
  
  The $key variable is the secret you set on the community settings page.
  
  Note: The maximum key length for Triple DES is 24 characters.
  
  The $string variable is the data you recieve from $_GET['data']. This variable contains base64 encoded and 3DES encrypted data. To make it URL safe + and / are replaced with - and _.
  
  The resulting $decrypted_string is a JSON encoded array containing all properties you specified in the receiver URL.
  - Original landing page URL and secret entered in community settings
    
    URL: https://supercommunity.com/landing.php?email=[email]&localid=[localid]
    
    Secret: {myS3cr3t}
  - Code example of the function to decrypt the data
```
function decrypt_3des_base64($string, $key) 
{ 
    $decrypted_string = openssl_decrypt( 
        $string, 
        'des-ede3', 
        $key, 
        OPENSSL_ZERO_PADDING 
    ); 
    return trim($decrypted_string); 
}
```
  - Code example
```
<?php 
// https://supercommunity.com/landing.php?kslp=AkjdJDEcnj3ddf[...]&data=afgX_Ltoq9ahrVG_lGm7bqO3V172b38R0AGolZ_O4lapqjFtOvax5-IrWnetOv7g 
    $data = $_GET['data']; 
    // Use the same secret as in the community
    $key = '{myS3cr3t}'; 

    // Revert URL safe encoding
    $mod4 = strlen($data) % 4; 
    if (0 !== $mod4) { 
        $data .= substr('====', $mod4); 
    } 
    $string = str_replace(array('-', '_'), array('+', '/'), $data); 
 
    $decodedJSON = decrypt_3des_base64($string, $key); 
    // {"email":"john.doe@example.com","localid":"1"}
?>
```

1.3: Community URL(s)

Enable custom community URLs: Check this option to allow users to specify custom community URLs (virtual domain) for their Community portal.

If the checkbox is checked, but all URLs are left empty, then custom URL support is disabled.

When custom community URLs are enabled, a row is displayed for each language in the panel with a text box next to it. Each text box allows the user to enter a valid URL for each individual language. For example, English: https://en.mycommunity.com

Note: The client and Panel Management IT still have to configure your DNS and Panel installation for new domains before they can be used here. If enabled but URLs are not specified, the feature behaves as though disabled.

1.4: Send Automated Opt-In Reminders

When this feature is enabled, if a new panelist has not confirmed their membership in the amount of days set under Interval, the panelist is sent a reminder. The panelist will continue to receive reminders at the set Interval, until the set Max number of messages is reached.

Interval: The number of days between reminders sent to unconfirmed panelists.
Max number of messages: The maximum number of reminders sent to unconfirmed panelists.

Note: You can enable this feature at any time. Enabling this feature will immediately send out reminders for anyone who has received an opt-in confirmation but has not clicked the link yet, regardless of when the original opt-in message was sent.

Tip: Prior to scheduling automated reminders, create your branded email template.

Tip: Sending a few opt-in reminders is helpful, but be careful not to send too many or it may frustrate uncommitted panelists and increase your chances of damaging your email sender reputation (due to spam flagging).

1.5: Favicon

Favicon: The favicon that will show up for users viewing the community site. A favicon is the icon that appears in a web browser tab, which is typically directly above the address bar.

The favicon must be a .ico file. The dimensions 16x16, 32x32 or 48x48 pixels work best in all browsers.
Apple touch icons: The "Apple Touch Icon" is used when a panelist saves your community website to their iOS touch screen device's home screen or bookmarks it.

The uploaded image must be a .png file. Depending on the devices you wish to support, the allowed dimensions are different. Available sizes are: 180x180 (iPhone), 167x167 (iPad Pro), 152x152 (iPad, iPad mini).

1.6: Google analytics (Panel Management/Built in only)

Google analytics tracking code: Allows you to integrate your Google analytics account into the community portal. A Google analytics account is required and can be setup at https://marketingplatform.google.com/about/analytics/.

To find your tracking code, go to the Google analytics 4 home page and select the account you wish to link. Once you are logged in, click the "Get tagging instructions" button. There you should see in bold MEASUREMENT ID: G-XXXXXXXXXX.Copy the string after MEASUREMENT ID: and enter that value into the "Google analytics tracking code" text box.

1.8: Captcha (Panel Managment / Built in only)

Panel Management uses hCaptcha as our main captcha provider. Google reCAPTCHA v2 and v3 are also available.

For Google reCAPTCHA v2, users need to create a Google reCAPTCHA account and select reCAPTCHA type – Challenge (v2), “I’m not a robot” checkbox option when creating a reCAPTCHA account with google.

For Google reCAPTCHA v3, users will need to obtain a Google reCAPTCHA account and select reCAPTCHA type – Score based (v3) option when creating a reCAPTCHA account with google.

Type/version: Select one of the available captcha types.
Client ID: The client ID for your selected type/version of captcha credentials.
Client secret: The client secret for your selected type/version of captcha credentials.
Require captcha to opt out: If enabled, panelists must solve the captcha on the opt out landing page before opting out. This setting does not affect the List-Unsubscribe functionality.

Note: Google reCAPTCHA credentials cannot be empty. Both Client ID and Client Secret must be provided. If hCaptcha credentials are left empty, the default values defined in global settings file will be used. If other credentials are required, both values must be provided.

2: Localizations

The localizations tab is used for setting translated values to global properties used through the community system. Each tab within the localizations tab represents a language that is currently being used in the panel and community. To add additional languages, they must first be created within the Language Manager (Panel), then that language's values can be edited here.

2.1: Authorization Texts

Login: Login button text
Logout: Logout button text
Username/E-Mail: Label for the e-mail field when logging in
Password: Label for the password field when logging in

2.2: Cookie Consent

The following pipe(s) are allowed:

%PRIVACYPOLICY_URL%: When this pipe is used, the Cookie Consent Link will point to the URL of the page selected in the Default privacy policy page dropdown. Otherwise, the Cookie Consent Link will point to the value entered in the text box labeled as Link.
%COOKIECONSENTLINK%: This will combine the Cookie Consent Link and Cookie Consent Link Text within the Cookie Consent Memo.

Fields in the Cookie Consent section are:

Memo: Explains the purpose of the cookies.
Link: Link to the privacy policy.
Link text: Text for the link to the privacy policy.
Accept button text: Text for the accept button.
Reject button text: Text for the accept button.

2.3: Actions Texts

Add: Button text for adding a reply to existing threads in a discussion forum.
Edit: Text for editing existing threads in a discussion forum.
Update: Text for update buttons. Update buttons are displayed when updating existing threads in a discussion forum.
Cancel: Button/link for canceling various actions.
Delete: Text for deleting an existing thread in a discussion forum.
Reply: Button text for replying to an existing thread in a discussion forum.
Create: Button text for creating new threads in a discussion forum.
Approve: Button text for approving a new thread.
Deny:Button text for not approving/denying a new thread.
Delete confirm text: Confirmation text that shows when deleting threads from a discussion forum.
Delete confirm yes: Button text for confirming the deletion of a thread from a discussion forum.
Delete confirm no: Button text for not confirming the deletion of a thread from a discussion forum.
Moderator: Text that appears under a moderator's screen name to designate moderator status.
Close: Button text that allows a moderator to close a thread from further posts and hide it from all users. To re-open a closed thread, simply click on it, click the edit button, then save the post.
Next: Button text that allows a moderator to jump to the next thread requiring approval.

2.3: Error Messages

Empty username/password: Error message that displays when a username/password field is left blank.
Invalid username/password: Error message that displays when an invalid username/password is used.
Invalid or expired session: Error message that displays when the session is expired or invalid.
Service unavailable: Error message that displays when the service is unavailable.
Captcha response invalid: Error message that displays when the captcha response is invalid.

2.4: Offline Message

Offline message: Displays to panelists when the community site is offline.

2.5: Info messages

Profile required: Displays to panelists who do not have a profile set up. This typically happens the first time a user logs in as they have not yet set a screen name or contact preferences.

2.6: Warning messages

Unsubscribed warning: Displays to panelists who are unsubscribed.

2.7: Date and time

Text for the following terms:

Start
End
Year
Month
Day
Hour
Hours
Minute
Minutes
Seconds
per Day
per Week
unlimited

2.8: Status messages

Text for the following terms:

Errors
Warnings
Success
Info

3: Moderators

Community moderators are assigned to communities to moderate social features such as Discussions. The moderators can log in to the community as regular users and have special privileges to approve, modify and delete user posts. Moderators may not be able to view some parts of the community such as surveys, rewards, history, and referral pages due to the fact that moderators are not actually panelists.

4: Login Integration

Login integrations allow the usage of OpenID Connect (OIDC) compatible identity providers (IDPs) to authenticate users in the community.

To add a new integration:

1. Click the New integration button.

2. In the Name field, enter the domain name of the identity provider, then click the Fetch settings button next to it. This will attempt to retrieve the provider's configuration from its .well-known/oidc-configuration endpoint.

3. If the settings were fetched successfully, provide the App id and, if PKCE is not being used, the App secret obtained from your identity provider.

4. For the Grants field, enter what OIDC field is offered through your login integration and will automatically be fetched.

Examples: The most common is openid, email and profile, the fetch button would retrieve information and populate it accordingly. If it doesn’t populate, you will need to manually fill in that field. For manually entering the Grants field, this is the most common OIDC information to retrieve through OIDC integration: “openid email profile”.

Note: If you are using Facebook, you only need to enter “openid email”. This will not work with profile.

5. If the automatic fetch does not succeed, contact your identity provider and request the necessary integration values to fill in the remaining fields manually.

6. Once you’ve completed entering the required information, a pop-up modal will appear with the redirect URL that will need to be added to your OIDC app setting.

7. Update the login widget to include a button. You will need to reference your LOGIN_INTEGRATION_URL to link the button to your integration: %LOGIN_INTEGRATION_URL:<LOGIN_INTEGRATION_NAME>%

Note: The LOGIN_INTEGRATION_URL is the name noted in the login_integration name field.

Example: <div style="margin-bottom: 0.5em;"><button class="button idp-button" onclick="document.location.href='%LOGIN_INTEGRATION_URL: <LOGIN_INTEGRATION_NAME>%'"> <img src="themes/1_1_1/IDP_PROVIDER_LOGO.svg" alt="">Sign in with IDP PROVIDER </button></div>

8. Next you will need to add CSS to modify the button for button class=”button idp-button" in your themes css.

Example:

.idp-button, .idp-button:hover {

display: flex;

align-items: center;

justify-content: flex-start;

width: 100%;

}

.idp-button > img {

width: 25px;

height: 25px;

margin-right: 0.5em;

border: 0 none;

}

Note: For OIDC integration with Decipher Registration Survey see Creating-a-Registration-Survey-Using-Decipher

5: Redemptions

This allows enabling and disabling individual redemptions for a community portal. Once a redemption is enabled, it displays in the community and panelists can select it as a redemption option.

Note: Redemption options must first be set up in Redemption Manager.

Forsta Panel Management Support

Articles in this section

In this article