Intarsia Data User Guide

The ID List Report includes two tables: one for Universal Analytics and one for GA4. Each table lists all known views (for UA) or properties & datastreams (for GA4).

All Datastreams

To optimize performance, Intarsia doesn’t automatically fetch all GA4 datastream IDs. If you’ve previously used a specific property or datastream in your Intarsia work, that datastream’s ID should automatically be in the table when the page is loaded. But, to explicitly fetch all datastream IDs, click the button in this section. (Note that this may take a few moments to complete.)

Refreshing after changes are made

If the report doesn’t show up-to-date information, click Refresh Data at the top of the report to force refresh of the data.

GA Views Summary Report

In the Views Summary Report, you select a GA Account from the picker at the top; Intarsia loads a list of all properties and views included in the account, along with their view settings.

The enables comparison of view settings (finally, a quick way to answer “is bot filtering enabled for all views?”), as well as quick-linking directly to GA.

Included View Settings

View settings include:

accountId
accountName
adminLink
botFilteringEnabled
created
currency
dataLink
defaultPage
eCommerceTracking
internalWebPropertyId
kind
selected
siteSearchCategoryParameters
siteSearchQueryParameters
stripSiteSearchCategoryParameters
stripSiteSearchQueryParameters
timezone
type
updated
viewId
viewName
webPropertyId
webPropertyName
websiteUrl

These settings are displayed in a table, as well as a heatmap.

GA Goals Summary

In the Goals Summary Report, you select a GA Account from the picker at the top; Intarsia loads a list of all properties and views included in the account, along with all of their goals and the settings for each goal.

This is useful for comparing goal presence and definition across properties, as well as quick-linking directly to GA.

Goal summaries

Different goals have different detail fields, which can make them difficult to compare. Intarsia summarizes each goal in a “summary” column, making this data consumable.

Included Goal Settings

Goal settings include:

accountId
accountName
active
adminLink
created
destCaseSensitive
destFirstStepRequired
destMatchType
destNumSteps
destUrl
eventActionExpression
eventActionMatchType
eventActionSummary
eventCategoryExpression
eventCategoryMatchType
eventCategorySummary
goal completions
id
internalWebPropertyId
name
pdtosComparisonType
pdtosComparisonValue
profileId
selected
summary
summaryDetail
summaryValue
table id
tableName
type
updated
value
viewName
webPropertyId
webPropertyName

These settings are displayed in a table, as well as a heatmap, to facilitate different kinds of analysis.

Custom Dimension and Metric Definition Comparison (Universal Analytics and GA4)

In each of these four reports, you select one or more GA Accounts from the picker at the top, then click Build when done to pull the data. Intarsia loads a list of all definitions (depending on your report type), along with all of their settings.

This allows the comparison of custom definitions across properties and accounts, as well as quick-linking directly to GA.

Included Settings

Custom Dimension (UA) settings:

accountId
accountName
active
adminLink
created
id
index
internalWebPropertyId
name
scope
updated
webPropertyId
webPropertyName

Custom Metric (UA) settings:

accountId
accountName
active
adminLink
created
id
index
internalWebPropertyId
name
scope
type
updated
webPropertyId
webPropertyName

Custom Dimension (GA4) settings:

accountId
accountName
adminLink
description
disallow ads personalization
display name
internalWebPropertyId
name
parameter name
propertyId
scope
webPropertyName

Custom Metric (GA4) settings:

accountId
accountName
adminLink
description
display name
internalWebPropertyId
measurement unit
name
parameter name
propertyId
scope
webPropertyName

These settings are displayed in a table, as well as a heatmap, to facilitate different kinds of analysis.

Definitions by Property

In addition to the default one-item-per-row view, Intarsia also provides a one-property-per-row view. In this case, each column represents either property-wide information (ie account name, property tracking ID), or a custom metric/dimension slot. In the metric/dimension slot columns, values are brief summaries of the item’s attributes; for example: “Application HIT Active”.

Heatmaps

