> ## Documentation Index
> Fetch the complete documentation index at: https://docs.invoca.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Adobe Experience Platform (AEP): Integration Guide

> Connect Invoca to Adobe Experience Platform (AEP) to send call and conversation data to the Edge Network Server API, so you can build more complete customer profiles and share Invoca insights with AEP destinations.

**Before you begin:** You need administrator access to your Adobe Experience Platform organization and Adobe Developer Console, plus permission to edit Marketing Data fields, Invoca Tags, and integrations in your Invoca account.

## What this integration lets you do

Adobe Experience Platform (AEP) streamlines collecting, managing, and acting on customer data across applications. Connecting Invoca to AEP lets you:

* Report Invoca phone calls and Signals to AEP as events, for a unified view of your customers.
* Send Invoca data to AEP Destinations, including Adobe products like Customer Journey Analytics and Adobe Target, and third-party solutions like Qualtrics, MS Dynamics 365, and Zendesk.

## Step 1: Set up a schema in AEP

1. Log in to your Adobe Experience Platform organization and confirm you're in the correct organization.
2. Select **Schemas** in the left navigation menu.
3. Click **+ Create schema**, then choose **Experience Event**.
4. Enter a name (for example, "Invoca") and description, then click **Finish**.
5. Add a field to a new Invoca Field Group by clicking the **+** next to your schema name, entering the field's properties, and clicking **Apply**. The first field you add prompts you to create the Invoca Field Group.
6. Repeat for each field Invoca sends. The default fields are:

| Field Name                     | Display Name                    | Type     |
| :----------------------------- | :------------------------------ | :------- |
| advertiser\_campaign\_name     | Invoca Campaign Name            | String   |
| revenue                        | Revenue                         | Currency |
| call\_source\_description      | Invoca Promo Number             | String   |
| calling\_page                  | Calling Page                    | String   |
| complete\_call\_id             | Invoca Call Record ID           | String   |
| destination\_phone\_number     | Destination Phone Number        | String   |
| duration                       | Call Duration (seconds)         | Integer  |
| hangup\_cause                  | Invoca End of Call Reason       | String   |
| invoca\_id                     | Invoca ID                       | String   |
| landing\_page                  | Full Landing Page URL           | String   |
| media\_type                    | Invoca Media Type               | String   |
| promo\_line\_description       | Invoca Promo Number Description | String   |
| recording                      | Invoca Call Recording URL       | String   |
| repeat\_calling\_phone\_number | Repeat Caller                   | String   |
| signal\_names                  | Signal Names                    | String   |
| utm\_campaign                  | Marketing Campaign              | String   |
| utm\_content                   | Marketing Content               | String   |
| utm\_medium                    | Marketing Medium                | String   |
| utm\_source                    | Marketing Source                | String   |

All fields belong to the Invoca Field Group. If you've created additional Marketing Data fields in Invoca that you want to send to AEP, add a field for each — choose your own field name and display name, and set the type to string.

## Step 2: Set up a dataset in AEP

1. In AEP, click **Datasets** in the left navigation menu, then **+ Create dataset**.
2. Select **Create dataset from schema**, choose the Invoca schema you created, and click **Next**.
3. Complete the dataset fields and click **Finish**.

## Step 3: Create a datastream in AEP

1. Click **Datastreams** in the left navigation menu, then **New Datastream**.
2. Enter a name and description, then click **Save**.
3. On the datastream's details page, click **Add Service** and choose the AEP service to configure (only services you have access to appear).
4. Copy the Datastream ID — you'll need it when setting up the integration in Invoca.

## Step 4: Copy your tenant and sandbox names

1. Log in to AEP and confirm the organization name at the top.
2. Copy the URL in your browser's address bar. It looks like:

```text theme={null}
https://experience.adobe.com/#/@your-tenant-name/sname:your-sandbox-name/platform/home
```

3. Note the value after the `@` symbol as your tenant name, and the value after `sname:` as your sandbox name. You'll need both later.

## Step 5: Create a project in Adobe Developer Console

1. Log in to the Adobe Developer Console and select the correct organization.
2. Click **Projects**, then **Create new project**.
3. Click **Edit Project** and rename it to "Invoca API Connection," then click **Save**.
4. Click **Add API**, select **Experience Platform API**, then **Next**.
5. Select **OAuth Server-to-Server**, enter a credential name, and click **Next**.
6. Select the Product Profiles to enable the API, then click **Save configured API**.
7. Copy the API Key (Client ID) — you'll need it for the Invoca installation.
8. Open **Generate access token** in the OAuth Server-to-Server card.
9. Click **Retrieve client secret** and copy the value — you'll need it for the Invoca installation.
10. Scroll to the bottom of the page and copy your Adobe Org ID — you'll need it for the Invoca installation.

