Skip to main content
Share call and conversation data with Segment to build more complete customer profiles and activate that data across your other Destinations.
This integration uses Segment’s HTTP API Source to track events tied to a Segment anonymous visitor ID.

​
Step 1: Create an HTTP API Source in Segment

  1. Log in to Segment and go to Connections > Sources, then click + Add source.
  2. Select Event streams, click the HTTP API tile, then Add Source.
  3. Name your source (for example, “Invoca Data”).
You can also reuse an existing HTTP API Source if you want the same Destination flows — skip to Step 2 to get its Write Key.

​
Step 2: Get your Segment Write Key

  1. Open the HTTP API Source, go to Settings, then API Keys.
  2. Note your Write Key.

​
Step 3: Set up the integration in Invoca

  1. In the sidebar, click Integrations, then Manage Integrations, then the Segment tile.
  2. Enter a friendly name for your Segment Workspace.
  3. Encode your Write Key: go to base64encode.org, paste the Write Key, add a colon at the end, click Encode, then paste the resulting value into the Encoded Write Key field in Invoca. Click Next.

​
Create an Action

  1. Click Track Event Stream.
  2. Enter a friendly name for the Action (include “Call” or the Signal name).
  3. Optionally filter by Profile or Campaign.
  4. Under Triggered By, choose All Calls or Signal.
  5. Enter the Event Name — this is the exact name that will appear in Segment.
  6. Optionally enter an ISO 4217 currency code; defaults to USD.
  7. Optionally add custom fields under Additional Parameters using + Add Values — a hard-coded parameter name paired with either a hard-coded or dynamic (via the substitution picker) value.
  8. Click Save. Repeat for each transaction type you want to report.

​
Step 4: Configure your Invoca Tag to capture the Segment Visitor ID

  1. Click the gear icon, select Invoca Tags, and locate the Tag on your website.
  2. Open the Revision History tab and create a new draft, or continue an existing one.
  3. Find the Segment Visitor ID parameter in the Marketing Data section, set Data Source Type to Cookie, enable it, and enter ajs_anonymous_id as the Data Source Name.
  4. Test your changes, then click Save & Go Live. If the Segment tag loads after the Invoca Tag runs, enable “Re-Run Attribution” and adjust the timing — 5 seconds is a reasonable starting point.

​
Validate that events are reaching Segment

In Invoca: click Integrations > Manage Integrations, open the Segment tile, then the Action you created, and review the Delivery Details chart (green = success, red = error). Click Delivery History for individual request/response details. In Segment: go to Connections > Sources, find the Invoca source, and confirm events are being received. Once data is flowing, build a Connection from your Invoca Source to your other Destinations in Segment to put the data to work.

​
FAQs

Does Invoca pass Revenue and currency? Yes — the Invoca Revenue field is passed as the event Revenue, defaulting to USD unless customized in the Action. What fields does Invoca pass by default? Segment Visitor ID, Marketing Source, Marketing Campaign, Marketing Content, Marketing Medium, your specified event name, Call Duration, Promo Number Description, Destination Phone Number, Full Landing Page URL, Calling Page, Revenue, Currency, Timestamp, gclid, wbraid, gbraid, fbclid, Google Analytics Client ID, and the Invoca Call Record ID. How can I see the data Invoca sends? Open an Action’s Delivery History tab and expand a row to see exactly what was sent for that call or Signal. How does Invoca send data? Invoca uses Segment’s HTTP API Source.

​
Where to go next

Last modified on September 25, 2026