Each report has two heatmaps: one that displays settings for a particular attribute, and one that does a summary comparison.

Custom Dimension Data Review (UA)

Use the Custom Dimension Data Review to quickly find out what values are being sent to which of your custom dimensions (and how frequently they’re sent).

Gathering data with the Custom Dimension Data Review report

Select a view and a date range from the picker at the top of the report.
Select (check) the custom dimensions you’d like to review. It will take a bit longer to pull data for a greater number of dimensions.
Once your selection is complete, click “Get data for selected dimensions”. Intarsia pulls the total number of hit recorded for each dimension, as well as the top 10 individual values recorded.

Hit type totals per dimension

This table-plus-heatmap combo shows each dimension as a single row; each row includes the total number of hits that were recorded with a value in this dimension, as well as the number of hits for several different hit types.

Hit types include:

Pageviews
totalEvents
screenViews
productDetailViews
productAddsToCart
productCheckouts

Heatmap cells are color-coded based on the number of hits in each combination. Bluer means more hits, yellower means fewer hits, and white means no hits were recorded. If a dimension isn’t listed, Intarsia wasn’t able to retrieve any data for that dimension.

Dimension Values

This table-plus-heatmap combo shows the specific values sent to each dimension. Each dimension-plus-value combo has its own row. In addition to the hit types included in the Hit Type Totals table, this table adds a “rank” attribute indicating the value’s rank in the list of recorded values for that dimension.

The Dimension Values heatmap shows dimensions on the Y-axis and rank on the X-axis. This facilitates a view of each dimension’s value distribution and quickly gives insight into questions like “does this dimension have many possible values, or just a few?” as well as indicating the breakdown between values (ie is it mostly-just-one-value-but-also-a-little-of-many-others, or several-values-used-relatively-equally?).

Custom Dimension Values >100 Characters (UA)

Use the Custom Dimension Values >100 Characters report to quickly find out what values with lengths greater than 100 characters are being sent to each of your custom dimensions (and how frequently they’re sent).

