Connect Invoca and iSpot to share call outcomes for a more complete view into TV and streaming ad performance.iSpot.tv is a cross-platform TV and video advertising measurement company providing real-time analytics on ad performance. This guide walks through: getting your Site ID and API credentials from iSpot, creating an auth connection in Invoca, configuring the Invoca Tag to capture IP Address and User Agent, determining which outcomes to share, and submitting a support case to configure the data delivery.
Step 1: Get API credentials from iSpot
The integration delivers a file daily to iSpot’s “Upload Conversions” API endpoint, which requires client credentials authentication. Get your Client ID and Client Secret from iSpot, along with your iSpot Site ID (this will populate in the Site ID column of the daily file).Step 2: In Invoca, create the auth connection to iSpot
Note: you’ll need assistance from your Invoca representative for this section — contact them or success@invoca.com.- In Invoca, click Integrations in the sidebar.
- Click Manage Credentials.
- Click + New Credential.
- Enter a name (for example, “iSpot API Connection”).
- Select iSpot from the dropdown.
- Paste the Client ID provided by iSpot.
- Paste the Client Secret provided by iSpot.
- Enter
client_credentialsfor the Grant Type. - Click Authorize.
Step 3: Configure the Invoca Tag to capture IP Address and User Agent
iSpot uses IP Address and User Agent to attribute conversions to TV and video ad interactions — both are required fields. IP Address is considered PII — review your company’s policies before enabling it.- Click the gear icon, then Invoca Tags, and find your Tag.
- Open the Revision History tab and create a new draft, or continue an existing one.
- Enable the Capture IP Address and Capture User Agent toggles — Invoca will pass these to iSpot for attribution.
- Test your changes, then click Save & Go Live. Publish to all Invoca Tags if you have more than one.
Step 4: Determine outcomes and submit a support case
Decide whether to report Invoca Calls to iSpot, and which Signals are valuable to share — Invoca creates one Data Delivery for Calls and a second for the Signals you choose. Note: iSpot appends “web” to the outcome name it passes, so if you’re sending web-based conversions with the same name as your Invoca Signals, consider including “Invoca” in your custom data column to distinguish the two sources. iSpot also caps conversion names at 28 characters — double-check your Signal names, and flag any that run long so Invoca can truncate them. Submit a case via Invoca Community:- Subject line: “Request to create iSpot Data Delivery.”
- Case Reason: Automated Imports/Data Delivery.
- Sub-category: Data Delivery - NEW.
- In the text box: confirm you’ve created your iSpot auth credential (never share the Client ID or Client Secret in the case itself), provide your iSpot Site ID, and list the outcomes to share (for example, Invoca Calls plus the Appointment Set and Purchase Signals).