Mastering Jasper PIM involves careful planning and attention to detail. Follow these best practices to avoid common pitfalls and ensure smooth operation, especially in an enterprise environment.
✅ DOs
1. Check the Jobs Table Before Running Batch Actions
Verify that no other jobs are in progress to avoid conflicts, duplicate uploads, or overwrite errors.
2. Consider the Capacity of Your Environment
Even dedicated environments have limits. Stagger mass syncs, imports, and updates to prevent system overload.
3. Use Communication Logs for Troubleshooting
Always check the Communication Logs and review the Debug column when sync issues arise. Most errors originate from external platforms.
4. Validate CSV Files Before Uploading
Run a test import with a single product first. Validate structure, slugs, and data to avoid widespread errors.
5. Verify Asset Links Are Public
Ensure any asset URLs (uploaded via CSV, UI, or API) are public. Private links will cause failed uploads.
6. Assign Slugs to Attribute Fields in CSV Profiles
Every attribute field must have a slug for the importer to recognize it. Missing slugs prevent saving and importing.
7. Save API Keys Immediately
You can only view an API key once. Save it securely when created—there’s no way to recover it afterward.
8. Refer to the Knowledge Base for Unfamiliar Tasks
When in doubt, use the [Knowledge Base] or contact Jasper Support for guidance and training.
9. Ensure Correct Scopes When Creating API Keys
API key scopes define access. Incorrect scopes will block product updates or channel syncs.
10. Enable ‘Auto Categories’ for Auto Categorization
In the category’s details tab, turn on Auto Categories before saving to activate this feature.
11. Allow Time for Auto Categories to Update
Wait 1–2 minutes after enabling auto categorization. The process runs via CRON and needs time to apply.
12. Check the Scheduled Content Tab Before Making Changes
Avoid redundant updates by verifying if changes are already scheduled for deployment.
13. Save Frequent Search Filters as Projects
Use projects to save commonly used filters. Great for quick access, independent of workflows.
14. Verify Product Publication Status Before Syncing
Ensure the product is marked as Published before syncing. This is the final checkpoint before data pushes live.
🚫 DON'Ts
1. Don't Run Multiple Intensive Processes Simultaneously
Avoid launching multiple mass jobs (syncs, imports, updates) at once—this can cause timeouts or performance drops.
2. Don't Overlook Communication Logs for Sync Issues
Missing the logs means missing critical error data. Always check logs first during troubleshooting.
3. Don't Skip CSV Validation
Skipping test uploads risks bulk data issues. Always validate CSV files and test first.
4. Don't Upload Non-Public Asset Links
Public links are required for assets to import successfully. Non-public URLs will be rejected.
5. Don't Forget to Assign Slugs in CSV Profiles
Slugs are required for attribute mapping. If missing, imports will fail, delaying progress.
6. Don't Misplace API Keys
Once created, API keys are no longer visible. If lost, you’ll need to generate a new one—plan accordingly.
7. Don't Proceed Without Reviewing the Knowledge Base
Unfamiliar with a task? Check the Knowledge Base or get training before proceeding.
8. Don't Assign Incorrect Scopes to API Keys
Wrong scopes = failed updates. Double-check when generating channel-specific keys.
9. Don't Forget to Turn On 'Auto Categories'
Auto categorization won’t work unless it’s explicitly enabled in the category setup.
10. Don't Check Auto Categories Immediately
Auto categories take 1–2 minutes to update. Don’t assume failure too soon—just give it time.
11. Don't Duplicate Scheduled Content Updates
Redundant changes can create confusion. Always verify scheduled updates before submitting new ones.
12. Don't Run Bulk Actions Without Verifying Filters
Double-check your filters! Running bulk actions on the wrong product set can cause irreversible changes.
13. Don't Attempt to Sync Unpublished Products
Even if enabled on a channel, products must be marked Published to sync successfully.