In GA4, parameter values are limited to 100 characters; GA4 truncates these values at 100 characters and doesn’t include characters 101+ in either the GA4 UI or BigQuery. (See https://support.google.com/analytics/answer/9267744?hl=en for more information.) If you’re migrating to GA4, the best way to know where issues with parameter value length might arise is to check your existing Universal Analytics Data.

Gathering data with the Custom Dimension Data Review report

Select a view and a date range from the picker at the top of the report.
Select (check) the custom dimensions you’d like to review. It will take a bit longer to pull data for a greater number of dimensions.
Choose the minimum length to use when pulling data. This defaults to 100, but can also be set to another number; use 200, 300, 400, etc. to check which dimensions have extremely long values.
Once your selection is complete, click “Get data for selected dimensions”. Intarsia pulls the top 10 individual values with length greater than your setting, along with the frequency of their use.

The rest of this report behaves exactly like the Custom Dimension Data Review report, but is based on the values retrieved according to your settings here. See <<LINK>> for additional information.

Copy Filters Between Accounts

Use this tool to copy filters from one account to another.

Select the source Universal Analytics account in the top left.
Select the filters you wish to copy (use checkboxes in the table).
Select the destination Universal Analytics account in the top right.
Click the Copy from Source to Destination (in the middle).
Review filters in the confirmation overlay, and click Confirm & Proceed.
If needed, select other filters and repeat the process until all required filters have been copied.

After copying, you’ll need to assign the filters to specific views in the new account using the GA (Universal Analytics) user interface. You can use the link icons in the two GA selectors to go to the accounts,

Filters Summary

The Filters Summary report gathers data for all Filters (and filter links) in an account, and pivots that information in several useful ways. Choose your desired GA account in the selector at the top, to populate tables below.

Filter summaries

Different filters have different detail fields, which can make them difficult to compare. Intarsia summarizes each filter in a “filter_summary” column, making this data consumable.

Details

Click an item from the main set of tabbed tables to display its details in the Details card.

Included Filter Attributes

Filter attributes include:

accountId
advancedDetails caseSensitive
advancedDetails extractA
advancedDetails extractB
advancedDetails fieldA
advancedDetails fieldAIndex
advancedDetails fieldARequired
advancedDetails fieldB
advancedDetails fieldBIndex
advancedDetails fieldBRequired
advancedDetails outputConstructor
advancedDetails outputToField
advancedDetails outputToFieldIndex
advancedDetails overrideOutputField
created
def
excludeDetails caseSensitive
excludeDetails expressionValue
excludeDetails field
excludeDetails fieldIndex
excludeDetails kind
excludeDetails matchType
filter summary
id
includeDetails caseSensitive
includeDetails expressionValue
includeDetails field
includeDetails fieldIndex
includeDetails kind
includeDetails matchType
link
linked view ids
linked view names
lowercaseDetails field
name
type
updated
uppercaseDetails field
uppercaseDetails fieldIndex
view map

Filters tab

This tab/table shows one row per filter, with all of the attributes listed above.

Views tab

This tab/table shows one row per view, and includes a “linked filter names” column. Useful for getting a summary of which filters are used on each view.

Unused Filters tab

List of filters that aren’t included in any view. These should be deletable, and can be deleted by following the link in the “name” column.

Duplicate Filters tab

List of filters that have a filter summary that exactly matches another filter. To clean these up, you’d want to delete all-but-one of any matching filters. You may need to reassign filters in some views to achieve this. Having multiple versions of the same filters doesn’t hurt anything directly, but it can be difficult to maintain and manage.

Audit tab

Lists every view-plus-filter combo in its own row, along with information about the filter, the view, and the filterlink itself (this is how GA keeps track of filter assignments in the back end.

Rank Map tab

The Rank Map shows data in basically the same format that’s used for the heatmap (below):
Each row is a view and each column is a filter, and each cell shows the rank of that filter in that view.

Tuning what’s included in the heatmap

With a large account with many filters, the sheer amount of data can make a heatmap unreadable. Intarsia offers two ways to limit what’s shown in the heatmap:

Filters: only include filters that are shown in at least X views (enter a number)
Views: include/exclude all views in the properties table by selecting/deselcting

Heatmap

The heatmap shows views on the Y-axis and filters on the X-axis; each cell shows the rank of that filter in that view. Cells are color-coded, with the highest-priority filters (lowest-number rank) using the darkest colors.

Custom Data Import Summary

The Custom Data Import Summary report gathers data for all Custom Data Imports defined in the selected property into a single table.

Choose your desired GA property in the selector at the top, and the table is populated with these attributes for each Custom Data Import:

accountId
created
id
importBehavior
internalWebPropertyId
name
profilesLinked
schema
type
ui link
updated
uploadType
webPropertyId

Unfortunately, the GA API doesn’t allow access to the schema defined for each Custom Data Import. Since that information can’t be included directly in this table, the easiest way to research and add it manually is to use the “ui link” value in each row to jump directly to the individual import. You can also click the link icon in the “name” column to do this.

Add Tag Name Dimension to GA tags (UA)

For debugging purposes, it can be useful to capture the name of a each tag in a Universal Analytics Custom Dimension. Intarsia automatically handles this, eliminating the need to open and edit each tag individually.

Create the custom dimension where you’ll store the GTM tag name (if it doesn’t already exist). Note its slot number.
In the Add Tag Name Dimension to GA tags tool, choose the GTM container from the picker at the top.
Select one or more tags from the Tag List.
Under GA dimension ID, choose the slot number of your new GTM tag name custom dimension.
Click the Add GTM Tag Name to dimension button (it will say something like “For each of 2 selected tags, set dimension 5 to the tag’s name) to make the update
On the confirmation dialog, click Confirm & Proceed.

GTM Container Inspector

Use the GTM Container Inspector to get a birds-eye view of a container, its assets, their configurations, and how they’re linked together. You can also add multiple containers at once, to compare their definitions.

To use this report, select a GTM container and workspace or version from the picker at the top. Intarsia shows a small summary of the container, as well as 3 tabbed tables.

Clicking a row in the Tags/Triggers/Variables tab/tables will show that item’s keys and values in a single table in the Details card.

Tags tab/table

View all tags in the workspace/version in a table format. With this view, you can quickly see which tags utilize which parameters, and what values are sent to them. This is an easy way to verify questions like “do all GA4 tags include a value for parameter x”.

Trigger tab/table

View all triggers in the workspace/version in a table format. In addition to showing all parameters used in each trigger, each trigger has a “trigger summary” column; this provides a quick way to compare triggers to each other.

NOTE - trigger summary not working for some trigger types -

Variables tab/table

View all variables in the workspace/version in a table format. In addition to showing all parameters used in each variable, each variable has a “var summary” column; this provides a quick way to compare variables to each other. This can be especially helpful when looking for variables with different names but the same definitions; sort by var summary to place these next to each other.

Container Visualization

Here we see the container visualized as a spacemap, highlighting the links between tags/triggers/variables. Try dragging nodes around, filtering whats’ displayed, and experimenting with settings. Click here for information about using spacemaps.

This particular spacemap represents tags, triggers, and Variables as nodes. The links between nodes indicate a relationship between the two items; for example, when a tag references a variable, a link is drawn between them. When a variable is used by many tags (or triggers, or other variables) it has many links; when it’s unused, it has no links.

In addition to the standard spacemap filter approaches, you can control exactly which tags, triggers, and variables are shown in the graph by selecting and deselecting items in the tables above. (Note that if all items in a table are deselected, the spacemap falls back to including all items from that table. If you prefer to remove a group entirely, deselect it in the filters below the spacemap.)

Parameter Values

The Parameter Values table lists all parameter values, and shows where they’re used (split by tags/triggers/variables). This illustrates how data is conceptually linked together. For example, a GA Settings variable would normally be used by many GA tags, while a specific ad conversion ID would normally be used by only a single tag.

About Migration projects

Intarsia Migration Projects help you migration an entire GTM container at once. Settings like parameter name mapping, etc are applied consistently throughout the migration. Intelligent, AI-driven suggestions are made.

(GA4) Migration Audit

Whether you’ve migrated a GTM container with Intarsia or not, the Migration Audit report compares the Universal Analytics items in a container against its GA4 items, and shows how one maps to the other.

First (at the top), select a GTM container to review. It’s also useful to select a source Universal Analytics property (this is used when determining source and expected parameter names). After loading, a summary of the container’s UA/GA4 assets is displayed.

Review Tabs/Tables

Tags, Triggers, and Variables

Lists of tags, triggers, and variables are shown in their own tabs. These are very similar to the GTM Inspector/Summary report.

UA Tags and GA4 Tags

These tables show subsets of the Tags table (either UA or GA4, respectively).

UA Custom Dimensions & Custom Metrics

These tables list the Custom Dimensions and Metrics defined in the selected UA source property.

Comparison Tabs/Tables

Settings/Config Comparison

In this table, the container’s Google Analytics Settings Variables and GA4 Configuration Tags are listed (one per row).

For GA Settings Variable rows, you can select a mapped GA4 Config tag in the “ga4_name_html” column. Note the column called “ga4_recommended”. Intarsia scans the Settings Variables and Config Tags and uses AI to determine which GA4 Config tag is most likely to have been the mapped version of the UA tag.

Each column in the table is a *value* that is sent to a parameter in at least one of the items in the table. The cells show the parameter name(s) that received that value.

For example, consider a variable called “dataLayer content.id” that holds an ID for the content shown on the page. This value is sent to Custom Dimension 1 for Universal Analytics Settings Variable “GA Settings”, and to a parameter called “content_id” in GA4 Config tag “GA4 Config”. In this case, there would be a column called “{{dataLayer content.id}}”; in the GA Settings row its value is “dimension_1”, and in the GA4 Config row its value is “content_id”. Since this field is populated for both rows, you know the value is included for each item. Comparing the cell values, you can immediately see that this has been properly mapped.

Event Comparison

If you’ve captured Event Category, Action, and Label fields as GA4 fields, this report uses AI to deduce which GA4 tags are the equivalents of UA event tags.

First, select the GA4 parameter names that were used for this mapping. (When migrating, it’s extremely useful (and a best practice) to duplicate your event category/action/label values into GA4 tags, because this allows hit level event comparison.)

In the table below, see the mapped values for each tag based on that comparison. If Intarsia didn’t get it right the first time, you can change the mapped event. Note the “matches” column (a quick way to verify if all 3 values match) and the ga4_event_name column.

Tools

Using Tables

Intarsia tables are scrollable, both vertically and horizontally. Scroll across to see all attributes, ; scroll down to see more rows.

Filtering

Filter results by typing in the Filter box. You’ll need to exit the box, or click “Search”, to see the result of your filter. Filtering supports regular expressions, and filtering tests against all attribute names and values.

To select or deselect all rows that were included in your filter, use the “Select these” and “Deselect these” buttons.

To achieve complex filtering, you may need to apply a filter, select/deselect those items, then apply another filter, and select/deselect those items, etc.

Zooming

Use the magnifying glass buttons to zoom into and out of the table.

Exporting

Intarsia can export table contents in 3 ways:

Google Sheets - if you haven’t already authorized the Google Sheets API, Intarsia will prompt you to enable authorization after clicking this button
CSV
Copy data to the clipboard

Selecting and deselecting

Tables may have select boxes; if so, click the box to select or deselect. In some cases, you can also click rows to select/deselect. Some tables may have a maximum number of selectable rows; in that case, once the max number is selected, you’ll be unable to select until one or more rows are deselected.

When exporting, a row’s selected/deselected status is included as a column called “_selected”.

Links

Some cells contain links; click the link icon to follow the link.

“Draw all rows” buttons

To improve page performance, Intarsia doesn’t always draw all available content. In those cases, click the “Draw all X rows…” button shown at the bottom of the table content to draw all rows. Regardless of this setting, exports still include all data.

Using Heatmaps

Heatmaps provide an overview that quickly reveals similarities and differences across sets of settings.

In general, when colors are the same, underlying values are the same. When colors are different, underlying values are different.

Interacting with Heatmaps: controlling data

In many cases, the data in a heatmap is controlled by a table just above it. Selecting/deselcting content in the table can pare down the amount of data shown in the heatmap and make it more readable. Note that simply filtering results isn’t enough; you may need to use the “Select these” or “Deselect these” buttons.

Interacting with Heatmaps - controlling color-coding attributes

In some cases, the card that includes the heatmap may contain a pulldown; you can use this to change the background attribute that controls color-coding. For example, if the default is “Name”, you’ll quickly see how names stack up across your data, and whether they’re consistent. Changing this to “Active” (or some other attribute) can reveal cases where Names match, but underlying data is different.

Interacting with Heatmaps: hovering

Hovering over a heatmap will bring up an overlay that displays additional information about the row/column combo.

Comparison Heatmaps

In general, heatmap colors are based on a single attribute. But, what if you want to see a combination of multiple attributes summarized in one color? In that case, we use a comparison model; you select the source property (or view, etc, depending on the heatmap) to compare to, and summaries of that property’s data (per row) are compared to similar summaries of other properties’ data. The result of this comparison produces a comparison score (scale of 0-1, with 0 being exactly the same and 1 being completely different). These comparison scores are used as the source for the heatmap’s colors. Generally, more grey = more similar, and more pink = more different.

Exporting Heatmaps (and other graphs)

In the upper right corner of most graphs, there are one or more download buttons (more if multiple download formats are supported).

Hover over the download buttons to see what type of download is available (usually PNG or SVG), and click to download.

Using Spacemaps

Spacemaps are the primary focus of some reports, but simplified versions also used throughout Intarsia’s tools. Some functionality is common to all.

About Spacemaps

Drag nodes to reposition

Dragging nodes moves them.

Hold Shift when releasing to “stick” a node where it is. Double-click to release the node, and it will be automatically positioned based on its location when released.

Zoom and pan

Zoom in and out by swiping up and down with two fingers or pinching. Click and drag in the space between nodes to move the entire diagram around.

Auto-update settings

Click the and Intarsia auto-sets the zoom, pan, charge, and link distance based on the graph’s data.

Export an image

See Exporting Heatmaps.

Export a table of the spacemap’s data

Click to export nodes and their data as a Google sheet, or to export the same data as CSV.

Help

Click for general help with Spacemaps.

Pausing processing

If the spacemap is unable to fully reconcile itself and reach a stable point, click to pause its engine and temporarily freeze all nodes where they are.

Filtering by node groups

To remove a group of nodes from the graph, uncheck it in the list of groups in the filtering area. To add it to the graph, recheck it.

Filtering by standard filters

Unlinked nodes - uncheck this option to remove all unlinked nodes from the spacemap.
Dev/Test Domains - uncheck this option to remove any site nodes whose domains appear to be dev/test related (for example, domains including ‘dev’, ‘test’, ‘localhost’, ‘preview’, etc).

Highlight by text

Type in the ‘Highlight’ field to highlight any nodes that have an attribute matching the value in the field. Highlight settings are updated when you click the “Highlight” button or exit the related text field.

Filtering by text to Exclude/Include

Type in the Exclude field to remove any nodes that have an attribute matching the value in the field. Exclude settings are updated when you click the “Exclude” button or exit the related text field.

Include Only works similarly, but updates the graph’s data by including only nodes that have an attribute matching its value.

Adding links with Additional Link Depth

Additional link depth allows you to build more specific graphs. For example, you may use the Include Only filter to focus on a single node, identifying it by filtering for its specific ID. However, this graph would have only one node and wouldn’t contain any nodes that the selected node is linked to (or from).

In this case, use Additional Link Depth. Increasing the value to 1 will add all nodes that are 1 link away from the selected node. Increasing to 2 will add all nodes that are 1 link away from the selected nodes, and also add all nodes that are 1 link away from those, and so on.

With this, you can start with a comprehensive global graph, and then pare it back to display a subgraph.

Link Threshold

The Link Threshold breaks links that are below the given setting (default is 0, so all links are represented).

Links usually have an assigned value; for example, in a Google Analytics View + Hostname graph, the number of pageviews on the Hostname is used to define both the size of the Hostname node, and also the value of the link between the Hostname and its View. More pageviews recorded for that Hostname in that view indicates a stronger link between the view and the Hostname.

If you find that a graph is cluttered with many nodes, the Link Threshold is a good way to clean it up. Weaker links are broken, simplifying the graph and pushing smaller nodes to the graph’s edges. This can be combined with the Unlinked Nodes filter; if that filter is deselected, then these newly-unlinked nodes can disappear from the graph entirely.

In another case, imagine node A which is linked to node X at a value of 100, and node Y at a value of 1. The A-X link is much stronger than the A-Y link. If the Link Threshold is raised to between 2-99, then the A-X link stays intact, while the A-Y link is broken, allowing X and Y to be automatically positioned in different areas of the graph.

Force controls: Link Distance

Force-directed node diagrams are governed by specific forces. The Link Distance force indicates how far apart you want linked nodes to be. With a Charge setting of 0, nodes are all positioned directly on top of each other, at the center of the graph (not very useful!). Higher numbers push linked nodes further apart from each other, and lower numbers cluster linked nodes more closely together.

(Note that this doesn’t mean all linked nodes will be exactly the same distance apart; other forces also impact the final rendered layout.

Force controls: Charge

Force-directed node diagrams are governed by specific forces. The Charge force indicates how far apart you want all nodes to be (both linked and unlinked). With a Charge setting of 0, nodes are all positioned directly on top of each other, at the center of the graph (not very useful!). Lower numbers push linked nodes further apart from each other.