> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pureclarity.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Using PureClarity During Development

> Best practices for implementing PureClarity in development, staging, and testing environments across all platforms

PureClarity supports various development workflows by providing dedicated environments for testing and development, ensuring your live environment remains clean and production-ready.

<Info>
  Development environments come with usage restrictions and fair use policies - sufficient for testing but limited to prevent production abuse.
</Info>

## Development Environment Benefits

### Isolated Testing

**Environment separation provides:**

* **Clean live environment** - No test products, orders, or activity
* **Safe development space** - Test features without affecting production
* **Realistic testing** - Full PureClarity functionality in staging
* **Data integrity** - Separate analytics and customer data

### Fair Use Policy

<Warning>
  Development stores are restricted to testing purposes only. Using them for production traffic violates terms of service and may result in access blocking.
</Warning>

**Allowed activities:**

* Feature testing and integration validation
* User acceptance testing (UAT)
* Performance testing with limited traffic
* Development team training

**Prohibited activities:**

* Production customer traffic
* High-volume load testing
* Revenue-generating activities
* Long-term production use

### Environment Identification

<Note>
  A banner at the top of PureClarity admin indicates when you're working in a staging or test environment.
</Note>

## Platform-Specific Implementation

### Shopify Development

**Automatic development recognition:**

* Stores with plan name "affiliate" skip plan selection
* Stores with plan name "partner\_test" get automatic setup
* No billing requirements for development stores

#### Agency Workflow Recommendations

<Tip>
  For agencies developing client stores: reinstall PureClarity when transferring ownership to ensure the client can use PureClarity in production.
</Tip>

**Transfer process:**

1. Complete development and testing with affiliate/partner\_test store
2. Prepare for client handover
3. Reinstall PureClarity on client's production account
4. Configure production settings and preferences
5. Transfer any custom configurations or campaigns

### Traditional Platform Setup

**Platforms:** Shopify, BigCommerce, Magento, WooCommerce, Custom

#### Dual Environment Strategy

**Recommended approach:**

1. **Staging signup** - Create account on development/staging site
2. **Production signup** - Create separate account on live site
3. **Separate access keys** - Maintain distinct API credentials
4. **Independent configuration** - Configure each environment separately

<Warning>
  Never use production access keys in staging environments - this can cause staging products to appear in live recommendations.
</Warning>

### Access Key Management

**Best practices:**

* **Environment-specific keys** - Use dedicated keys per environment
* **Secure storage** - Store keys securely in environment variables
* **Regular rotation** - Update keys when transitioning to production
* **Documentation** - Maintain clear records of which keys belong to which environment

## Development Workflow Integration

### Testing Phases

#### Stage 1: Initial Development

* Set up staging PureClarity account
* Configure basic integration
* Test core functionality
* Validate data feeds and API connections

#### Stage 2: Feature Testing

* Test recommendation engines
* Validate campaign functionality
* Check personalization features
* Verify analytics tracking

#### Stage 3: User Acceptance Testing

* Conduct UAT with limited test users
* Validate user experience flows
* Test GDPR compliance features
* Verify mobile responsiveness

#### Stage 4: Production Preparation

* Set up production PureClarity account
* Configure production access keys
* Transfer tested configurations
* Plan go-live strategy

### Configuration Transfer

<Tip>
  Document all staging configurations to streamline production setup and ensure consistency.
</Tip>

**Transfer checklist:**

* Campaign settings and templates
* Segment definitions and rules
* Zone placements and configurations
* Custom template designs
* Analytics and tracking setup

## Best Practices

### Environment Management

1. **Clear naming** - Use distinct names for staging/production accounts
2. **Regular cleanup** - Remove test data periodically
3. **Documentation** - Maintain environment setup guides
4. **Access control** - Limit staging access to development team

### Development Security

**Security considerations:**

* Never expose staging credentials in production code
* Use environment-specific configuration files
* Implement proper secret management
* Regular security audits of development environments

### Performance Testing

**Testing guidelines:**

* Use realistic but limited data volumes
* Test with representative user journeys
* Validate caching and performance optimizations
* Monitor resource usage during testing

<Note>
  For comprehensive load testing, coordinate with PureClarity support to ensure appropriate environment provisioning.
</Note>

## Troubleshooting Common Issues

### Cross-Environment Contamination

**Problem:** Production data appearing in staging
**Solution:** Verify access keys are environment-specific

### Development Account Limitations

**Problem:** Features not working in development
**Solution:** Check fair use policy compliance and environment restrictions

### Transfer Issues

**Problem:** Configurations not working after production deployment
**Solution:** Verify all settings transferred correctly and access keys updated

## Related Documentation

* [Platform Settings](/support/general/settings)
* [Environment Credentials](/integrations/magento/magento-2/environment-credentials)
* [Debug Toolbar](/support/general/debug-toolbar)
* [Support Policy](/support/general/support-policy)