Country Targeting Setup and Configuration

Country-specific targeting allows you to create custom consent banner configurations for individual countries, ensuring each nation’s visitors see consent interfaces that comply with their local privacy laws. This granular control is essential for websites serving global audiences where different countries have different regulatory requirements, cultural expectations, and language needs.

This comprehensive guide covers everything you need to know about setting up country-specific consent rules, from basic configuration through advanced multi-country strategies.

When to Use Country Targeting

Country targeting is most valuable when you need to comply with specific national privacy laws that differ from neighboring jurisdictions or global standards.

Ideal Use Cases

  • Countries with unique privacy laws: Brazil (LGPD), Switzerland (FADP), Japan (APPI), and other nations with distinct privacy frameworks requiring specific consent mechanisms
  • Language-specific banners: Show consent banners in the local language for specific countries, improving user understanding and compliance rates
  • Regional business requirements: Apply different cookie policies based on business relationships or operations in specific countries
  • Testing and rollout: Test new consent configurations in specific countries before global deployment
  • Post-Brexit UK compliance: Configure UK-specific rules separate from EU rules if your UK and EU privacy approaches differ

When to Use EU Targeting Instead

If you need to target all EU member states with identical GDPR-compliant banners, use EU/EEA targeting instead of creating 27+ individual country rules. EU targeting automatically covers all member states with a single configuration, simplifying management and ensuring you don’t miss any countries.

Use individual country targeting within Europe only when you need country-specific variations (like different languages or specific national privacy law nuances beyond GDPR).

Setting Up Your First Country Rule

Creating a country-specific consent rule is straightforward. This walkthrough uses Brazil as an example, implementing LGPD compliance.

Step 1: Access Geolocation Settings

  1. Log into your WordPress dashboard
  2. Navigate to Settings > DigiConsent
  3. Click the Geolocation tab
  4. Ensure your Pro license is active (you’ll see a confirmation at the top of the page)

The Geolocation tab displays all existing location rules and provides options to create new ones.

Step 2: Create New Country Rule

  1. Click Add New Location Rule
  2. In the Targeting Type dropdown, select Specific Country
  3. In the Country dropdown that appears, select Brazil
  4. Give your rule a descriptive name in the Rule Name field, such as “Brazil – LGPD Compliance”

Rule names are for your reference only—visitors never see them. Use names that clearly identify the purpose and location of each rule.

Step 3: Configure Banner Design

With your country rule created, configure how the consent banner appears to visitors from Brazil.

Banner Text and Language:

  1. Scroll to the Banner Content section
  2. Update the Banner Message with Brazilian Portuguese text explaining cookie usage: “Este site utiliza cookies para melhorar sua experiência. Ao continuar navegando, você concorda com nossa política de privacidade.”
  3. Customize Button Labels in Portuguese:
    • Accept button: “Aceitar”
    • Reject button: “Rejeitar”
    • Settings button: “Configurações”
  4. Update Privacy Policy Link Text to “Política de Privacidade”

Visual Customization:

  • Adjust colors, fonts, and positioning to match your website design
  • These visual settings can be identical to your default banner or completely unique
  • Consider Brazilian cultural preferences—bright colors and clear typography often work well

Step 4: Configure Cookie Categories

Define which cookie categories are relevant for Brazilian visitors under LGPD.

  1. Scroll to the Cookie Categories section
  2. Enable the categories you want to show:
    • Necessary: Always enabled, pre-checked for visitors
    • Analytics: Optional, requires explicit consent
    • Marketing: Optional, requires explicit consent
    • Preferences: Optional, requires explicit consent
  3. Translate category names and descriptions into Brazilian Portuguese for clarity
  4. Assign cookies to appropriate categories (cookies assigned globally apply here unless overridden)

LGPD, like GDPR, generally requires opt-in consent for non-essential cookies, so configure your consent type appropriately in the next step.

Step 5: Set Consent Type

Choose how consent is obtained from Brazilian visitors:

  • Opt-in (Explicit Consent): Recommended for LGPD compliance. No non-essential cookies load until the visitor clicks Accept or enables specific categories.
  • Opt-out (Implied Consent): Cookies load immediately, but visitors can opt out. Not recommended for LGPD, which generally requires opt-in.
  • Notice Only: Informational banner with no consent requirement. Not appropriate for LGPD compliance.

Select Opt-in for LGPD compliance.

Step 6: Configure Display Controls (Optional)

Customize when and how the banner appears to Brazilian visitors:

  • Display Delay: Wait 2-3 seconds before showing the banner, reducing immediate interruption
  • Scroll Trigger: Show banner after visitors scroll 20% of the page, indicating engagement
  • Page Lock: Enable to prevent page interaction until consent is provided, ensuring compliance
  • Exit Intent: Display banner when visitors attempt to leave without consenting

Display controls can be configured per country rule, allowing different approaches for different regions.

