Calls Aren't Routing Correctly via Lookup Table

A misrouted or dropped call from a Lookup Table is usually a Lookup Field mapping problem — here’s what to check.

​

Symptoms

• Calls drop shortly after being placed.
• Calls aren’t routing as expected.

​

Cause

​

Resolution

1. Field no longer available. If you delete a Marketing Data Field or Signal, or change its API name, the Lookup Table’s ability to route calls or append data can break.
2. Incorrect Marketing Data Field formatting. Make sure the Marketing Data Field’s API name matches the header name in your Lookup Table exactly — don’t use the field’s Friendly Name as a spreadsheet header. When uploading a file, select Download Template during the Upload File step; it includes both friendly names and API names, so you don’t need to enter headers manually.
3. Data formatting and accuracy. Small formatting errors can disrupt this feature:
   • Leading zeros in zip codes can get dropped by spreadsheet software.
   • URLs need to match the format Invoca actually captures (for example, https://www.example.com vs. www.example.com).
4. Naming conventions. Avoid giving a Marketing Data Field the same name as a Signal or an Invoca General Parameter. When names conflict, Invoca prioritizes Signal values over General Parameter values, which in turn take precedence over Marketing Data Field values. For example, if you create a Signal named “revenue,” it registers as True/False — but if you also expect the General Parameter “Revenue (Sale Amount)” to return a dollar amount under that same name, the Signal value takes precedence instead, which can cause unexpected results.
5. API name updates. Changing a Marketing Data Field’s API name can break existing API calls, webhooks, or apps using that field, and can disrupt data appending to objects like Campaigns, Phone Numbers, or Profiles.

​

Where to go next

• Lookup Table Routing