Skip to main content

SalesExec ClickPoint Integration Request Tab

Chris Arenas avatar
Written by Chris Arenas
Updated over 2 weeks ago

Overview

The ClickPoint Integration Request Tab in LeadExec allows you to configure the request body for deliveries. This is where you will add the schema outlined in the client’s posting documentation.

⚠️ Important: The SalesExec ClickPoint Integration lead receiver only accepts XML and URL-encoded requests. JSON payloads are not supported.

Using the dropdown menu, you can replace the lead field values in the schema with delivery method tags. These tags auto-populate the field values in the delivery based on your configuration.


Key Functionality

  • Schema Configuration: Add the XML schema as per the client’s specifications, or configure for URL-encoded delivery if required.

  • Field Mapping: Use the dropdown menu to insert delivery method tags that correspond to the lead fields.

  • Auto-Population: Tags will auto-populate the field values in the delivery based on the configured settings.

  • Content-Type Consideration: If you are creating an HTTP Post delivery using the URL-encoded content type, you may not need to add a full XML schema.

How to Use This Feature

  1. Navigate to the Request Tab
    In your LeadExec account, go to the ClickPoint Integration section and select the Request tab.

  2. Add Schema (XML only)
    Input the XML schema provided by the client. For URL-encoded deliveries, follow the client’s posting instructions instead of adding an XML schema.

  3. Map Lead Fields
    Utilize the dropdown menu to insert delivery method tags that correspond to the lead fields.

  4. Auto-Populate Fields
    The tags will auto-populate the field values in the delivery based on the configured settings.

  5. Save Settings
    After configuring the request body, click Save to apply the settings.

Best Practices

  • Client Documentation: Always refer to the client’s technical documentation to ensure the correct schema and field mappings are used.

  • Field Validation: Ensure that all required fields are included and correctly mapped to prevent data errors.

  • Testing: Test the configuration in a sandbox environment before applying it to production to ensure proper functionality.

Troubleshooting

  • Missing Fields: If certain fields are missing in the delivery, verify that they are included in the schema and correctly mapped.

  • Data Formatting Issues: If data appears incorrectly formatted, check the schema and confirm it matches the client’s expectations.

  • Delivery Failures: If deliveries fail, review the schema, field mappings, and ensure the request is sent as XML or URL-encoded (not JSON).

Did this answer your question?