Skip to main content
Two ways to automate posting conversion data into Invoca beyond manual Signal uploads: SFTP file drops and the Signal API.
You can post conversion call data manually using Upload Signal Records under Signals in the platform, but there are two ways to automate this process instead.

​
1. SFTP for Signal File Upload or Lookup Table

SFTP lets you upload Signal Files or Lookup Table files by placing them in a designated SFTP folder, set up either by you or by Invoca. Once a file lands in the folder, Invoca’s automated process retrieves and processes it every 6 hours. This is useful for streamlining Signal or Lookup Table uploads without manual UI work, and works well for customers without their own SFTP capability. Requirements:
  • SFTP server information (not required if Invoca hosts it)
  • Platform Super User name and email
  • For Signal File Upload: transaction_id, call_record_id, or call_start_time to identify the associated call
  • For Signal File Upload: data mapping fields (Signals or Marketing Data fields)
  • For Lookup Table: a primary key (required) and secondary key (optional)
  • For Lookup Table: Marketing Data fields to apply data to

​
2. Signal API

The Signal API applies Signals and/or Custom Data Fields to specific calls retrospectively, using references like Call Record ID, Transaction ID, or Call Start Time. This is useful when data needs to be applied from external systems that weren’t available during the call itself. Signals are boolean values (sale, quote, and so on); Custom Data Fields can hold any alphanumeric value (account type, customer quality score, and similar). A maximum of 100 API requests can be sent within a 60-second window. Custom Data Fields must already exist in your Marketing Data Dictionary before they can be applied via the API — a Signal’s field can be created on the fly, but Custom Data Fields cannot.

​
Where to go next

Last modified on September 25, 2026