Test a Touchpoint

Use Test a Touchpoint to test and troubleshoot whether or not MXO is returning the correct responses for customers.

You can test responses based on an individual context, existing key, or existing TID. The test simulates which responses MXO returns for an individual customer on a given interaction point.

The response includes details about all capture and optimization points configured for the interaction point. If any optimization points are present, MXO also returns information about the content for those optimization points.
Important: Content is returned in Base64 format and should be decoded for review.

Where can you find the TID?

You can find the TID in the one__randomid cookie. The MXO tag sends the contents of this value back to MXO server with each request.

Example: one__randomid=29dbc7e2-227c-44a4-9847-ed77a5d79e9c

Test a touchpoint

  1. In MXO, go to Test & Publish > Test a Touchpoint.

  2. Complete the following fields to create the request:
    FieldDescription
    URIURL and interaction point path for the touchpoint you want to test. For example: http://www.mysite.co.uk/homepage
    TIDID of the customer for which the request is being made. This allows you to test that an individual customer is being shown the best content. You can either use a specific customer ID or leave the field blank to let MXO create a new customer ID. Typically, you would use either a TID or key in a test. Use both to connect the TID with a specific key.
    Use TID from my browserIf MXO detects a TID in your browser, you can choose to use it by activating this option.
    Customer KeyCustomer key associated with the customer for which the request is being made. You can either use a specific customer key or leave the field blank to not associate the customer to a customer key. Typically, you would use either a TID or key in a test. Use both to connect the TID with a specific key.
    Customer Key Name API name of the key with which the customer key should be associated.
    PropertiesCustomer and activity attributes that align with specific and wildcarded interaction points' attribute capture points. Click + Add Property to select as many properties as desired.
    SnapshotSnapshot you want to use for the test. This includes the snapshot of any changes currently 'in the works' and the snapshot of any changes currently on the launchpad.
    Media TypeOptional. Type of response to be returned. Select either JSON or XML. By default, this is set to JSON.
  3. Optional. Activate the Receive legacy response switch to ignore the dataMimeType in the request header and limit the response to one action per optimization point.
    Note: This setting mimics how the MXO tag code handles the interaction call. To mimic a direct API call, keep the Receive legacy response switch off.

  4. Click Execute to run the test.

MXO returns a response including details about all capture and optimization points configured for the interaction point. For example:Test a Touchpoint response example

Click Reset to clear all configured fields and restart the request.