Step 7: Save and Test

  1. Click Save Changes at the bottom of the page
  2. Clear all caches (WordPress cache, page cache, CDN cache)
  3. Test the configuration using a VPN or proxy set to Brazil
  4. Verify the Brazilian Portuguese banner appears with correct text and behavior

Your Brazil-specific consent rule is now active. Brazilian visitors will see this custom configuration instead of your default banner.

Managing Multiple Country Rules

As your international presence grows, you’ll likely create multiple country-specific rules. Effective management ensures consistent compliance across all jurisdictions.

Organizing Rules

Use clear, consistent naming conventions for country rules:

  • Geographic + Legal Framework: “Brazil – LGPD”, “Switzerland – FADP”, “Japan – APPI”
  • Geographic + Language: “Canada – French”, “Canada – English”
  • Geographic + Purpose: “UK – Post-Brexit”, “China – Restricted”

Consistent naming helps you quickly identify and manage rules as your list grows.

Rule Priority and Conflicts

Remember the rule hierarchy when creating multiple location rules:

  1. US state rules (most specific)
  2. Country rules
  3. EU/EEA rules
  4. Default rule (least specific)

If you create both a country rule for France and an EU rule, French visitors will see the country rule because it’s more specific. Only create country rules within the EU if you need country-specific variations beyond the EU-wide rule.

Cloning Rules for Efficiency

When creating similar rules for multiple countries, use the clone feature:

  1. Find the rule you want to duplicate in the Geolocation rules list
  2. Click Clone next to that rule
  3. Update the country selection and rule name
  4. Modify any country-specific details (language, specific regulations)
  5. Save the cloned rule

This is particularly useful when creating multiple language variations of the same compliance approach.

Advanced Country Targeting Strategies

Beyond basic country rules, advanced strategies help you manage complex international compliance scenarios.

Language-Based Targeting

Countries with multiple official languages benefit from language-specific consent banners.

Example: Canada (English and French)

Create two country rules for Canada, using different configurations for English and French-speaking regions:

  1. Create “Canada – English” rule with English text
  2. Create “Canada – French” rule with French text

Since DigiConsent can only apply one rule per country, you’ll need to choose which to use as default. Alternatively, create a bilingual banner showing both languages, which is often the most practical approach for multilingual countries.

Progressive Consent Approaches

Some countries have evolving privacy regulations. Implement progressive consent that can be easily updated as laws change.

Example: Australia (Privacy Act with ongoing reforms)

Australia’s Privacy Act is under review for potential GDPR-like reforms. Create an Australian rule that:

  • Currently uses opt-out consent (matching current law)
  • Is clearly documented for easy upgrade to opt-in when reforms pass
  • Includes forward-looking banner text explaining privacy commitments beyond legal minimums

When law changes, simply edit the existing rule to strengthen consent requirements without creating entirely new configurations.

Regional Trade Bloc Approach

Some countries participate in trade blocs with harmonized privacy regulations. Create similar rules for bloc members.

Example: APEC Privacy Framework Countries

While APEC member countries don’t have identical privacy laws, they share common principles. Create similar (but country-specific) rules for major APEC economies like Australia, Japan, Singapore, and South Korea that reflect their shared privacy framework while accommodating national variations.

Country-Specific Compliance Examples

Practical examples for countries with notable privacy laws help you understand how to configure country rules for real-world compliance.

Switzerland (FADP)

Switzerland has the Federal Act on Data Protection (FADP), which is GDPR-like but distinct.

Configuration:

  • Country: Switzerland
  • Consent Type: Opt-in (explicit consent for non-essential cookies)
  • Language: Offer German, French, Italian, and Romansh options (or multilingual banner)
  • Cookie Categories: Necessary (pre-checked), Analytics, Marketing, Preferences (all opt-in)
  • Banner Message: Explain cookie usage clearly, reference FADP compliance, link to privacy policy

United Kingdom (UK GDPR + PECR)

Post-Brexit UK maintains GDPR-equivalent regulations plus PECR (Privacy and Electronic Communications Regulations).

Configuration:

  • Country: United Kingdom
  • Consent Type: Opt-in (UK GDPR requires explicit consent)
  • Language: English
  • Cookie Categories: Strictly Necessary (pre-checked), Performance, Functionality, Targeting (all opt-in)
  • Banner Message: Reference UK GDPR and PECR compliance, explain cookie purposes clearly
  • Special Note: Ensure cookie information is easily accessible and written in plain English (ICO guidance emphasizes clarity)

Japan (APPI)

Japan’s Act on the Protection of Personal Information (APPI) has specific requirements for handling personal data.

Configuration:

  • Country: Japan
  • Consent Type: Opt-in for sensitive personal data; opt-out may be acceptable for less sensitive cookies (consult legal counsel)
  • Language: Japanese
  • Cookie Categories: Clear categorization with Japanese explanations
  • Banner Message: Japanese text explaining purpose, data usage, and rights under APPI
  • Cultural Consideration: Japanese users value detailed information and transparency—provide comprehensive explanations

Canada (PIPEDA)

Canada’s Personal Information Protection and Electronic Documents Act (PIPEDA) governs private sector data protection.

