Define Third-Party Profile | Vantage CX - 1.4 - Defining a Third-Party Profile - Vantage Customer Experience

Vantage Customer Experience User Guide

Vantage Customer Experience
Release Number
Release Date
June 2021
Content Type
User Guide
Publication ID
English (United States)
  1. Select "" > Real-time Decisioning > Third-party sources.
  2. Select Create New.
  3. Complete the name and description, then identify the location and HTTP location of the third-party data.
    Setting Value

    Enter the web address for the third-party service in the form http://server:port. Vantage CX uses this address when making the call to the third-party application to retrieve the third-party data.

    HTTP Method

    Select either GET or POST. Most implementations use GET.

  4. Select Create.
  5. [Optional] Complete the following settings.
    Setting Value


    User name for basic authentication to the third-party application.


    Password for basic authentication to the third-party application.

    Infer Unmapped Attributes

    This option allows Vantage CX to use attribute data from a third-party source in criteria, even when no attribute has been generated. The inferred/unmapped values are available during the current session and are discarded after the session ends.

    Inferred/unmapped attribute values are treated as strings.

    Unless you are using the inferred/unmapped attribute values in criterion expressions, there is no reason to select this option. It is important to understand that inferred/unmapped attributes do not become part of the Vantage CX configuration, so those attributes do not appear as attributes in the user interface.You can generate any attributes you want Vantage CX to use when refining its decisioning algorithm.

    You might choose to use this option if you know that attributes will be included in the third-party data, and you want to include that data in rule expressions.

    To use the inferred/unmapped attribute in a rule expression, use the format tpp_name.profile.tpp_attribute, where tpp_name is the name of the third-party profile and tpp_attribute is the name of the data item from the third-party application XSD or JSON. The value tpp_attribute is the name that the attribute would have been given if it had been generated.

  6. [Optional] Select Add Key Value Pair + to add additional keys.
    Most likely, the URL parameters will be authentication tokens and some value like a customer ID that Vantage CX uses to identify which third-party profile to retrieve.

    You can specify external key data using the external key format ${externalKey} for the key. If you specify a value that will not be mapped to an external key, then the parameter value is free form; for example, 65, someAuthToken, and so on.

  7. Select Actions > Import attributes to load the XSD or JSON sample data file.
    For more information about these files, see Understanding the Required Customer Data Formats.
    Setting Value
    URL Specify the file's location.

    In some cases, the third-party’s security policy prevents the URL choice from calling the XSD or JSON sample data file successfully. If the third-party application is in a different domain from the domain where Vantage CX is located, then the third-party application must have a publicly available crossdomain.xml file at the root of its domain. For example, if you are trying to access the XSD file, then there must be a crossdomain.xml file at the root of the domain at that allows applications to call the third-party service. If you cannot call the XSD or JSON sample data from its URL, download a copy of the document to your local machine and select File to upload it.

    Vantage CX examines the document content to determine whether the file is an XSD or JSON sample data file regardless of the file's extension.
  8. Select Create Attributes +.

    Vantage CX reads the XSD or JSON sample data file and displays a list of potential attributes in the order in which they were encountered in the document by attribute name. The list includes any attributes that already exist and all new ones generated from the document. A large XSD or JSON sample data file can contain many elements and thus many potential attributes, so the list can be very long.

    The list shows the attribute name, its data type, the item in the XSD or JSON sample data file that the attribute maps to, whether the attribute can have multiple values, and whether the attribute exists in the current third-party profile (that is, the attributes have already been created). If this is the first time you have created tags for this third-party profile, then all the values in the Exists column are False.

    Attributes must be unique within the attribute category. If the XSD or JSON file has multiple attributes with the same name, the name of the element within which they are enclosed is used to modify the name and distinguish between them. Also, if the attribute already exists with a different data type, it is not updated.

    If you choose, you can define the rest of the third-party profile and create attributes later. To avoid slow response times, do not enable the third-party profile until you have generated its attributes; otherwise, Vantage CX attempts to map the data to attributes that do not exist.
  9. Select each potential attribute that you want to generate.
    You must select at least one attribute.
  10. Select Add Selected.
    Vantage CX creates new attributes in the third-party profile. After Vantage CX generates attributes for the third-party profile, the attributes have the owner Customer.

    By default, the name of the generated attribute category is the same as the name of the third-party profile. This attribute category contains the simple attributes. Complex attributes have their own complex attribute categories.

    Attributes associated with a third-party profile can be edited like any other attribute.