Include and Exclude Existing Variables from Mapping

Once you have imported your existing analytics variables, you can using the Include column to choose which variables to include or exclude from the Apollo implementation.

As variables are included, you can see the running total of variables which you're deciding to retain:

Map to Apollo Variables

Use the Apollo Item Name column to see if Apollo has a corresponding item for each imported item. For example, if you have a Form Name variable in your current implementation, a search for “form” shows various “Form” related items in Apollo. If you find a match, you can select it to map your current variable to the corresponding Apollo item.

If you are unsure of the purpose of of given Apollo Item, you can use the Info Icons to give you more insight into the purpose of the Item. For example, say you notice that Apollo has a variable called 'Fulfillment Source' but you're not sure what this means, you have hover over the Info icon to view the definition:

There may be some cases in which what your organization calls a variable is different from what it is called 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:

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

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 might need to select a “Beacon Globals Setup” or other non-data layer event in the Apollo Event column:

Compare Variable Configurations

If you are unsure if you'd like to map an existing Item to an Apollo Item, you can select the Apollo Item and then view the differences in configuration between the two. To do this, select the Item in the Item Name column, then the Chevron icon on the far right of the row. This expands the Comparison View:

Map to Apollo Events

After selecting the correct Apollo Item Name, the next step is to click on the Apollo Events column next to it to see all of the Apollo Events that can be associated with the selected item. Apollo events are website or mobile app actions that occur or are initiated by users. In some cases, there will be just one Apollo Event associated with an item. In other cases, multiple Apollo Events may be associated with an item. You should select the Apollo Events that you believe are applicable to your website and/or mobile app. These can be changed later, so it is best to choose all that you think may apply.

Once Events are selected, you can use the X to deselect an associated event, or Clear All to wipe the mapped Item and Apollo Event(s).

Filter Your Existing Variables

At anytime, you can filter the Map Existing Implementation table by variables you have chosen to include or exclude or search the list of variables by your existing variable names:

Mapping Influences the Implementation Design for Your Property

As you map your implementation items to Apollo Items and Events, behind the scenes, Apollo will begin to select business requirements that are related to those items, and your implementation data layer will start being built. You should continue this process for all items in your current implementation that you wish to carry forward to your new Apollo implementation.

Start Over

If you've discovered the reporting platform configuration (e.g., report suite) you chose to import was not the correct one, you can opt to start the mapping process over, by selecting the Start Over button:

This will remove any progress you’ve made on mappings as well as any artifacts and configurations Apollo has begun to design as a result of those mapping selections.

Finish Mapping Your Implementation

The Map Existing Implementation process is a one-time step, meant to be performed at the start of your Apollo implementation, so it is important to conclude this process and prevent users from coming back into the Map Existing Implementation screen and making changes. When you've finished mapping your Items to the existing Items in the Apollo database, you should conclude the mapping process by selecting I'm Done or Save & Finish:

Once you Save and Finish this indication, you can begin adding new items to the implementation via the Design Apollo module. Attempts to view the mappings selected reveal to users that the mapping process is complete for the property: