Adobe Analytics: Installation & User Guide

Connect Invoca to Adobe Analytics to tie each phone call to a caller’s Adobe Visitor ID, so call data and Signal insights show up alongside the rest of your marketing data.

​

Step 1: Prepare your Adobe Analytics report suite

1. Get your Report Suite ID and tracking code namespace. Follow Adobe’s documentation to find your tracking code namespace (the subdomain that appears before .sc.omtrdc.net) and your Report Suite ID. You’ll need both in Step 2.
2. Create a Success Event for Invoca calls — a Counter-type success event to track Invoca calls.
3. Create an eVar for the Invoca Call Record ID. Name it complete_call_id, set the variable type to a text string, and note the eVar number assigned to it.

​

Step 2: Set up the integration in Invoca

1. In the Invoca sidebar, click Integrations, then select Manage Integrations.
2. Click the Adobe Analytics 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 report suite — useful if you plan to connect multiple report suites.
4. Enter the tracking code subdomain from Step 1 in the Adobe Analytics Namespace field.
5. Enter the Report Suite ID from Step 1.

​

Create an Action

1. Enter a friendly name to distinguish this Action, such as “Invoca Calls to Adobe Analytics.”
2. Optionally, filter which calls or Signals to send by choosing a Profile or Campaign.
3. Enter the Adobe Success Event Name — the exact event and slot number you created in Step 1 (for example, event6 if you used slot 6).
4. Enter a Fallback URL. Adobe requires a page URL for every request; use this when Invoca can’t capture a calling page.
5. Enter the eVar Name for the Invoca Call Record ID (for example, eVar26).
6. Check Include events from “static” and “overflow” numbers only if you want to report events where Invoca didn’t capture an Experience Cloud Visitor ID for the call. Events without a Visitor ID won’t tie to a visitor or session.
7. Optionally, configure Additional Parameters or Context Data (see Step 4).
8. Click Save.

​

Step 3: Capture the Experience Cloud Visitor ID in Invoca

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. If creating a new draft, click New Draft, not New Tag.
3. Determine whether your Adobe Analytics implementation uses AppMeasurement or the Experience Platform Web SDK (Alloy). AppMeasurement typically shows network requests to omtrdc.net; Web SDK shows requests to adobedc.net.
4. If you use AppMeasurement: open the Advanced options and paste this into the Custom Code box, replacing the placeholder with your Adobe Organization ID (found in the URL after logging in to Adobe Admin Console):

options.integrations.adobeAnalytics = {
  username: "XXXXXXXXXXXXX@AdobeOrg",
};

return options;

5. If you use the Web SDK: in the Marketing Data section, find the Experience Cloud Visitor ID parameter, set its Data Source Type to JavaScript Data Layer, and enable it. Enter mcid as the Data Source Name. Then paste this into the Custom Code box:

try {
  alloy("getIdentity").then(function(result) {
    mcid = result.identity.ECID;
  });
} catch (error) {
  console.error('Adobe Error:', error);
}

return options;

6. Test your changes to confirm they work correctly.
7. Click Save & Go Live. If the Web SDK sets the Visitor ID after the Invoca Tag runs, enable Re-Run Attribution in the Tag and adjust the timing — 5 seconds is a reasonable starting point.
8. If you have multiple Invoca Tags, publish updates to each.

​

Step 4: Send additional parameters or context data (optional)

​

Step 5: Send call outcomes and events using Data Sources

1. In Adobe Analytics, enable Transaction ID Storage.
2. Create a Counter-type Success Event for each Signal you want to send.
3. In Admin > Data Sources, configure a Generic Data Source (Transaction ID) with a metric for each Signal, and a dimension for campaign tracking code.
4. In Data Sources > Manage, find your new Data Source and note its FTP credentials.
5. Download the Data Sources FTP template.
6. Contact your Invoca account team to request a new data delivery to Adobe Analytics. Include the Signal names, any filters you want applied, your report suite’s time zone, and the downloaded template.
7. Share your Adobe Analytics FTP credentials securely — for example, using a one-time secret link service, or by sharing the username and hostname in your request and the password by phone.

​

Step 6: Send call and caller metadata using Classifications

1. In Adobe Analytics, create Classifications based on the Invoca Call Record ID eVar from Step 1.
2. Create a text field for each data point you want to transfer. Invoca recommends transferring fewer than 30 fields total to reduce errors.
3. In Admin > Classification Importer, download the FTP template for your report suite and Invoca Call Record ID dataset.
4. Under Import File > FTP Import, note your FTP credentials.
5. Contact your Invoca account team to request the data delivery, including the field names, any filters, your report suite’s time zone, and the template.
6. Share your FTP credentials securely, as in Step 5.

​

Where to go next

• Adobe Experience Cloud: Integration Overview
• Can Invoca Send More Than 30 Data Fields in an Adobe Analytics Classifications Data Delivery?
• Do Signal Values Have to Be 1/0 in an Adobe Analytics Data Sources Data Delivery?
• Adobe Analytics Webhook Not Firing for Syndicated Calls