All Collections
Map Existing Implementation
Map an Existing Adobe Analytics Implementation
Map an Existing Adobe Analytics Implementation

As an existing Adobe Analytics customer, learn how to map your current implementation to Apollo

Anne Farmer avatar
Written by Anne Farmer
Updated over a week ago

Importing an Existing Implementation

You will typically begin importing your existing implementation during the property creation process. However, if you did not complete the Map Existing Implementation step while creating your Apollo property, you can access the module via the button in the upper right of Property Settings.

To import your existing Adobe Analytics implementation into Apollo, you first have to establish an Adobe IO connection. This connection will allow Apollo to import your existing implementation variables from your Adobe Analytics Report Suite. If you are beginning the Map Existing process for a new Apollo property during the Property Creation flow, you will establish your API connection in an earlier step. If you are beginning the process for an existing Apollo property from the Property Settings, ensure you have a successful API connection under the Connections card.

During the property creation process, you will be asked if you'd like to Map an Existing Implementation.

Clicking No, I'm done will complete the property creation process and disable the Map Existing Implementation module for your property now and in the future. All configurations for your Apollo property will take place in the Design module.

Clicking Yes will allow you to select the Adobe Analytics Report Suite you would like to map to your Apollo property.

Once you have selected your report suite, click Import. This initiates the import process. At this time, all other design features, such as Business Requirements and Apollo Event Attributes, go into read-only mode until you complete the map existing implementation process. If you decide against mapping your existing implementation, you can click Never Mind to return to the Map Existing confirmation dialog.

After you have imported the desired Adobe Analytics Report Suite from property creation, you will be redirected to the Map Existing Implementation view.

If you are mapping your implementation across multiple sessions, you will see a banner in your Apollo property indicating that the Design features are unavailable. These features will remain unavailable until you have finished mapping your implementation. You can return to the Map Existing Implementation module by clicking Take me there.

Additionally, you can access the Map Existing Implementation feature by visiting Property Settings and clicking Map Existing Implementation in the upper right of the modal.

Mapping Your Existing Adobe Analytics Variables to Apollo Variables

In the Map Existing Implementation module, you will see a list of variables configured in the Adobe Analytics Report Suite you have imported. If at any time you would like to restart the mapping process, click the Start Over button. This removes all previous mappings you have made and allows you to select a different Adobe Analytics Report Suite to map from. If you have multiple API connections associated with your Apollo property, you may also select the connection you would like to use.

Above the variable table, you will also see the ratio of variables you have included in your mapping over the total number of variables available to map.

At anytime you can filter the existing variables list to see those that have been included or not. Additionally, the open search field allows you to search the table for existing variables by Variable Name.

Using the Include column, toggle the switch to include any variables from your report suite that you would like to map to your Apollo property. By default, the value for each variable is set to exclude, indicating that the variable will not be included in the Apollo implementation. Toggling the value to include enables the variable, allowing you to map it to the corresponding Apollo Variable and Event(s).

Note: If there are “out-of-the-box”/platform built-in data points associated with your implementation, they will not be shown on the Map Existing Implementation screen. These are automatically mapped and included in your implementation.

Using the Apollo Variable Name column, look for an Apollo variable that corresponds to the Adobe Analytics variable you would like to import. For example, if you have a variable, Product Name, in your current implementation, a search for product in the Apollo Variable Name dropdown shows various "product" related variables available in Apollo. If you would like to learn more about a variable, hover over the information icon next to it to display its definition. When you find a match, select it to map your current variable to the corresponding Apollo variable.

Once you have selected a corresponding Apollo variable, you will be able to select which Apollo Events the variable should be associated with. In the Apollo Events dropdown, you will find a list of Apollo Events that are currently using the Apollo variable you are mapping. Again, if you would like to learn more about an event, hover over the information icon next to it to display its definition. In some cases, there may be just one Apollo Event associated with a variable. In other cases, multiple Apollo Events may be associated with a variable. You should select all of the Apollo Events that you believe are applicable for your implementation. Click Select All to select all available events. Click Clear All to revert any assignments you've made for the Apollo Variable or Event(s).

To save the selections and updates you have mapped click the Save button in the floating footer. If you exit or refresh the Map Existing Implementation module without saving, all unsaved changes will be lost. To undo any unwanted modifications since your last save, you may click Revert Changes in the floating footer.

There may be some cases where your organization identifies a variable differently from what it's named in Apollo. For example, your organization might use the KickFire Account-Based Marketing tool to identify companies visiting the website. This may be labeled more generically in Apollo as shown here:

In addition, there are some implementation items that are not set in the data layer. These might be set by JavaScript plugins or other mechanisms. In these cases you will see the Apollo Variable associated with one of the following Apollo Events:

Client Side Data Enriched, Server Side Data Enriched.

If you don’t find a corresponding Apollo event or variable that matches the variables in your current implementation, please reach out to the Apollo team who can help determine if what you are looking for already exists.

As you map your Adobe Analytics Report Suite variables to the corresponding Apollo events and variables, Apollo is enabling the related business requirements behind the scenes. Additionally, Apollo is generating the data layer specification for the implementation you are building. You should continue this process for all of the items in your current implementation that you wish to carry forward to your new Apollo property.

Complete Mapping

Once you are done with your configurations, you may click All Mappings Complete in the upper right or Save & Finish in the floating footer. Please ensure that you are completely satisfied with your mappings, as you won't be able to make changes after you've completed the map existing process.

Congratulations! You've finished mapping your existing Adobe Analytics Report Suite to your Apollo property. Now you can take advantage of the rest of Apollo's features.

Did this answer your question?