Skip to main content
Connect Invoca to Dynamic Yield to send calls and Signals, so you can understand which experiments and personalizations are driving calls and call outcomes.
Before you begin: You’ll need access to your Dynamic Yield account settings to generate a server-side API key.

Step 1: Get your Dynamic Yield API key

  1. In Dynamic Yield, go to Settings > API Keys.
  2. Create a new server-side API key and note it down — you’ll need it in the next step.

Step 2: Set up the integration in Invoca

  1. In the Invoca sidebar, click Integrations, then Manage Integrations.
  2. Click the Dynamic Yield tile. If your account shows “Learn More” instead, contact your Invoca account team to enable the integration.
  3. Enter a friendly name to identify your Dynamic Yield account.
  4. Enter the Dynamic Yield API Key from Step 1.

Create an Action

An Action sends a call or a specific Signal to Dynamic Yield. This integration offers two Action types:
  • Track Events (with IP Address): uses the Dynamic Yield User ID and Session ID for attribution, and includes the caller’s IP address for geolocation targeting and audience building.
  • Track Events (without IP Address): uses the same IDs for attribution, but excludes the IP address for stricter privacy compliance.
  1. Enter a friendly name for the Action — include “Call” or the Signal name, plus “with IP” or “without IP,” to distinguish between Actions.
  2. Optionally filter which calls or Signals to send by choosing a Profile or Campaign.
  3. Under Triggered By, choose All Calls to report every call, or Signal to report a specific Signal.
  4. Enter a Custom Event Name — this is the name that appears in Dynamic Yield reports (for example, “Invoca Call” or “Appointment Set”).
  5. Enter a Default Value — a fallback revenue amount for this event. If a Signal includes revenue, that value overrides the default. Enter 0 if you don’t want a default value.
  6. Enter a Currency Code in 3-letter ISO 4217 format. If left blank, Invoca sends “USD” by default.
  7. Click Save. Repeat for each transaction type you want to report.

Step 3: Configure your Invoca Tag(s) to capture Dynamic Yield IDs

  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. In the Marketing Data section, find the Dynamic Yield User ID (_dyid) parameter. Set its Data Source Type to Cookie, enable it, and enter _dyid as the Data Source Name.
  4. Find the Dynamic Yield Session ID (_dyjsession) parameter. Set its Data Source Type to Cookie, enable it, and enter _dyjsession as the Data Source Name.
  5. If you’re using the “with IP Address” Action, also enable the IP Address toggle in the Marketing Data section.
  6. Test your changes to confirm everything works, then click Save & Go Live.
If you have multiple Invoca Tags, publish the update to each.

Validate that events are reaching Dynamic Yield

  1. In Invoca, click Integrations, then Manage Integrations.
  2. Click the Dynamic Yield tile, then the name of the Action you created.
  3. Review the Delivery Details chart, which shows successes (green) and errors (red) by day for the last 30 days. If you see errors, click the Delivery History tab to see individual requests and responses.
  4. In Dynamic Yield, use Experience API Logs to verify events in near real-time.

FAQ

What’s the difference between the two Actions? They control what level of user data is sent. “With IP Address” sends the caller’s IP for geolocation and audience building; “without IP Address” omits it for stricter privacy compliance. What are the _dyid and _dyjsession cookies? These are standard first-party cookies the Dynamic Yield script places on your site to track users and sessions. The Invoca Tag reads these cookie values to pass to the API for attribution. How can I see the data Invoca sends to Dynamic Yield? Open an Action in Invoca and check the Delivery History tab — expand a row to see the full JSON payload sent for that call or Signal. What data is shared with Dynamic Yield?
  • Custom Event Name
  • Dynamic Yield User ID (required)
  • Dynamic Yield Session ID
  • IP address (only with the “with IP Address” Action)
  • Currency
  • Revenue or default value
  • Partner Unique ID or Transaction ID, as the unique transaction identifier
How does Invoca send data to Dynamic Yield? Invoca uses the Dynamic Yield Events API, sending a server-to-server POST request.

Where to go next

Last modified on September 24, 2026