Testing

Before going live with your integration, it is crucial to conduct thorough testing to ensure that data ingestion, processing, and the subsequent campaign and journey triggers work as expected. This section provides guidance on how to effectively test the system using sample files and what to check for after each file upload.

Creating Test Users

Start by creating a set of test users who are part of multiple segments, campaigns, and journeys. Ensure these users are designed to test various conditions and edge cases in your segmentation logic and campaign criteria.

Preparing Test Files

Construct several CSV sample files, each containing data relevant to the selected test users. The data should be varied to test the addition, updating, and removal of custom attributes, and to simulate different user behaviors and interactions that would trigger segment changes.

Uploading Test Files

Upload each sample file using the process outlined in the “Uploading Files via SFTP” section of this documentation. Ensure to monitor the system for any immediate feedback or errors upon upload.

Validation Checklist

After each file upload, conduct the following validation checks:

1. Custom Attribute Data

• Addition: Verify that new custom attribute data has been accurately added to the relevant user profiles.
• Update: Confirm that existing custom attribute data has been updated correctly.
• Removal: Check that the removal of custom attribute data is reflected in the user profiles.

2. Mobile Application Profile and User Profile Sync

• Validate that any changes in custom attributes are mirrored between the Mobile Application profile and the User Profile within the Pulsate platform.

3. Segment Updates

• Confirm that segments have been updated as expected. This includes:
  • Users being added to segments when they meet the criteria.
  • Users being removed from segments when they no longer meet the criteria.

4. Campaigns and Journeys Triggering

• Check that campaigns and journeys that should have been triggered based on segment changes have been delivered correctly.
• Validate that no campaigns or journeys are triggered during quiet hours if they are due to segment updates from data processing during those times.

5. Logs and Reporting

• Review logs, if available, for any discrepancies or errors during the data ingestion process.
• Use reporting tools within the Pulsate platform to confirm that user activity is recorded and attributed correctly.

Recommended Testing Practices

• Incremental Testing: Start with simple test cases and gradually introduce complexity.
• Documentation: Keep detailed records of each test case, including the expected outcomes and any discrepancies.
• Automation: If possible, automate the testing process for efficiency and consistency, especially if you expect frequent updates and changes to data.
• Cross-Functional Reviews: Involve stakeholders from different teams (e.g., development, marketing, data analytics) to review test cases and outcomes.

By meticulously testing your SFTP data uploads and the resulting processing by the Pulsate service, you can ensure that your users have a seamless experience with personalized content that resonates with their actions and attributes. Should you encounter any issues or have questions during the testing phase, please contact support@pulsatehq.com for assistance.