Adobe Analytics Integration

Introduction

This integration allows Delacon to push calls as events into Adobe Analytics.

This guide will take you through the following integration steps:

1. Map the Delacon services within the Delacon portal

2. Add Adobe information

3. Provide Delacon with Event Variables

4. What the data will look like in Adobe

Please note this integration will need to enabled by Delacon before proceeding with the steps below. Contact your Account Manager or Delacon Support to activate the integration for your account.

1. Mapping Delacon Service IDs

Firstly, determine and map all services for which you want to send call data into Adobe Analytics.

Step 1

Alternatively, click on the direct link: https://pla.delaconcorp.com/siteui/configuration/integrations

Delacon_-_Google_Chrome_2022-06-07_19.00.35.png

Step 2

Click on ‘New Integration’:

Step 3

Select the Service ID’s you want to map to Adobe Analytics and click ‘Add’. Note you can select multiple services at the same time.

Step 4

Click Home to return to the Adobe integration homepage.

2. Adding Adobe Information

Once you have selected the Delacon Service IDs to map, you need to add the below Adobe Analytics information to the mappings:

Report Suite ID
Event#
URL

All of this information can be found in your Adobe Analytics instance.

Example of event# required is shown below

Step 5

You have two options for updating this information in the Delacon Portal:

Option 1: Updating for all CIDs mapped

On the Adobe integration screen in the Delacon portal, enter the above information in the relevant fields and click ‘Save’.

This will update the added information for all mappings.

Note: The URL should be in this format: http://xxxxx.sc.omtrdc.net/b/s//6. Adobe ClientCare can help provide the URL.

Option 2: Updating CIDs individually

If you don’t want to update all of the CIDs with the same Adobe Analytics information, you can update each one individually.

1. Click on the ‘Edit’ button for the CID you want to update:

2. Update the relevant fields with the Adobe Analytics information and click ‘Confirm’:

3. Repeat the above process for all CIDs you want to update.

3. Provide Delacon with Event Variables

Once you have mapped your Adobe Analytics integration to Delacon and added the Adobe Analytics information, you will need to provide all relevant Event Variables to Delacon. The Event Variables are the pieces of call tracking data you want to track and report on in Adobe Analytics.

You will need to set up the event variables within Adobe, which assigns a digit to each variable. Please provide these to your account manager or Delacon Support in order for us to add them to your mappings.

Delacon_-_Google_Chrome_2022-06-07_19.25.14.png

See the table below for the available Event Variables (eVar):

Attribute Name/API Key	Description
PLA_BusinessName	The Business Name of the CID
PLA_BusinessCategory	The Business Category Name of the CID
PLA_Caller	The caller number in e.164 format, for example, Australia number is 61xxxxxxxxx
PLA_CallerHashed	The caller number in e.164 format and hashed by SHA256
PLA_CallNumber	The number that the caller called
PLA_CallTime	The milliseconds call time in Epoch time
PLA_Call_Id	The Call ID
PLA_Caller_Anon	When this variable is used, the caller's number is presented anonymised using a UUID-generated random number.
PLA_CallResult	The result of the call: Answered, Busy, Hang UP
PLA_CID	The CID
PLA_City	The city the call originated from
PLA_Dtmf	The phone menu option selected by the caller
PLA_DtmfDesc	The name of the menu option selected by the caller
PLA_Duration	The duration of the call
PLA_Efid	The EFID value extracted from the landing page
PLA_Exchange	The exchange the call originated from
PLA_Keywords	The keywords that can extracted from the landing page
PLA_LandingPage	The landing page of the web session
PLA_Locale	The country and local language
PLA_MID	The MID
PLA_PageCall	The page visited when the call is made
PLA_PageCallExtract	A special way to transform the page call from into a string with ":" as separator. Each token is part of the page call url. For example: https://abc.com/xyz/hzk to abc.com:xyz:hzk
PLA_Referral	The referral page
PLA_SearchEngine	The search engine used by the caller, i.e. Google, Bing, Yahoo, etc.
PAL_SearchType	The type of search, i.e. organic, paid
PLA_State	The state the call originated from
PLA_SurveyOutcome	The outcome of the post call survey
PLA_SurveySaleAmount	The sales value if a sale occurred
PLA_UserAgent	The user agent of the browser
PLA_TermNumber	The termination number