## Step 6: Capture the Experience Cloud Visitor ID in Invoca

Invoca reports events to Adobe using the Experience Cloud Visitor ID when it's available, falling back to the caller ID as a secondary identifier. Invoca passes the caller ID only in the US platform, not the UK platform.

1. Click the gear icon to open your account settings, then click **Marketing Data**.
2. Check whether you already have a field with the API Partner name `mcid`. If you do, confirm it captures the Adobe Experience Cloud Visitor ID, and skip to Step 8.
3. If the field doesn't exist, create a new Marketing Data field:
   * Type: Short text
   * Partner API Name: `mcid`
   * Friendly Name: Experience Cloud Visitor ID
   * Attribution Model: Last
4. If you don't have permission to create Marketing Data fields, contact Invoca support with these details.

## Step 7: Update your Invoca Tag to capture the Experience Cloud Visitor ID

If your Tag isn't already capturing the Experience Cloud 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 (click **New Draft**, not **New Tag**), or continue an existing draft.
3. On the Tag's draft page, find the Experience Cloud Visitor ID parameter in the Marketing Data section.
4. Set its Data Source Type to JavaScript Data Layer and enable it. Enter `mcid` as the Data Source Name.
5. In the `Advanced > Custom Code` block, paste this before the final `return options` line:

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

If you use a different name than "alloy" for the Web SDK, replace "alloy" in the code with that name.

6. Test your changes and confirm the value is captured and dynamic number insertion still works.
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.

## Step 8: Create an Adobe Experience Platform OAuth provider credential

1. In the left navigation menu, select **Manage Integrations**, then **Manage Credentials**.
2. Click **+ New Credential**.
3. Give the credential a friendly name.
4. Choose **Adobe Experience Platform** from the Provider dropdown, and enter the API Key (Client ID) and Client Secret you copied in Step 5.

## Step 9: Set up the AEP integration in Invoca

1. Select **Integrations** in the sidebar, then **Manage Integrations**.
2. Click the Adobe Experience Platform tile and enter details for your AEP datastream.
3. Enter a friendly name for your AEP organization.
4. Enter the API Key (Client ID) again.
5. Enter your Adobe Org ID from Step 5.
6. Enter your Adobe Sandbox Name and Adobe Tenant Name from Step 4.
7. Enter the Datastream ID from Step 3.
8. Click **Next**.

### Create the Action

An Action represents a Call or a specific Signal as an Event in AEP.

1. Click **Edge Network Server API Action**.
2. Enter a friendly name that includes "Call" or the Signal name. Optionally filter by Profile or Campaign to limit which calls or Signals send to this datastream — useful if you have multiple AEP orgs or datastreams mapped to different Invoca Profiles or Campaigns.
3. Under Triggered By, choose the transaction type to send: select **All Calls** to report every call, or **Signal** and the specific Signal to report an in-call event. Create a separate Action for each transaction type you want to send. The Event Name is the exact name that appears in Adobe, so choose it carefully.
4. If you added extra Invoca fields to your schema in Step 1, add them under Additional Parameters — the Parameter Name should match the schema's Field Name, and the Parameter Value can be hardcoded or a dynamic substitution token (click the `< >` icon to see available values).
5. Click **Save**. Repeat the Action setup for each transaction type you want to report.

### Validate that events are reaching the AEP datastream

From Invoca:

1. Click **Integrations**, then **Manage Integrations**.
2. Click the Adobe Experience Platform 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 — the response often explains the issue.

From Adobe Experience Platform:

1. Click **Datasets** in the left navigation menu and find the Invoca dataset to see records ingested and any errors. Click a Batch ID for error details.
2. Select **Customer**, then **Profiles**, to find a profile associated with an Invoca event, and view the Events tab for event details.

## Put the data to work

The value of the AEP integration comes from sharing Invoca call and conversation insights with other systems — Adobe Analytics, Customer Journey Analytics, Customer Journey Orchestration, MS Dynamics, Zendesk, and more — through AEP Destinations.

If your goal is Customer Journey Analytics, Invoca's integration handles data ingestion into AEP; from there, build a Connection to pull in the Invoca dataset, define a Data View, and build your customer journey visualizations using Adobe's documentation.

## Where to go next

* [Adobe Experience Cloud: Integration Overview](/s/article/jhdcp92865-582)
* [Adobe Analytics: Installation & User Guide](/s/article/adobe-analytics-installation-user-guide)