Skip to main content
Add Invoca call and conversation data to VWO Data360 for a complete view of online and offline touchpoints.
If your organization uses VWO Data360 for customer experience analytics, A/B testing, optimization, or consumer journey analytics, this integration sends call and conversation insights to VWO in real time using their Offline Conversions API. It can help you identify digital leakage points, connect offline conversions to your online conversion funnels, and use offline data for segmentation and optimization.

​
Step 1: Prepare your VWO account to receive Invoca data

VWO’s Offline Conversions API must be enabled at the account level, as part of the Data360 package. Before recording offline conversions:
  1. Create a custom event in the Data360 module for each call or Signal you want to track.
  2. Create a metric using those events.
  3. Create and start a campaign using that metric.
Note the custom event names you create — you’ll need them in Step 2.

​
Step 2: Configure the VWO integration tile in Invoca

  1. In the sidebar, click Integrations, then Manage Integrations, then the VWO tile. If it’s “Ready to Integrate,” click Integrate; otherwise contact your Invoca CSM.
  2. Create a collection: enter an Invoca Friendly Name for this VWO project, and your VWO Account Number (found in the upper right of your VWO view).
  3. Create an Action to trigger data flow — one for each transaction type you want to send:
    • Invoca Friendly Name — for example, “VWO Invoca Calls” or “VWO Invoca [Signal Name].”
    • Profile or Campaign — filter which calls/Signals send, if applicable.
    • Triggered By — All Calls, or a specific Signal.
    • Event Name — must match the custom event name you created in VWO.
    • Additional Parameters — optionally send custom properties, using hard-coded or dynamic (substitution token) values.
  4. Click Integrate.

​
Step 3: Capture the VWO ID

  1. Click the gear icon, then Invoca Tags, and find your Tag.
  2. Open the Revision History tab and create a new draft.
  3. Find the VWO ID parameter in the Marketing Data section, set Data Source Type to DataLayer, enable it, and enter _vwo_uuid as the Data Source Name.
  4. Test your changes, then click Save & Go Live. If the VWO cookie sets after the Invoca Tag runs, use the “Re-run attribution” setting (5 seconds is a reasonable starting point) and publish to all Tags if you have more than one.

​
Step 4: Validate your integration in Invoca

  1. In Invoca, click Integrations, then Manage Integrations, then the VWO tile, then the name of your Action.
  2. Review the Delivery Details chart, showing successes (green) and errors (red) by day for the last 30 days. Click Delivery History for individual requests and responses.

​
Step 5: Validate data in VWO

Use the audit tab in your VWO view to spot-check the Invoca webhook payloads and confirm the right data is flowing.

​
FAQs

How does VWO attribute an event? Using the VWO UUID to tie the event to a tracked digital session — static calls won’t attribute. Invoca reports the call start time for call transactions and rule-based/AI Signals, or the Signal’s “occurred at” time (falling back to start time) for imported Signals. If the reported time falls after the session, the event won’t associate with session-level experiments. How is data sent to VWO? Using the real-time Offline Conversions API — VWO typically surfaces the data within 10 minutes of call end. What data is sent to VWO? No PII is sent. Fields include the VWO UUID, the call’s start timestamp, phone type (Landline or Mobile), and the Calling Page value.

​
Where to go next

Last modified on September 25, 2026