Preparing for a Go-Live on win//p

Owned by Sylvain Paillard
Last updated: Sept 27, 2023
3 min read

Launching a new implementation on the Boxalino Winning Interactions Platform, or win//p, is a crucial step. This platform, designed for intelligent data management and analytics, can be invaluable for businesses. However, a successful deployment necessitates proper planning and a solid checklist to ensure that nothing is overlooked.

Here is a detailed checklist to guide you through your go-live preparation for win//p:

Data Export and Indexing

1. Verify Data Exports

  • Task: Ensure that all data exports are functioning as expected and sending production data into the production index.

  • Why: To make sure that your application uses the most current and relevant data.

  • How: Test the export process, review the data in the production index, and make sure that all your planned data synchronization are going through successfully (full, delta and instant).

Production Credentials

2. Use Correct Production Credentials

  • Task: Verify that your production setup utilizes the proper production credentials—both apikey and apisecret.

  • Why: Using test credentials could result in limited functionality and potential issues.

  • How: Update your configuration files or environment variables to use the production apikey and apisecret.

3. Set Test and Dev Parameters Appropriately

  • Task: Make sure that the test and dev parameters are set to test=false and dev=false.

  • Why: This ensures that you are not in testing mode during production.

  • How: Check and update your API calls or configuration settings to use test=false and dev=false.

Server Requests

4. Server-to-Server Requests to the Correct Domain

  • Task: Confirm that all server-to-server requests in the production environment are directed to main.bx-cloud.com.

  • Why: To ensure that your server requests go to the appropriate, live endpoint.

  • How: Update the endpoint URLs in your codebase to target main.bx-cloud.com.
    Keep using r-st.bx-cloud.com for testing and staging environments.

5. API request Endpoint with profileId parameter

  • Task: Confirm that all server-to-server requests in the production environment include the profileId=[PROFILE_ID] parameter.

  • Why: To ensure that your server requests are load-balanced throughout all Boxalino live server nodes (otherwise, they will all go to the same server node).

  • How: Update the endpoint URLs in your codebase to target include a “profileId” parameter (with the same value as the “profileId” field of your API request) either

    • directly in the URL:
      https://main.bx-cloud.com/narrative/[ACCOUNT]/api/1?profileId=[PROFILE_ID]

    • or as an HTTP-Header in the parameter name X-BX-PROFILEID

Tracking Requests

6. Direct Tracking Requests to the Correct Domain

  • Task: Make sure that all your tracking requests are directed to track.bx-cloud.com.

  • Why: This is the designated endpoint for production-level tracking.

  • How: Update the tracking request URLs in your codebase to point to track.bx-cloud.com.
    Continue to use r-st.bx-cloud.com for testing and staging environments.

Search Autocomplete

7. Use the Special Sub-Domain for Search Autocomplete

  • Task: For client-side Search Autocomplete requests, use the special sub-domain provided by Boxalino to avoid issues with ad blockers.

  • Why: Some ad blockers might mistakenly block legitimate search autocomplete functions.

  • How: Implement the special sub-domain in your client-side code for Search Autocomplete.

Final Steps

  • Perform end-to-end tests: Before going live, conduct comprehensive tests to verify that all systems are working as intended.

  • Monitor closely after go-live: Keep an eye on logs to promptly identify and fix any unforeseen issues.

  • Check statistics after go-live: Review analytics to promptly identify and fix potential tracking issues.

By following this checklist diligently, you can minimize risks and ensure a smooth transition as you go live on the win//p. Good luck!