Configuration:

  • Country: Canada
  • Consent Type: Opt-out is often acceptable for non-sensitive cookies; opt-in for more sensitive tracking
  • Language: Bilingual (English and French) or separate rules per language
  • Cookie Categories: Essential (pre-checked), Analytics, Advertising (opt-out available)
  • Banner Message: Bilingual text or language toggle, explain PIPEDA compliance, emphasize transparency

Testing Country-Specific Rules

Proper testing ensures your country rules work correctly and display appropriate content to targeted visitors.

Testing Methods

Method 1: VPN Testing

The most reliable testing method uses a VPN service to simulate visitors from different countries:

  1. Subscribe to a reputable VPN service with servers in your target countries
  2. Connect to a server in the country you want to test (e.g., Brazil)
  3. Open an incognito/private browser window (to avoid cached consent preferences)
  4. Visit your website
  5. Verify the country-specific banner appears with correct language, content, and behavior
  6. Test all banner interactions (Accept, Reject, Manage Preferences)
  7. Disconnect VPN and test default configuration still works for non-targeted locations

Method 2: Browser Developer Tools Override

Some browser developer tools and extensions allow geolocation spoofing, though this is less reliable than VPN testing:

  1. Install a geolocation spoofing browser extension
  2. Set your spoofed location to the target country
  3. Clear cookies and cache
  4. Visit your website in incognito mode
  5. Verify the banner appears correctly

Note: Some geolocation methods rely on IP addresses rather than browser geolocation API, making this method less reliable.

Method 3: Testing Mode Override (Development)

DigiConsent Pro may include a testing mode that forces specific country detection for development purposes. Check plugin documentation for availability.

Testing Checklist

For each country rule, verify:

  • Banner appears to visitors from the target country
  • Banner does NOT appear to visitors from other countries (they see appropriate rules instead)
  • Text displays in the correct language without translation errors
  • Cookie categories are correctly labeled and translated
  • Accept/Reject/Manage buttons function properly
  • Consent type (opt-in/opt-out) behaves as configured
  • Display controls (delay, scroll trigger, page lock) work as expected
  • Cookies are blocked/allowed correctly based on consent choices
  • Consent preferences are saved and persist across page loads
  • Privacy policy link directs to the correct page

Maintaining Country Rules

Country-specific privacy laws evolve. Maintain your rules to ensure ongoing compliance.

Monitoring Regulatory Changes

Stay informed about privacy law changes in countries where you have specific rules:

  • Subscribe to privacy law newsletters and updates from international law firms
  • Monitor regulatory authority websites in your target countries
  • Set calendar reminders to review country rules quarterly
  • Join privacy professional communities that share regulatory updates

Updating Rules

When regulations change:

  1. Review the specific regulatory changes and their implications
  2. Determine if your existing rule needs updates or complete reconfiguration
  3. Make necessary changes to consent type, categories, or banner text
  4. Test thoroughly before deploying changes
  5. Document the changes and their regulatory justification
  6. Clear all caches after updates

Archiving Old Configurations

Maintain records of previous country rule configurations:

  • Take screenshots before making significant changes
  • Document the date, reason, and nature of each change
  • Keep records for at least as long as your data retention period (often 2-7 years depending on jurisdiction)

This documentation proves compliance efforts if regulatory questions arise.

Troubleshooting Country Targeting Issues

Wrong Banner Appears for Country

If visitors from a specific country see the wrong banner:

  • Check rule priority: A more specific rule (like US state rule) might be overriding your country rule
  • Verify country selection: Ensure you selected the correct country in the rule configuration
  • Test geolocation detection: Use a VPN to confirm geolocation is working correctly
  • Clear caches: Cached banners might show old configurations
  • Check rule status: Ensure the rule is enabled/active

Geolocation Not Detecting Country

If country detection fails completely:

  • Verify geolocation service: Confirm the geolocation database is accessible and up to date
  • Check hosting restrictions: Some hosts block external geolocation API calls
  • Test with multiple IPs: Try different networks to rule out specific IP database issues
  • Review error logs: Check WordPress debug logs for geolocation errors

Translation or Character Encoding Issues

If translated text appears corrupted:

  • Verify UTF-8 encoding: Ensure your database and WordPress installation use UTF-8 character encoding
  • Test special characters: Some characters (Chinese, Arabic, Cyrillic) require proper font support
  • Check font availability: Ensure your theme’s fonts support the character sets you’re using
  • Validate translations: Have native speakers verify translations display correctly

Next Steps

With country targeting configured, explore related Pro features:

  • EU Targeting Configuration: Set up automatic EU/EEA detection for GDPR compliance
  • US State Targeting: Implement state-specific rules for CPRA, VCDPA, and other US privacy laws
  • Location-Based Rules: Learn advanced strategies for managing complex multi-location consent scenarios

Country targeting gives you precise control over consent management on a nation-by-nation basis, ensuring you meet each country’s specific legal requirements while optimizing user experience for visitors worldwide.